Contact
Tell us where your lifecycle stops.
Most teams build onboarding and defer the rest — at-risk and win-back go unanswered while users churn. Tell us which stages are live, which are unbuilt, and what your channels and consent rules look like. A named human reads every message.
Before you write
Getting in touch.
Who replies to my message?
A member of the PatternSix team reads and answers your message directly. There is no autoresponder standing in for a person.
What should I include?
It helps to say which lifecycle stages you run today — onboarding, activation, at-risk, win-back, expansion — which channels you use (email, in-product, messaging), roughly how many contacts you hold, and who would act as the accountable human owner for approvals and consent handling.
I only have onboarding built. Is that a problem?
No. A programme that is roughly 90% onboarding and 10% everything else is the common starting point. It is a useful place to begin the conversation, not a barrier to it.
How do you handle consent and unsubscribe for the contacts I share?
Suppression, consent state and unsubscribe are enforced as configured constraints across every operated account — not left to discretion — and every send is retained in an audit trail. Advertising and data-protection decisions remain with your accountable human owner. See the security and privacy pages for detail.
Where can I read how pricing works?
Revenue is a recurring subscription scaled to the number of active journeys and contact volume. The pricing page sets out the structure.
Prefer to read first?
See what AI colleagues operate, where the named human owner stays accountable, and how consent and suppression are enforced.