What this guide is, and is not
An SMS reactivation engine is the highest-leverage marketing asset most operators are not running. The dormant list in your CRM has thousands of contacts who used to buy and stopped. Reaching them well is a category-defining channel. Reaching them poorly burns the relationship and your sender reputation in the same week.
This guide tells you what good looks like. It does not tell you how to build one. The actual decision engine, message-scoring layer, framework-selection logic, and pre-send architecture that Gibson runs inside Reignite are proprietary. You'll finish this guide knowing how to evaluate any provider, including us. You won't finish with a copy of our build.
Why SMS at all
Email re-engagement campaigns hit dormant lists with 20% open rates and 2 to 4% click rates. SMS hits dormant lists with 98% open rates and replies that land in hours, not weeks. The reason is structural. Email is where dormant relationships go to die. SMS arrives where the person already is, on their phone, and gets read.
But SMS is also a more fragile channel. Compliance is tighter. Brand-damage risk is higher. The wrong message at the wrong time burns more than just the lead. Which is why the engineering matters more, not less.
The five questions to ask any reactivation provider
Before signing a contract, ask each of these. The answers separate real engines from glorified blast tools.
- +Who owns the sender number? If your provider routes through a shared pool, your messages share a reputation with whoever else is on the pool. You want a dedicated number, identifiable to your brand, that doesn't get spam-flagged because someone else abused it.
- +What happens before the SMS sends? A real engine scores every draft before it leaves the system. Bad drafts get rewritten. Unsafe drafts get blocked. Ask: 'what is your pre-send quality control?' A vague answer means you're the test.
- +How is opt-out handled? ACMA requires a working opt-out path on every commercial SMS. The provider should never send to an opted-out number again. Roll-your-own opt-out logic is where most homemade engines fail compliance.
- +What happens when a lead replies? A blast tool sends a message and stops. A real engine reads the reply, classifies it (booking intent, question, opt-out, negative, ambiguous), and routes accordingly. Ask: 'show me a reply that triggered a booking, and one that triggered an escalation.'
- +How is success measured? Reply rate is a vanity metric. Booked-jobs-per-1000-sends and recovered-revenue-per-tenant are the real ones. A provider who can't show you those numbers from another tenant is selling you the experiment.
Where most setups quietly fail
After running this category for a long time, we see the same failure modes repeatedly. Watch for these.
- +Shared sender numbers. The cheapest provider option. Tanks deliverability the first time another tenant on the same pool gets reported.
- +No conversation continuity. The engine forgets the previous reply when drafting the next message. Leads stop engaging after one turn.
- +Manual approval queue. Every draft has to be approved by a human before send. Looks safe in the demo. Becomes a backlog in week two and nothing ships.
- +No outcome recording. Replies happen, jobs get won, but nothing flows back into the CRM. The whole engagement disappears from reporting.
- +No learning loop. The engine never improves. It sends the same messages with the same scoring forever.
The compliance frame, non-negotiable
Australian SMS marketing is governed by the Spam Act 2003 and ACMA. Get any of these wrong and the fines are real.
- +Identification. The sender must be identifiable in the first message. Your business name, not a generic short code.
- +Consent. You can only SMS contacts who consented or have an inferred consent (existing customer relationship, public listing where consent can be inferred). Dormant CRM contacts who were customers have inferred consent for 24 months after last engagement.
- +Opt-out. Every message must include a working opt-out. STOP-keyword handling at the carrier level is the safest route. Don't roll your own.
- +Quiet hours. No commercial SMS between 9pm and 9am local time, or on Sundays.
What you should refuse to sign off without
If you're paying for an SMS reactivation build (us or anyone else), these are the deliverables that protect you.
- +Dedicated tenant sender number, with a compliance receipt showing the inbound webhook is correctly configured.
- +Documented pre-send quality control, with an example of a draft that was rewritten and a draft that was blocked.
- +Documented reply classification, with an example of each class routing correctly.
- +An outcome dashboard that shows recovered revenue per tenant, not just replies.
- +A monthly evidence pack: messages sent, replies received, outcomes recorded, opt-outs handled, sender reputation status.
Where the value flows
A well-built SMS reactivation engine changes more than one number in your reports.
- +Sales: warm appointments dropped in the calendar, sourced from leads the team had forgotten existed.
- +Marketing: the dormant list becomes a measurable channel, not a write-off.
- +Data quality: every reply updates the CRM record. Dormant contacts re-enter active pipeline with a fresh conversation behind them.
- +Customer engagement: the brand stays alive in the customer's phone, not buried in their unread email.
Want us to build it for you?
Reignite is the engine described in shape above. We can have your tenant of it live in 48 hours: your CRM, your voice profile, your compliance frame, your sender number. From $1,000 for the prototype, scoped engagement after.
Book a 30-min diagnose call from the Sandbox page.