Lifecycle and Email
SMS and WhatsApp lifecycle
Within Lifecycle and Email, this is the piece that use the channels people answer, with the restraint they demand.
What does this work cover?
Use the channels people answer, with the restraint they demand. In practice that means consent captured properly per channel, which is a legal requirement rather than a nicety, and then the harder half: timing rules that respect time zones and quiet hours, because the cost of getting this wrong is permanent.
Why this work exists
The work looks administrative from the outside. It decides how much of everything else actually lands.
Lifecycle and Email is the wider programme; this is the piece that gets scoped first more often than any other.
The nearest piece of work to it is building the welcome sequence most businesses never finish. Where that is already handled, this moves faster than the estimate; where it is not, the two get done together or neither of them holds.
What good looks like
A good outcome here is boring: no contradictions, no gaps, nothing that needs explaining.
The gap between that and where most accounts start is why this is scoped as SMS and WhatsApp lifecycle rather than as a line inside something larger. Working out whether low open rates are a subject line or a deliverability problem is the usual second step once it is in place.
When this is the right work
You can tell this is the constraint when:
- You have phone numbers and no programme
- An SMS went out at the wrong hour and the opt-outs told you
- WhatsApp is used for support and never for lifecycle
If none of those is true, something else is probably the constraint, and the Lifecycle and Email overview maps the alternatives. The usual neighbours are getting the abandoned basket flow to stop annoying people who already bought and deciding which segments are real and which are wishful.
What the work covers
The constituent pieces:
- Consent captured properly per channel, which is a legal requirement rather than a nicety. This is the piece a client can verify themselves, which matters more than it sounds.
- Timing rules that respect time zones and quiet hours, because the cost of getting this wrong is permanent, with the evidence kept so the decision can be defended later.
- Message selection: only the ones worth interrupting somebody for. Boring, necessary, and the first casualty when a deadline moves.
- WhatsApp template approval and the session window, which govern what you can send and when. Usually scoped at half the size it turns out to be.
How it runs
The running order, which matters more here than it does elsewhere.
Proving it in one place first
Changes get made to a small, representative slice and measured there before being applied everywhere. It is slower for three weeks and faster for the rest of the year.
Clearing the contradictions
Where two systems disagree about the same fact, that gets settled before anything is built on top of either of them.
Setting the review rhythm
How often this gets looked at again, and by whom, is agreed now rather than left to whoever notices first.
What each part runs into
Each part meets a different obstacle depending on the market it is done in:
- Consent captured properly per channel, which is a legal requirement rather than a nicety – in Chandigarh, complicated by the fact that a buying pattern that resolves faster than the reporting cycle
- Timing rules that respect time zones and quiet hours, because the cost of getting this wrong is permanent, which in Manchester runs into a sector mix that pulls the brief in several directions
- Message selection: only the ones worth interrupting somebody for: the Chicago version of this has to deal with a seasonal peak that arrives before the content is indexed
- WhatsApp template approval and the session window, which govern what you can send and when, where a Vancouver engagement contends with a reporting line that averages away the market in question
The avoidable version of this
Treating SMS as cheap email. It reaches a lock screen, and the tolerance for a low-value message is close to zero.
Naming it upfront is the difference between a result and a report about effort.
How it is measured
Opt-out rate per message type, and revenue per message sent. That measure is agreed before the work starts, so there is no argument about the result afterwards.
The point of the number is to settle an argument, so it is chosen for being hard to dispute rather than for being flattering.
What you end up with
The concrete artefact is a channel plan with consent handling, approved templates, and rules on what is allowed to interrupt.
Given with the raw working attached, so the conclusion can be re-derived.
How it differs by sector
By sector, the same scope produces different priorities:
- In SaaS and technology the binding constraint is that product-led companies where the buyer self-educates and the trial is the sales call.
- Home and trade services: the thing that changes the scope here is that emergency intent, service-area geography, and a phone that has to be answered.
- For Travel and hospitality, aggregators hold the demand, so direct booking depends on being the specific named property. and that shapes how far this can go.
The industry pages carry the rest of that detail. SaaS and technology and Home and trade services are the two where this piece of work most often decides the outcome.
Common questions
How often can we send SMS?
Less often than you want to. Each message should clear a bar of being worth a buzz in somebody’s pocket.
Is WhatsApp better than SMS?
In markets where it is the default messaging app, yes, with stricter rules. Templates need approval and the session window limits when you can respond freely.
Does anything need doing before SMS and WhatsApp lifecycle?
Sometimes. The signals above are the honest test, and where something upstream is the real constraint we will name it even though it is not the work on this page. Home and trade services is the part that scales. Legal and professional services is the part that never will.
Is there a minimum worth doing?
There is a point below which the measurement cannot detect a change, and we would rather say so than take the work. Opt-out rate per message type, and revenue per message sent has to be able to move for the engagement to mean anything. The common mistake is covered in Content and Editorial; the expensive one in Conversion Rate Optimization.
Does this have to be bought separately from Lifecycle and Email?
No. It is usually part of a wider Lifecycle and Email engagement, and it is described separately because it is the piece clients most often ask about by name. It can also be scoped on its own where that is genuinely what is needed, and we will say which applies after looking. The definition is in First-party data or Third-party data. The practice is in GA4 or Matomo.
Ask about sms and whatsapp lifecycle
Write what you would say on a call. The reply will be the same thing we would have said.
Get the two or three things that matter
We will tell you if the answer is that you do not need us yet. That happens often enough to be worth saying out loud.