Demonstration · not a client result
WhatsApp and voice agents what the deliverable looks like
The structure of the deliverable for whatsApp and voice agents, how it is produced and how you accept it, with a live specimen generated from the matching free tool’s worked example. Synthetic or permitted data only.
What this page isDemonstration
- Practice
- 05 Digital solutions
- The deliverable
- 4 sectionsProduced in 5 stages, each with a review point
- Data
- Synthetic or permittedNot a client result
Demonstration of methodSynthetic or permitted data.Not a client result.
The deliverable, section by section.
What you receive, and what each part is for.
Journey design
The flow, its branches and human handoff.
DemonstrationPrototype
Working on the chosen channel.
DemonstrationLanguage review
By fluent speakers for each language used.
DemonstrationCost model
Channel and provider costs at your expected volume.
DemonstrationA live specimen.
Generated from the worked example in WhatsApp and IVR journey planner: synthetic data, real method. Change the inputs in the tool to see your own.
Demonstration · synthetic data · not a client result
Flow and failure map
- 01Choose a languageInput: buttons or menuIf no choice after 10 seconds: repeat the question.
- 02Say or pick the cropInput: speechIf speech not recognised twice: offer simpler choices.
- 03Describe the problemInput: free textIf something goes wrong (not yet defined): hand over to a person.
- 04Receive advice and a follow-up SMSInput: buttons or menuIf call drops before the advice ends: send an sms follow-up.
Journey risks
- Note: Step 2 relies on speech recognition in 3 languages.Test recognition quality in each language with real users before launch.
- Gap: Step 3 (“Describe the problem”) has no failure case.Every step needs a tested answer to “what if this goes wrong?”
- Note: 3 languages need review by fluent speakers.Machine translation is not enough for advice people act on.
- Note: Channel fees apply.WhatsApp Business and telephony providers charge per message or minute. Get current prices from your provider.
How it is produced, and accepted.
Each stage ends in something you review; acceptance is tested against criteria agreed at the start.
- 01
User need
Agree users, languages and the task.
Review pointUser needs and success measures agreed.
- 02
Scope
Scope the journey, handoff and costs.
Review pointWritten scope with acceptance criteria.
- 03
Build
Build the prototype.
Review pointWorking build demonstrated at agreed milestones.
- 04
Test
Test with users and reviewers.
Review pointAcceptance tests passed and recorded.
- 05
Handover
Hand over with the rollout options.
Review pointHandover of code, content, access and documentation.
How proof is labelled
- DemonstrationsDemonstrations use synthetic or permitted data.
- Documented experienceDocumented experience is attributed to the organisation that held the work.
- Measured resultsMeasured results are added only once they have been measured; none are shown yet.
What needs to move forward?
Tell us the decision, the challenge or the opportunity. We reply with a scoped approach, a named principal and a fee before any work begins.
No charge to submit an enquiry.
