Original phone-menu writing and an explicit routing worksheet
IVR script examples with complete branches and one shared retry.
Clear options. Complete messages. A consistent next step.
Prepare the spoken words and their intended selection paths together. This guide supplies a complete original phone-menu packet: four menu options, two information messages, two recovery prompts and a neutral ending. A filled routing worksheet shows which words belong to each selection and when the example ends.
| Key | What the menu offers | Intended action |
|---|---|---|
| 1 | Collection hours | Say H, then end |
| 2 | Collection point instructions | Say P, then end |
| 9 | Hear this menu again | Say M; keep the same retry state |
| 0 | Finish | Say E, then end |
Supply the studio facts before writing the menu
Brindle Paper Studio, its adult staff and its adult callers are invented for this writing exercise. Collection hours are Tuesday and Thursday, from ten in the morning to noon, local time. The collection point is at the courtyard entrance, on the shelf beside the door marked Collection. These are the supplied facts for both information branches.
The packet has six distinct spoken blocks. Their names are worksheet labels, not words for a caller to hear. Keep those blocks together with the menu-to-message mapping so that a later wording edit does not quietly change what a key is meant to do.
Write the complete main menu
The menu names the studio and offers four choices. Each option has a matching row in the routing worksheet below. Keep “press one” connected to collection hours and “press two” connected to collection point instructions when you adapt the words.
Welcome to Brindle Paper
Studio’s information menu. For
collection hours, press one.
For collection point
instructions, press two. To
hear this menu again, press
nine. To finish, press zero.Finish both information branches
Hours block H, selected by key 1: “Collection hours are Tuesday and Thursday, from ten in the morning to noon, local time. Goodbye.”
Collection point block P, selected by key 2: “The collection point is at the courtyard entrance, on the shelf beside the door marked Collection. Goodbye.”
After either complete block, the example ends. Each message already includes its own goodbye, so it is not followed by the neutral ending or another menu. The collection point wording identifies a place; it does not say that a caller has walked there or collected anything.
Give no input and an unlisted key different first prompts
No-input block N: “No selection was received. Please choose from the menu.”
Unlisted-key block U: “That selection is not listed. Please choose from the menu.”
Neutral ending block E: “Thank you for calling Brindle Paper Studio. Goodbye.”
On the first failure, use the prompt that matches the event and then replay the complete menu. Key 0 uses the neutral ending directly. A second failure also uses only that neutral ending and ends, rather than adding another recovery prompt.
Track one shared retry across both failure types
Start by saying M and entering R1, meaning one automatic retry remains. R0 means that retry has been used. In the worksheet, “empty” means no selection was received; no waiting duration is specified. “Other” means a key outside 1, 2, 9 and 0. Empty and other share the same allowance, rather than receiving one retry each.
The Say column uses the six block labels: M for menu, H for hours, P for collection point, N for no input, U for unlisted key and E for neutral ending. “N then M” and “U then M” mean two complete blocks in that order. END is terminal: no further input or spoken block follows it. The worksheet itself is not spoken text.
For a mixed path, begin with M. An empty selection gives N then M and moves to R0. A valid 9 says M again and stays at R0. An unlisted 7 now gives E and ends. If the first failure had instead been 7, a subsequent valid 1 would still give H and end.
A valid 9 preserves whichever retry state is current. It neither consumes an unused retry nor restores a used one. Someone who repeatedly chooses 9 can continue replaying the menu under this authored policy; the worksheet does not impose a maximum call length.
State Key Say Next
R1 1 H END
R1 2 P END
R1 9 M R1
R1 0 E END
R1 empty N then M R0
R1 other U then M R0
R0 1 H END
R0 2 P END
R0 9 M R0
R0 0 E END
R0 empty E END
R0 other E ENDRepair a wrong branch while keeping the menu intact
Suppose a draft worksheet sends key 2 to H, then END. That is a mismatch: the spoken menu offers collection point instructions for 2, but the row supplies hours. Replace the key-2 row in both R1 and R0 with P, then END. The menu wording can stay unchanged.
The complete accepted key-2 message is repeated below so the correction can be reviewed as a finished branch. It replaces the misrouted hours message; do not append the hours or another menu after it.
The collection point is at the
courtyard entrance, on the
shelf beside the door marked
Collection. Goodbye.Keep the writing packet separate from a configured phone application
Twilio’s official phone-tree tutorial describes phone-tree logic handled in an application. Its Gather reference distinguishes collected input from a no-input path. Those references help explain why a script needs explicit input branches; the one-shared-retry rule in this example is an original planning choice, not a vendor default.
For another writing option in ordinary Honeyline character Chat, supply the brief, six blocks and intended flow. Review the actual reply and keep the wording you accept yourself. If supplied-text narration is a later task, prepare the chosen block’s complete spoken words separately from the routing worksheet. An actual phone application and its input handling require separate configuration and review.
References for the phone-application boundary
The references describe configured phone applications and input behavior. Brindle Paper Studio, all six spoken blocks, the worksheet and the one-shared-retry policy are original writing material. No phone application was configured or tested for this guide.
Frequently asked questions
What belongs in an IVR script example?
Include the complete spoken menu, a matching message or action for every offered key, clear endings and a stated recovery policy. This example supplies six spoken blocks and twelve routing rows across two retry states.
Why separate no input from an unlisted key?
They describe different events: no selection was received, or the selection was outside the offered keys. The first failure gets its matching N or U prompt and then the full menu. Both events use the same one-retry allowance.
Does pressing 9 reset the retry allowance?
Not in this authored example. Key 9 replays the menu and keeps R1 or R0 unchanged. Repeated valid replays are allowed; the script makes no maximum-duration promise.
Can a valid information choice still work after the retry is used?
Yes. In R0, key 1 still gives the complete hours message and key 2 still gives the complete collection point message, then each ends. The used allowance affects a further empty or unlisted selection, which gives the neutral ending.
Is one shared retry required by Twilio?
No. It is the policy supplied for this original writing exercise. The linked documentation concerns configured phone applications and input handling; it does not prescribe this example’s retry count or wording.
Does this Honeyline writing workflow set up a phone menu?
No. The workflow described here prepares words and a flow for manual review. It does not configure a phone service, route keypad selections or demonstrate a working call. Keep any later phone implementation separate from the accepted writing packet.
Keep the words and the intended flow together.
Review each menu option against its complete branch. Keep the spoken script separate from worksheet labels and implementation notes.