ZenotiHelp

Configure a phone tree (ivr)

ZTZenoti Docs Team Updated September 23, 2026 7 min readHow-to

A phone tree (IVR) is the automated menu system callers hear when they dial your center. It routes callers to the right person or service without requiring a live agent to answer every call. For example, "Press 1 for Appointments, Press 2 for General Inquiries." Configuring an effective phone tree reduces wait times and ensures callers reach the right department.

A phone tree (also called an IVR) is an automated menu system that greets callers and routes them based on their selections. You build a phone tree by arranging nodes in a flow. Each node performs an action, such as playing a greeting, presenting a menu, or transferring the call.


On this page


Before you begin

Permissions: Go to Configuration > Security > Security Roles > select a role > scroll to the Zenoti HyperConnect section. Enable Connect Access Enable and any feature-specific permissions your team needs.

  • HyperConnect voice must be provisioned and enabled for your center.
  • Plan your call flow before you start building. Decide which menu options callers need and where each option should route.

Steps

Create a phone tree flow

  1. Open HyperConnect and click the Settings icon.
  2. Select the Voice tab.
  3. In the Phone Tree section, click Manage.
  4. Click Create New and select from the available options:
  • Create from scratch β€” build a new phone tree flow from a blank canvas
  • Use a template β€” start from a pre-built phone tree template. Two templates are available: Template-Standard flow (greeting + menu β€” the most common IVR pattern) and Template-Missed call flow (rings multiple users then routes to voicemail)
  • Duplicate existing β€” copy an existing phone tree flow as a starting point

Add nodes to the flow

Build your phone tree by adding nodes. Each node type performs a specific action.

Node type Description Key configuration
Welcome Greeting Plays an audio greeting when the caller connects. Typically the first node in a flow. Choose Say (text-to-speech) or Play (upload an MP3 audio file, max 5 MB). Enter greeting text or upload your audio file.
Menu Presents options mapped to keypad digits (for example, "Press 1 for Appointments, Press 2 for General Inquiries"). Map each DTMF key (0–9) to a downstream node. Configure the menu prompt text or audio. Set a timeout for no-input and a maximum number of retries.
Transfer Call Routes the call to a specific employee or extension. Select the target employee or enter an external phone number. Optionally assign a routing template.
Voicemail Directs the caller to leave a voicemail message. Configure the voicemail greeting (pre-set or custom upload). Set Number on loop β€” how many times the greeting plays before recording starts. Set the maximum recording duration. Choose whether the message goes to the center or to specific agents; if you choose specific agents, select at least one.
SMS Sends a text message to the caller (for example, a booking link). Enter the SMS message text. The system sends the message to the caller's phone number and continues the flow.
Play Audio Plays a recorded audio message to the caller. Upload an MP3 audio file (max 5 MB) or enter text for text-to-speech playback.
Operational Hours Branches the flow based on whether the call arrives during or outside business hours. Configure two branches: During business hours and Outside business hours. Uses the center's configured business hours schedule.
AI Receptionist Connects the caller to the AI voice agent for automated handling. Configure the first message (greeting text), after-hours greeting, handover type (Manual or Automatic), handover messages, knowledge base (upload PDF/DOCX/HTML/TXT files and add web links), and pronunciation dictionaries. See details below.
Call Queue Places the caller in a queue until an agent becomes available. Configure hold music, queue position announcements, maximum wait time, and agent assignment mode (manual or automatic). See Set up call queuing.
SmartBot Hands off the caller to SmartBot for automated text-based interaction. Select the SmartBot configuration for this center. The caller interacts with SmartBot via voice-to-text.
Call Percentages Splits callers across different branches based on configured percentages. Set percentage allocations for each branch (must total 100%). Useful for A/B testing call flows.

Number on loop is required, not optional. Welcome Greeting, Menu, Voicemail and Play Audio nodes all need it. If you leave it blank, the node shows an Invalid configuration detected: warning on the canvas listing Number on loop, and the flow can still be saved in that state β€” so a tree with every node in place can still be misconfigured. Check each node for the warning before you rely on a new flow. A value of 1 plays the prompt once. | Conditional Routing | Routes callers down different branches based on caller attributes. | Select a routing condition: New Guest (unrecognized caller), Existing Guest (matched to a guest profile), Forwarded Source, Forwarded Number, or Guest Country Code. Configure a branch for each matching outcome. | | Hang Up | Ends the call gracefully. Use this node to terminate a phone tree branch after a message or voicemail. | No configuration required. Place at the end of any branch to disconnect the caller cleanly instead of leaving them in silence. |

  1. Select the flow you created.
  2. Click Add Node.
  3. Select the node type.
  4. Configure the node settings using the parameters described in the table above.
  5. Click Save.
  6. Repeat to add more nodes and build the complete flow.

