WhatSnapHelp

WhatSnap for Agencies

Build a high-performance messaging infrastructure for your GHL agency — from hardware models to pricing strategies.

Scale WhatSnap across multiple clients with this complete agency guide. Learn infrastructure models, pricing strategies, and best practices for managing messaging across your entire GHL agency.

Why Agencies Use WhatSnap

While other agencies wait weeks for A2P registration or fight with shared Twilio numbers, you can have clients messaging the same day with 100% deliverability from real devices.

What you offer:

  • P2P messaging across iMessage, SMS, WhatsApp, and Twilio — all from real devices
  • iMessage "blue bubble" trust for Apple users
  • No per-message fees — just subscription + your own SIM plans

Infrastructure Models

Choose the model that fits your fulfillment approach.

You provide the hardware. Host a Mac mini or Android rack in your office and assign lines to client subaccounts.

Pros:

  • 100% control over uptime
  • Faster client onboarding
  • Recurring hardware fees

Cons:

  • You're responsible for uptime
  • You cover SIM plan costs

Best for: Full-service agencies with dedicated office space.

Pricing Your Service

Don't just pass through the WhatSnap subscription cost. Your value is in the infrastructure stability and results you deliver.

ModelRecommended PriceYou Provide
SaaS Add-on+$49/mo1 dedicated line
Managed Messaging$297-$497/mo3 lines + campaign management
Full Fulfillment$1,500+/moMulti-channel cluster + outreach

Scaling formula: Start with one line per 200 daily outbound messages. A client sending 1,000 messages/day needs a "5-Line Infrastructure Bundle."

Managing Multiple Clients

The Agency Dashboard

From your WhatSnap Manager, you see an overview of your entire network:

  • Lines: Every connected device across all clients
  • Subaccounts: Which GHL subaccounts have WhatSnap active
  • Status: Real-time health indicators (🟢 Connected, 🟡 Warning, 🔴 Offline)

Data isolation: While you manage everything from one dashboard, clients cannot see each other's messages or contacts.

For step-by-step instructions on activating subaccounts, allocating lines, and moving resources between clients, see Allocating Lines and Subaccounts.

Essential SOPs

1. The 14-Day Warm-up

Never let a client send 1,000 messages on Day 1. Enforce the 14-day warm-up schedule for every new P2P line. The warm-up article covers the full day-by-day process, including how to automate it with AI agents.

2. Weekly Uptime Checks

Every Monday morning:

  • Verify all client devices show 🟢 status
  • Check for any queued messages (indicates delivery issues)
  • Review the weekly message volume per client

3. Template Review

Before any campaign goes live:

  • Verify message scripts follow outreach best practices
  • Check for spam trigger words
  • Confirm opt-out language is included

Common Questions

Can I white-label the WhatSnap Manager?

While the tech is WhatSnap, you can hide the Manager tab from clients using GHL User Permissions. Manage their lines for them as a "Managed Infrastructure" service while maintaining your brand.

How many lines should I assign per client?

Start with one line per 200 daily outbound messages. If a client needs to message 1,000 leads per day, they need a 5-line setup.

What happens if a client cancels?

Toggle their subaccount to OFF in your WhatSnap Manager. The hardware line is freed up and can be assigned to a new client.

Should I include the SIM plan cost?

For managed services, yes — build it into your monthly fee. For BYOD setups, have the client pay their carrier directly.

Related

Was this page helpful?

Last updated on February 8, 2026

On this page