B2B readiness assessment scenario
A growth consultancy asks about goals, role, company size, process, challenge, urgency, and readiness. The result is Low, Medium, or High readiness. High readiness gets a relevant email and booking path. Medium receives education, waits two days, then branches on engagement. Low receives a useful resource and a slower path. The record must preserve inputs, score, result, sequence state, and sales handoff.
What the test records
- How the contact enters the journey.
- Whether declared answers and the outcome remain usable.
- Whether scores or segments can trigger the sequence.
- Which answers, scores, opens, clicks, and product events can create branches.
- Waits, exits, suppression, and re-entry behavior.
- Personalization and dynamic content.
- Sales notification or CRM handoff.
- Analytics at contact, step, and journey level.
- Whether AI assists, creates once, or supports ongoing conversational edits.
- Plan restrictions and usage costs.
Ecommerce scenario
Ecommerce-first products use a separate fair test. A shopper browses a category, views a product, starts checkout, abandons, returns through a message, purchases, and exits pre-sales nurture. The record follows catalog context, consent, identity, cart state, purchase state, cross-channel messages, suppression, and attribution.
Evidence record template
| Field | Required note |
|---|---|
| Date | Exact workflow and pricing check date |
| Plan | Edition and relevant add-ons |
| Trigger | Observed or documented entry condition |
| Data retained | Fields, answers, events, scores, and state |
| Branches | Supported conditions and limits |
| Exit | Goal, suppression, and re-entry behavior |
| Handoff | Owner, CRM, notification, or booking route |
| AI scope | Capture and nurture recorded separately |
| Evidence | URL, note, screenshot, or test record |