A snapshot copies your texting setup to a new client, and it copies your mistakes with it. Before you deploy one, check that its templates carry the right sender identity and opt-out language, that no workflow texts without consent, and that the client has their own registration and number.
Snapshots are how agencies scale, so this isn't an argument against them. It's an argument for treating a snapshot as a compliance document. What follows is what to look for, using Ready as the texting layer. Compliance is the sender's responsibility, and this is risk reduction, not a legal opinion.
What a snapshot carries, and what it doesn't
A GoHighLevel (GHL) snapshot is a saved copy of an account's configuration: workflows, templates, pipelines, forms and similar assets. Check exactly what yours includes before you rely on this list, because GHL decides what goes in a snapshot and can change it.
What a snapshot can't hand over is the thing carriers care about most: the client's own identity. A registration belongs to a business, not to your agency's template. The number, the registered campaign and the consent behind each lead are all client-specific.
So the split looks like this.
| Item | Travels in a snapshot? | Who has to supply it |
|---|---|---|
| Workflow logic and timing | Yes, check yours | You, reviewed per client |
| Message templates | Yes, check yours | You, edited per client |
| Business name in the text | The old client's, if hard-coded | The new client |
| Registration (brand and campaign) | No | The new client's business details |
| Phone number | No | Bought for the new client |
| Proof of consent | No | The new client's forms and CRM |
The templates problem
The most common snapshot failure is a template that names the wrong business. If a message hard-codes "Hi, it's Dana from Summit Dental" (a made-up example) and you deploy it for a roofer, you've sent a text that misidentifies the sender, and carriers compare message content to the registered business.
Use merge fields for the business name and review every template once per client. Ready adds "Reply STOP to opt out" and the business name to the first text to each contact, unless the account turns it off, so read the footer against your template to avoid a doubled or contradictory opt-out line.
Also check that each template fits the registered use case. A client registered for appointment reminders shouldn't inherit a promotional blast from a snapshot built for a different campaign. Our guide to picking a campaign use case explains how that choice shapes what's allowed.
Workflows that text without consent
Snapshots often include a "new lead" workflow that texts the moment a form is submitted. That's the right speed, but only if the form collects consent to texts. A contact form with no checkbox and no disclosure is a consent problem the snapshot happily replicates across fifty clients.
For each client, the form feeding the workflow needs to say who will text, roughly how often, and that the person can reply STOP. Ready stores no per-contact consent, so the client's form or CRM is the record, and you should keep it where you can pull it up. (A sign-up on a Ready-hosted opt-in page is the exception, stored per contact; support@tryready.com can send a copy.)
Cold contact is a separate matter. SMS goes to people who've consented or replied; cold contact is by phone and mail. A snapshot that texts a purchased list is a liability, not a time saver. Read who gets sued when a client's list is texted before you promise a client anything about their lists.
Quiet hours and timing inside workflows
Snapshot workflows are written with wait steps and often ignore the recipient's time zone. Ready enforces quiet hours by recipient area. Campaigns, drip campaigns and automations wait up to 24 hours for the window. An inbox text to one person is scheduled for when the window opens and shows in the thread with Cancel. An API text is held only if the window opens within 6 hours; otherwise the API answers 409 QUIET_HOURS_BLOCK with next_allowed_at.
There's one carve-out. A reply to a contact who texted this account in the last 24 hours can go out at any hour. So a lead who texts at 10 PM can get an answer, while a template fired at 10 PM at a lead who only filled in a form will be held or refused. Test a late-night submission once per snapshot, and see our post on quiet hours across time zones for the details.
Opt-outs across cloned accounts
A STOP always blocks that number in the sub-account that received it. Whether it also blocks the parent and the other sub-accounts is decided by Ready for every account, not by a setting you can change, so don't promise a client that one STOP silences every client of yours. Check GET /v1/opt-outs/:phone when a contact moves between tools or accounts.
This matters most when you deploy a snapshot over an account that already had contacts. A person who opted out somewhere else can end up in a new workflow if the old opt-out list didn't come along. Clean the list before the snapshot's first send. The opt-out API is documented in the opt-outs reference.
Who owns what after the deploy
A snapshot blurs a line that matters: your agency built the workflow, but the client's business is the sender. Carriers see the client's registered brand, and the person who gets the text sees the client's name. If a complaint arrives, it lands on the client's registration first.
So put three things in your agreement. The client confirms in writing that their forms collect consent. The client keeps the consent records, or you keep them on their behalf and say so. And either side can pause a workflow the moment a complaint arrives. That's not legal advice, and a lawyer should draft the real terms, but even a short paragraph beats discovering the question mid-dispute.
The pre-deploy checklist
Run this each time you push a snapshot to a client:
- Replace every hard-coded business name with a merge field, then read each template aloud.
- Match each template to the client's registered use case.
- Confirm the client has their own registration, approved, and their own number.
- Open the form that triggers each workflow and confirm it collects consent to texts.
- Send a test from the client's sub-account, reply, then reply STOP and try again.
- Check the first-text footer against your template wording.
- Submit a test lead outside calling hours and see what happens.
- Check the mapping between the client's GHL sub-account and its Ready account.
On cost, each segment is $0.0075 plus a $0.0045 carrier fee, and registration is $25 a month per client with $2 a month per number. Texts through a connected GHL sub-account are billed from the first one, so your tests cost money. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing. The all-in rate leaves out screening, the per-segment charge for the Scrub lists and Number validation switches.
Keep the snapshot honest
Treat the snapshot as a living file. When a carrier rule shifts or a client complains, fix the snapshot, and note the date, so the next deployment starts clean. For the onboarding steps that sit around it, see the agency client onboarding checklist, and for registration see the GoHighLevel 10DLC guide.
The snapshot should save you hours and never skip the per-client facts. If you want to try Ready on one client's sub-account, sign up and run the checklist above.