Onboard each new client's texting in this order: gather their business details, confirm how their leads consent, register the business, get a number, connect the sub-account, then send a test before any workflow goes live. Skip a step and you usually find out when a text is filtered, which is a bad time to be explaining it to a client.

This checklist is for agencies running client sub-accounts in GoHighLevel (GHL). It assumes you're using Ready as the texting layer, which installs natively into GHL through OAuth. The same order works on any setup, though the product details below are Ready's.

Before you touch the sub-account: collect the facts

Registration is where most delays start, and almost all of them come from missing or mismatched business details. Collect these before you open the form.

  • The client's legal business name, exactly as it appears on their EIN paperwork.
  • Their EIN. Ready registers businesses with an EIN only, so a client without one can't register. Tell them early rather than after you've built their workflows.
  • A business address and a working website.
  • A privacy policy and terms on that website that mention texting.
  • A contact person and email who can answer a carrier question.
  • A plain description of what they'll text and who they text.

If any of that is missing, the client's work stalls. Our guide to website, privacy policy and terms requirements lists what reviewers look for on the site.

Confirm consent before you build anything

Registration asks you to describe how people opt in, and carriers compare that to what they see. So settle it first. For each client, write down where a lead agrees to texts: a form checkbox, a booking page, a keyword, a verbal yes logged in the CRM.

Then check the wording. A person should be able to tell they're agreeing to texts from this business, how often, and that they can reply STOP. Ready stores no per-contact consent for you, so the client's form or CRM is the record. Keep it somewhere you can pull up in a dispute. (The one exception is a sign-up on a Ready-hosted opt-in page, which is stored per contact; support@tryready.com can send a copy.)

The opt-in examples and sample messages post has wording you can adapt. Who carries the risk when a client's list is bad is a separate question, covered in who gets sued when a client's list is texted. Settle it in your agreement before the first send.

Register the client's business

Registration is one line per client on Ready: $25 a month, covering the brand and its first campaign. A second campaign adds $20 a month. There's no setup fee; the charge at submit is the first month. Most approvals take 2 to 7 days.

Fill it in from the client's collected facts, and make the campaign description match what the client will really send. A mismatch between the registered use case and the actual messages is a common reason for a later problem. The form takes a few minutes. Our GoHighLevel 10DLC registration guide explains the fields in more depth.

One rule on timing: don't send client traffic at volume while registration is in review. An account can send up to 500 texts a month before it registers, at its normal rate, and after that it has to register. Treat that as room for a test, not a launch plan.

Get the client a number

Each client gets a number of their own, at $2 a month. A card on file and a number are needed before anything sends. Pick a local number that matches the client's market, since people tend to answer a familiar area code.

If the client wants local presence (sending from the number closest to the contact's area code), it's off unless you turn it on, and it costs $0.0015 for each segment of a delivered text. Accounts made before November 16, 2026 keep it free. In GHL, the #from:local# tag picks it. Leave it off unless the client's contacts are spread across area codes.

Connect the sub-account

Install Ready into GHL with OAuth and map each client's sub-account to its Ready account, so every client stays isolated. Inbound and outbound messages then sync both ways, and replies land in the GHL conversation. Our GHL setup guide walks through the clicks.

Two billing notes agencies miss. Texts sent through a connected GHL sub-account are billed from the first one, so budget a few cents for testing the sync. And each client sub-account is mapped separately, so check the mapping client by client, not once for the agency.

Run a pre-launch test

Before a workflow goes live, send these from the client's sub-account to a phone you control:

  1. A normal outbound text, and confirm it arrives from the client's number.
  2. A reply, and confirm it shows up in the GHL conversation.
  3. A STOP reply, then try a second text and confirm it's blocked.
  4. A text that includes the business name and opt-out language, so the first message identifies the sender.

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 check how that footer reads against your template. Count it when a message sits near a segment limit. A single segment is 160 characters in GSM-7 and 70 once an emoji appears, and each segment is billed at $0.0075 plus the $0.0045 carrier fee.

Set the guardrails before the client asks

Decide these on day one, in writing:

ItemDecide
Quiet hoursCampaigns, drip campaigns and automations wait up to 24 hours for the window. A text sent from the Inbox is held until the window opens. An API text is held only if the window opens within 6 hours, otherwise it isn't sent and someone sends it again.
Opt-outsSTOP is honored on the sub-account that received it. Check GET /v1/opt-outs/:phone before any send from another tool.
Who answers repliesName the person who reads replies, because odd opt-out wording needs a human.
BillingDecide whether you pass through, mark up or bundle. See the rebilling guide.
PricesAccounts opened before November 12, 2026 keep their signup prices, shown under Billing.

The all-in rate is $0.012 per segment and doesn't include screening, the $0.003 per-segment charge for Scrub lists and Number validation when switched on.

Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.

Mistakes that cost agencies a week

Most delays trace back to a short list. A client gives a trade name that doesn't match the EIN record, so the review stalls. The website has no privacy policy, or one that never mentions texting. The registered use case says appointment reminders and the first workflow sends promotions. Or a snapshot gets copied from another client and carries that client's wording into the new account.

None of these are exotic. They're all caught by reading the intake sheet against the first workflow before launch. If a registration is rejected, the rejection decoding guide shows how to read the reason and resubmit. Budget a day for one resubmission on your first few clients, and you'll rarely need it later.

The one-page version

Keep this near the intake form:

  1. Legal name, EIN, address, website and privacy policy are collected.
  2. The consent source is written down and checked.
  3. Registration is submitted, then approved, before volume starts.
  4. A number is bought for the client.
  5. The sub-account is connected and mapped to the right Ready account.
  6. A test send, a reply, a STOP and the footer have all been checked.
  7. Quiet hours, the reply owner and billing are agreed in writing.

Run every client through the same sheet and the surprises shrink. Compliance stays the sender's responsibility, so the checklist reduces risk without erasing it. When you're ready to try it on one client, sign up and start with the test.