Voice: control the first turn and how numbers are read
T
Thomas Mueller
User story
As an agency, I want to control what the voice employee does right after the greeting and how it reads numbers, so that calls start naturally and booking numbers are understandable.
Problem / context
Right after the greeting the employee immediately asks whether to use the caller's phone number (last 4 digits) instead of pausing. Long booking numbers are read as a jumble ("TEST 197 167 311 72 DI 311 X"). Interruption markers end up in transcripts. Calls started from the app's CALL button are not stored.
Acceptance criteria
- Setting: "wait for caller after greeting" (no automatic first turn).
- Setting or SSML-like hint to read IDs digit by digit / in groups.
- Interruption markers are not written into the transcript shown to users.
- Every call, including those started from the app CALL button, is stored as a call activity.
Log In