Tip: Start with a Welcome Greeting node, then add a Menu node with options that branch to Transfer Call, Voicemail, Call Queue, or AI Receptionist nodes. Use Conditional Routing to handle new vs. returning callers differently.

Configure the AI Receptionist node

The AI Receptionist node connects callers to the AI voice agent for automated handling. Configure the following settings:

  1. Add an AI Receptionist node to your flow.
  2. Enter the First message β€” the greeting the AI agent speaks when the caller connects (for example, "Hi, thanks for calling. How can I help you today?").
  3. Optionally enter a First message after business hours β€” an alternative greeting used outside business hours.
  4. Set the Handover type:
  • Manual β€” The AI agent asks the caller before transferring to a human agent.
  • Automatic β€” The AI agent transfers immediately when it cannot resolve the request.
  1. Configure Handover messages:
  • Inside business hours message β€” Spoken to the caller before transferring during business hours.
  • Outside business hours message β€” Spoken before transferring outside business hours.
  • Take note messages β€” Spoken when the AI agent takes a message instead of transferring (separate messages for inside and outside business hours).
  1. Optionally enable Handover outside hours and enter a Handover phone number for after-hours call transfers.
  2. Select Handover employees β€” the employees who can receive transferred calls from the AI agent.
  3. Enter Handover instructions β€” internal guidance for the AI agent on when and how to escalate calls.
  4. Upload Knowledge base files (PDF, DOCX, HTML, or TXT) and add web links that the AI agent searches to answer caller questions.
  5. Optionally upload Pronunciation dictionaries to define custom pronunciations for brand names, service names, or industry-specific terms.
  6. Click Save.

Configure the Operational Hours node

The Operational Hours node routes callers differently based on your center's business hours.

  1. Add an Operational Hours node to your flow.
  2. Configure the During business hours branch (for example, route to a Menu node with agent options).
  3. Configure the Outside business hours branch (for example, route to a Voicemail node or play a closed message).
  4. Click Save.

Configure the Conditional Routing node

The Conditional Routing node directs callers down different branches based on caller attributes.

  1. Add a Conditional Routing node to your flow.
  2. Select the routing condition:
  • New Guest β€” Routes callers whose phone number does not match any existing guest profile.
  • Existing Guest β€” Routes callers whose phone number matches an existing guest profile.
  • Forwarded Source β€” Routes based on the source from which the call was forwarded.
  • Forwarded Number β€” Routes based on the specific phone number from which the call was forwarded.
  • Guest Country Code β€” Routes based on the country code of the caller's phone number.
  1. Configure a branch for each matching outcome (for example, route new guests to a Welcome Greeting and existing guests directly to a Menu).
  2. Click Save.

Publish the phone tree

Publishing a phone tree makes it active for incoming calls. Only one phone tree can be published at a time for a center.

Warning: Publishing immediately makes the phone tree live for all incoming calls to your center. Test your flow thoroughly before publishing during business hours. A misconfigured Transfer Call or Menu node could misdirect every caller. If possible, publish during off-hours and verify by calling your center number.

  1. Open the phone tree flow you want to activate.
  2. Click Publish.

Note: The system updates the call routing to use the published flow.

To stop using a phone tree, click Unpublish. Incoming calls revert to ringing directly to available agents.

Current limitations

  • The phone tree cannot yet automatically distinguish new vs. existing guests by name in greetings. Use the Conditional Routing node with "New Guest" / "Existing Guest" conditions for different routing, but personalized name greetings are not supported.
  • Phone tree design is limited to the 13 widget types listed above. Custom widget types cannot be created.

Edit or delete nodes

  1. To edit a node, select it in the flow and update its settings. Click Save.
  2. To delete a node, select it and click Delete.

Delete a phone tree flow

  1. If the flow is currently published, unpublish it first.
  2. Open the flow you want to delete.
  3. Click Delete Flow.
Was this article helpful?
Your feedback helps us improve our documentation.