Follow the experience.
Not just the send.

1. Customer situation

   An anonymous diagnostics organization needs an Assignment of Rights (AOR) form completed. This example begins with a form-required signal, not a customer identity.

   Customer: There is a form to complete, but I need to understand why it matters. Receive relevant guidance only through an agreed channel.

   Team: Form completion is required. Carry the requirement and Journey context into the Engagement Plan. Check the intended outcome and the permitted contact context.

2. Intended outcome

   The objective is a completed and verified Assignment of Rights form. Message delivery alone is not the objective.

   Customer: Understand the request, access the form and complete the required action. Acknowledge completion when it is confirmed.

   Team: Observe form progress, submission and verification—not an invented uplift target. Keep the observation window and completion definition explicit.

3. How the plan works

   Illustrative plan steps—Introduce, Explain and Confirm—connect wording, replies, materials and feedback. They are not the fixed Journey stages.

   Customer: Please review and complete your Assignment of Rights form. If you need help accessing it, reply to let us know. A reply keeps the current-step context attached.

   Team: Saved cohort wording, selected channel, timing and reply handling belong to the plan. AI drafting is for the cohort, not unrestricted per-person generation. Inspect communication constraints and the plan’s operating mode.

4. Control boundary

   Governance connects wording, agreed channels, opt-outs, quiet hours and frequency limits to the relevant programme context.

   Customer: Contact follows the permitted channel and timing context. I can opt out or ask for help. Only the governed plan determines the next contact.

   Team: Must say, May say and Never say constraints guide cohort wording. Drafting, approval and publishing are distinct; plan mode and review settings determine the applicable gates. This example keeps the relevant control context visible.

5. Experience response

   The person follows the permitted prompt and completes the example process. Experience Recovery is not a mandatory detour.

   Customer: “I have completed the form.” Verification and an appropriate completion acknowledgment.

   Team: Record the submission and verification context. A relevant Feedback Opportunity can follow completion. Return the permitted status and learn from the interaction.

6. Results & continuation

   Orchestration Plans connect permitted continuation and outputs back to client systems. An unresolved action remains unresolved.

   Customer: The example form is complete. A relevant Feedback Opportunity can ask about the experience. Feedback informs the next interaction.

   Team: Return permitted status, signed forms, CRM tasks or engagement insights as appropriate. Do not share individual replies or message wording as engagement insights. Outcomes can inform reviewed, versioned improvements. Adaptive promotion requires a person; Agentic plans can auto-promote a message-test winner.

The six demonstration beats are not Journey stages. The product stages are Action Required, Notified, Started, In Progress, Submitted, Verified, Completed. Blocked is a distinct status, not the inevitable step after Completed. Introduce, Explain and Confirm are illustrative plan-owned step names.