Solutions
Message the person, not the schedule
Your contacts receive lifecycle messages that respond to real product behaviour, within the consent state they set. AI colleagues operate the sends; a named human owner approves what reaches them.
How a contact moves through the lifecycle
The person on the other end
A contact is not a row in a list. It is a person who signed up, tried the product, and is deciding whether to stay. PatternSix treats each contact as a governed object, with a consent state and preferences the system reads before it decides anything.
Whether to message this person now, with what, and why is the judgement the lifecycle programme exists to make well — and to record.
Messages that answer behaviour
Most deferred programmes send on a fixed clock. A contact gets day-three and day-seven emails regardless of what they did in the product. AI colleagues move your sequences to behaviour-based triggers driven by product-usage signals, so a message lands in response to real activity rather than an arbitrary timer.
The stages a contact rarely hears from
Teams we speak to describe a split of roughly 90% onboarding and 10% the rest of the lifecycle. The at-risk and win-back stages — where a disengaging contact could still be recovered — go unattended, and users lapse without any intervention. AI colleagues operate those recovery journeys on disengagement signals, so the later stages stop going quiet.
What a contact can rely on
When a person opts out or withholds consent, that state is enforced as a constraint checked before every send; no model judgement can override it. Every send is retained with a full account of what was sent to whom and why, giving the accountable owner an auditable basis for oversight and the contact a programme that respects the choices they made.
What sits behind each message to a contact
Segmentation from real usage
AI colleagues place each contact into segments from how they signed up and how they behave in the product, so a message targets where a person actually is in the lifecycle rather than reaching an entire list at once.
Contact preferences honoured
Each contact's consent state and unsubscribe choice are read as configured constraints, not left to discretion. Advertising and data-protection decisions stay with the accountable human owner.
Full lifecycle, one contact record
Onboarding, activation, at-risk, win-back and expansion all operate against a single contact across email and in-product channels, so stages connect instead of running as disconnected campaigns.
Copy drafted, then approved
AI colleagues draft and revise the copy each stage needs; they do not publish it. A named human owner approves every template before it reaches a contact, keeping brand voice under human control at the point of contact.
Questions about how contacts are messaged
Do messages fire on a schedule or on behaviour?
Behaviour-based triggers are the default. AI colleagues drive sequences from product-usage signals, so a contact hears from you in response to what they are actually doing, not a fixed day count. Time-based steps are used only where a stage genuinely calls for one.
How is opt-out enforced?
Opt-out and consent state act as a hard filter applied before a message is scheduled, not a preference the system weighs. A contact who has withdrawn consent is removed from eligibility at that gate, and no model output can put them back.
Which channels reach my contacts?
Two: email and in-product. PatternSix operates owned-channel messaging and does not undertake paid acquisition, so the programme stays inside channels your contacts already have a relationship with.
What data decides who receives a message?
Eligibility is decided in two separate layers. What a contact does in the product shapes which segment and trigger they match, and their consent state decides whether they can be messaged at all — the second check governs the first.
Will AI-drafted copy sound like our brand?
AI colleagues draft and revise the copy; they do not publish it. A named human owner approves every template before it is deployed, so brand voice stays under human control at the point it reaches a contact.
What can I show about a specific send?
The send-level audit trail records what was sent, to whom and why. That gives the accountable owner a defensible basis for oversight and answers a contact query or a reviewer with the actual record.
Do you cover at-risk and win-back contacts?
Yes. AI colleagues monitor engagement and usage signals to detect at-risk and lapsed contacts, then trigger targeted recovery journeys — the high-value stages under-resourced teams routinely skip.
Who signs off changes to what contacts receive?
The accountable human owner approves messaging templates, consent-handling rules and any material change to journey logic before it goes live. AI colleagues iterate on non-material timing and variants within those approved bounds.
See these controls running in the product
Walk the modules that act on a contact, and the human control points that govern them.