Client Onboarding on iMessage: Own the First 30 Days
The short answer
Client onboarding is the stretch between a signed contract and a client's first real result, and it's the window where churn gets decided. The work looks like admin: booking kickoff, chasing documents and access, confirming milestones, checking in. Every item on that list is a small ask, and small asks die in inboxes. Move them to iMessage and they get answered, because messages on this channel see a 98% open rate with 90% read inside three minutes, against email open rates that have fallen to 27.7%. Onboarding looks like a coordination problem and behaves like a revenue problem. The client who went quiet in week two is the one you're surprised to lose at renewal, and the postmortem always blames the product.
3 use cases in this category
Trigger
Event in your CRM
Under 60s
Send iMessage
Result
Reply in the thread
Key takeaways
- Stalled onboarding charges twice: once in idle unearned revenue, again at renewal when friction is fresh.
- Emails ask for work and arrive where people defer work.
- One sequence fires at signature and runs nine steps across 30 days.
- Onboarding texts should sound like the person the client just signed with.
- CRM setup is a workflow build, not integration.
- One headline: time from signature to first delivered milestone.
Where iMessage runs in the funnel
What does a stalled onboarding actually cost?
Stalled onboarding charges twice: once in idle unearned revenue, again at renewal when friction is fresh. Twenty clients at $4,000/mo is $133/day per account; 26 to 9 days frees $2,266 per client, roughly $45,000 a quarter.
- Labor compounds it. A coordinator writing four chase emails per account per week across 20 accounts writes 320 emails monthly. Cold email replies at 0.45% per Belkins 2025 data; your request sits three slots below a newsletter.
- At renewal, a client decides what working with you feels like in month one. One spent being chased learns the relationship runs on chasing, and that lesson sticks long after delivery fixes everything.
Why do kickoff emails and document requests go unanswered?
Emails ask for work and arrive where people defer work. Texts are interruptions with a name on them, and everything you're asking for is short: pick a time, grant access, upload one file, confirm.
- Email reminders lose weight with each repetition. Texts hold up better; under 3% are flagged spam versus 85% of email. The fourth message lands in one thread, not a folder the client stopped opening.
- iPhone households average $85,000 income, 40% above Android, so B2B books skew toward blue bubbles. iMessage availability checking tells you which numbers are reachable before you write a word.
How does the onboarding play work, step by step?
One sequence fires at signature and runs nine steps across 30 days. Step one goes out 15 minutes later while the buying signal is warm; step two resends the booking link two hours later if no slot booked.
- Day 1 confirms the call and lists three things to bring. Day 3 chases one document item per message (naming the whole list gives permission to do none). Day 7 confirms first milestone; Day 14 asks one question answerable in a word. Day 21 sends the first real number unprompted; Day 30 closes with what shipped plus next-30 plan.
- Schedule every step in recipient time zone so Day 3 doesn't land at 6am in Denver. Watch delivery states and read receipts so the sequence isn't running blind.
What's the right cadence for the first 30 days?
Cadence beats volume in onboarding. Nine touches across 30 days reads as attentive; the same nine crammed into week one reads as a bot. The table below is the default shape. Compress it for engagements shorter than 30 days, and stretch the back half for long enterprise builds.
- Read the silence column as carefully as the message column. A read receipt with no reply at Day 3 almost always means the ask is bigger on their side than it looks on yours.
15 min after signature
- Trigger
- Contract signed
- What the message does
- Names the account owner, sends the kickoff link
- What silence tells you
- Check the number is reachable before anything else
Same day, +2 hours
- Trigger
- No kickoff booked
- What the message does
- Resends the link with one line of context
- What silence tells you
- Booking friction, not disinterest
Day 1
- Trigger
- Kickoff booked
- What the message does
- Confirms the time, lists three things to bring
- What silence tells you
- They will show up unprepared
Day 2
- Trigger
- Kickoff held
- What the message does
- One-line recap plus a single next action
- What silence tells you
- The recap didn't land, repeat it live
Day 3
- Trigger
- Documents outstanding
- What the message does
- Chases one specific item, offers to do it together
- What silence tells you
- The item is harder than you think
Day 7
- Trigger
- First milestone due
- What the message does
- Confirms the hit or flags the slip early
- What silence tells you
- The timeline is slipping quietly
Day 14
- Trigger
- Mid-window check
- What the message does
- Asks one question answerable in a word
- What silence tells you
- First genuine churn signal, escalate
Day 21
- Trigger
- First result available
- What the message does
- Sends the number before they ask
- What silence tells you
- Value isn't registering yet
Day 30
- Trigger
- Window closes
- What the message does
- Recaps what shipped, sets the next 30 days
- What silence tells you
- Account is coasting, book a review
What do you actually say in an onboarding text?
What do you actually say in an onboarding text?
Onboarding texts should sound like the person the client just signed with. Short, lowercase where it fits, one ask per message, and no template smell.
- Voice memos at Day 2 and Day 21 carry tone that paragraphs cannot; clients replay them. Tapbacks on milestone confirmations close loops without writing. Group messaging at Day 2+ keeps buyer and operator in one thread so nothing gets relayed wrong.
- Step one, 15 minutes after signature: "hey Marcus, it's Dana from Northlight. saw the agreement come through, congrats. i'm your day to day on this one. grab whatever kickoff slot works this week and we'll get moving: [link]"
- Day 3 document chase: "morning Marcus. everything's ready except ad account access, and that's the only thing holding the build. it's about 30 seconds on your end. want me to jump on a 5 min screenshare and do it with you?"
- Day 14 check-in: "quick one, nothing needed from you. two weeks in, how's it feeling? one word is a fine answer."
How do you set up onboarding texts in your CRM?
How do you set up onboarding texts in your CRM?
CRM setup is a workflow build, not integration. GoHighLevel runs it natively; trigger on Won or contract-signed, whichever fires first. Run iMessage availability checking before step one.
- Map variables to custom fields: owner name, kickoff link, and the outstanding item at Day 3. That last field makes the document chase specific instead of generic.
- Build exits first: replies stop remaining steps and sit with the account owner. Milestone complete skips confirmation. Webhooks write delivery states and read receipts back to the CRM. REST API and webhooks handle other stacks. Opt-out is enforced account-wide.
Setup happens during white-glove activation rather than on your side. Bring the CRM you already run and we will map the triggers on the call.
See it wired to your CRMHow do you measure whether onboarding texts worked?
How do you measure whether onboarding texts worked?
One headline: time from signature to first delivered milestone. Baseline a full quarter before switching channels. Hold out 10% of new accounts on email to carry a control group.
- Four diagnostics: time to kickoff booked (hours from signature), time per document (per item, not per client), reply rate by step, and read-to-reply lag. Unread means wrong number or hour; read-no-reply means ask too heavy.
- Tie all to retention with a lag. Track 30-day activation and check 90-day plus 12-month logo retention two quarters later. On-time activation predicts renewal; onboarding becomes a retention lever not just ops cost.
Is texting clients during onboarding compliant?
Is texting clients during onboarding compliant?
TCPA governs business texting on every channel, including signed clients. Onboarding stands on firmer ground because the client handed over the number as engagement. Capture messaging consent in the agreement and log timestamp.
- FCC consent-revocation rules took effect 11 April 2025; revoke-all extends to 31 January 2027. Honor revocation in whatever words the client uses, not only STOP. Blue Reacher enforces account-wide opt-out.
- iMessage is not carrier SMS, so no A2P registration is required. That's a registration distinction, not a consent exemption. Consent rules apply the same way they do everywhere else.
Frequently asked questions
Should onboarding texts come from a person or from the company?
A person, always. A text signed by the account owner tells clients they bought a relationship, not just software. Use the owner's first name in step one and keep it on every step, so the thread reads as one conversation with one human that they'll reach for later when something breaks.
What happens if a client is on Android?
Android clients still get the message via RCS then SMS fallback, so a mixed book runs through one sequence. iMessage availability checking tells you which numbers are blue-bubble before you send, so you know which threads will read as personal text and which won't.
How many onboarding texts is too many?
Nine touches across 30 days is the practical ceiling. Count asks per message: one ask per text can run daily, while three stacked stalls the sequence. Cut any step that only confirms what the client already knows. Never send a message whose entire content is that you're following up.
Does iMessage replace onboarding email?
No. Email keeps contracts, invoices, long-form docs, and anything the client will search for later. Texting handles the short layer: scheduling, chasing, confirming, and checking in. Pattern: text carries the ask, email carries the attachment. Text tells them the email exists.
Can we send files and updates inside the thread?
Yes. Media, voice memos, and tapbacks all live in the channel. A kickoff recap can be a 20-second voice memo; a milestone update can be a screenshot of the real dashboard. Buyer and operations lead sit in one group thread instead of relaying. Keep contracts and signatures in email for searchable records.
Do we need A2P 10DLC registration to text our own clients?
No. A2P 10DLC governs US carrier SMS routes; iMessage is not carrier SMS. That's a registration distinction, not a consent exemption. TCPA and FCC revocation rules apply the same way. Capture consent in the engagement agreement, log it, and honor revocations in whatever wording the client uses.
Which message in the sequence matters most?
Day 21, the one that sends the first real number before the client asks. Every message before that is coordination, which only buys patience. Day 21 turns patience into belief. Most teams skip it because the result feels too early; send it anyway. A small number unprompted beats a big one late.
What does it cost to run onboarding on a dedicated line?
$249 per line per month or $1,949 per year (about $162.50/mo). Unlimited iMessages; new outreach paces at 50 opted-in / 30 cold per line per day (conversation channel, not blast). No per-message fees. White-glove setup included; the $449 activation fee waives on annual billing. Flat rate means volume spikes don't produce surprise bills.
Onboarding is the cheapest retention you'll ever buy
Every account you sign this quarter runs through a first 30 days whether you design that window or not. Book a walkthrough and we'll map your current onboarding sequence onto a dedicated iMessage line, wire it into GoHighLevel or your CRM through the API, and hand it back running. $249 per line per month, unlimited iMessages, no A2P registration required, and the $449 white-glove activation is waived on annual billing.