A customer journey is the full sequence of interactions a person has with a business, from first awareness through purchase, onboarding, support, and renewal or exit. For communications teams, the journey matters because each stage has different message types, urgency levels, and channel requirements, and treating them as one undifferentiated stream produces both over-contact and missed handoffs.
The standard stages
Most frameworks divide the journey into five stages: awareness, consideration, purchase, retention, and advocacy. Some add onboarding as a distinct stage between purchase and retention. The labels matter less than the property each stage shares: the customer's intent and tolerance for contact change as they move through it. An awareness-stage recipient has not consented to transactional messages; a support-stage recipient expects fast, thread-aware responses, not campaign-style sends.
Why communications planning needs the journey map
Channel selection rules differ by stage. During awareness and consideration, paid or opted-in marketing channels are appropriate: email, RCS, WhatsApp opt-in, or click-to-message ad entry points. During purchase and onboarding, transactional channels dominate: order confirmations, OTP verification, delivery updates. During retention and support, inbound responsiveness matters more than outbound volume. Orbit's Omnichannel channel selection matrix and the Channel fallback matrix for WhatsApp, RCS, and SMS give a per-stage decision structure rather than a global channel preference.
Consent and quiet-hours rules also attach differently by stage. Marketing sends must respect consent and regional quiet-hours windows; transactional messages are typically exempt from marketing consent but still carry deliverability obligations. Mapping stages explicitly prevents the common failure where a support message is treated as a campaign send and suppressed, or where a campaign send is misclassified as transactional. Orbit covers the timing side in SMS send-time optimization and quiet hours, and the quiet-hours configuration guide walks through setting the policy document in the dashboard.
A touchpoint-to-channel map, worked
The mapping above reads as rules; this is what it looks like filled in for a typical messaging program. Each row is one touchpoint a customer actually receives, with the consent class that governs it and the fallback path when the primary channel cannot deliver:
| Stage | Touchpoint | Channel | Consent class | Fallback |
|---|---|---|---|---|
| Awareness | Click-to-message ad reply | WhatsApp opt-in | Marketing | RCS, then email |
| Consideration | Abandoned-cart reminder | RCS | Marketing | SMS |
| Purchase | Order confirmation | SMS | Transactional | |
| Onboarding | OTP verification | SMS (Verify API) | Transactional | Voice call |
| Retention | Delivery status update | Transactional | SMS | |
| Support | Inbound case reply | Inbound thread | Service | Same channel the customer used |
Two properties of the table matter more than the specific channels. First, the consent class travels with the touchpoint, not the channel: an order confirmation sent over SMS is transactional, while the same SMS pipe carrying a promotion is marketing. Second, the fallback column is part of the journey design, not an operational afterthought — the fallback chains guide covers the channels[] ladder shape, and the pre-launch readiness guide explains how the dry-run preview probes every step of that ladder before a campaign goes live, so a broken fallback fails at review time rather than mid-send.
Measuring each stage
Different stages need different instrumentation. Awareness and consideration are measured through acquisition attribution and reply rates. Purchase and onboarding are measured through delivery and read rates on transactional sends. Retention is measured through support response times, resolution rates, and post-interaction surveys, which Orbit covers in Voice-of-customer surveys over SMS and WhatsApp and Voice of customer and CXaaS. A single blended metric across all stages hides where journeys break.
A minimal journey map for a messaging program
- List the five stages and name the messages your customers currently receive at each one.
- Assign a channel and a consent class (marketing or transactional) to each message.
- Define the fallback path when the primary channel fails, using the fallback matrix rather than ad-hoc retries.
- Attach one metric per stage and review the map quarterly alongside your compliance posture review.
This definition closes a gap in Orbit's glossary, where the customer-journey concept previously had no standalone page despite being implied throughout omnichannel and conversational-experience content. Once the stages are explicit, channel selection, consent classes, and metrics stop being platform settings and start being journey design.
Frequently asked questions
What is a customer journey in a communications context?
A customer journey is the full sequence of interactions a person has with a business — awareness, consideration, purchase, onboarding, retention, and advocacy or exit. For a communications team it is a planning structure: each stage carries different message types, urgency levels, consent rules, and channel requirements, and treating the whole stream as one undifferentiated send queue produces both over-contact and missed handoffs.
How many stages should a messaging program map?
Five is the standard division — awareness, consideration, purchase, retention, advocacy — with onboarding sometimes split out as a sixth stage between purchase and retention. The count matters less than the property each stage changes: the customer's intent and tolerance for contact. Map the stages where those properties genuinely shift; merge any two stages where the messages, consent class, and channels are identical.
Does the consent class belong to the channel or the message?
The message. A single channel carries both classes: an order confirmation over SMS is transactional, a promotion over the same SMS pipe is marketing and must respect consent collection and quiet-hours windows. This is why the minimal mapping assigns the consent class per touchpoint rather than per channel — misclassification at this layer is what produces a suppressed support message or a campaign send treated as transactional.
What is the minimum viable journey map for a messaging program?
Four steps: list the stages with the messages customers currently receive at each one, assign each message a channel and a consent class, define the fallback path per touchpoint using the fallback matrix rather than ad-hoc retries, and attach one metric per stage. Review the map quarterly. A map that fits on one page and gets reviewed beats a comprehensive one that does not.