IVR intelligence for voice agents

Every phone menu, mapped for your AI agents.

TurnGraph gives your voice agents the exact path through a company’s phone menu: what to press or say, what to listen for, and when to act.

Built for teams automating calls to

  • Health plans
  • Pharmacies
  • Banks
  • Insurers
  • Utilities
  • Government agencies

The problem

Phone menus weren’t built for AI agents.

They were designed for patient people. A voice agent needs to know the menu before it dials.

Timing is unforgiving

Most menus wait only a few seconds for an answer before repeating or moving on. An agent that hesitates answers the wrong prompt.

Every menu is different

Some lines list keypad options. Others open with a spoken question or accept only certain phrases. Your agent needs to know which.

Not every path leads somewhere

Some options end in a general queue or ask for account details first. Knowing the destination before you dial avoids dead ends.

Why a mapped route

Generic IVR prompts only get you so far.

Most voice agents are told to listen to the menu and pick the best option. That holds until a line wants a key within a few seconds, opens with a spoken question, or keeps the right department two menus deep. A route mapped for each number tells your agent exactly what to do, so it reaches the right person instead of failing before the conversation starts.

Generic IVR prompt

Listen to the menu and choose the option that best matches the caller’s goal.

  • Guesses at every menu, on every call
  • Misses short answer windows
  • Ends up in the wrong queue or back at the main menu

TurnGraph route for this number

As soon as you hear “For providers, press 2”, press 2 right away, without waiting for the rest of the menu.

  • The exact key or phrase for each menu
  • The sentence to wait for and how long the line waits
  • The path to the right department, checked on recorded calls

Mapping

A complete map of every menu.

We call each number, listen to every prompt, and follow each option with its own short call. Every option is stored with its key, its spoken phrase, the sentence that announces it, and where it leads.

  • Keypad and speech-driven menus
  • Menus that open with a spoken question
  • Departments, further menus, and requests for account details
Provider services Heard on the call

PromptFor claims, say claims or press 1. For eligibility, press 2. For provider enrollment, say provider enrollment or press 3. To speak with a representative, press 0.

1Claims · or say “claims”Menu
2EligibilityAsks for member ID
3Provider enrollment · or say “provider enrollment”Department
0RepresentativeNot followed
Call timeline Main menu
Line
Members · 1Providers · 2Pharmacy · 3
Agent
Press 2
0s2s4s6s8s10s12s
CueAnswer windowAgent action

Timing

The right action at the right moment.

Phone menus give callers a few seconds to respond. Every route tells your agent which sentence to listen for, so it acts the moment its cue is spoken instead of waiting out the whole menu. We measure how long each line waits too, so you can tune your platform’s turn-taking to match.

  • A cue sentence for every step
  • Measured answer windows for your turn-taking settings
  • A fallback if a key or phrase isn’t accepted

API

One request before every call.

Send a phone number, a goal and your voice platform. TurnGraph returns what the line will ask for, then every step in order: what to listen for, what to press or say, and how long the line will wait.

inputs
Everything the line will ask your agent for, such as an NPI, member ID or policy number, named from the line’s own words. Check you have each one before you dial: an unfilled variable can sink the call.
action · value
Press a key or say a phrase, and exactly which one.
listen_for
The sentence the line says right before your agent should act.
timing
When to act: after an opening question, on the option’s own cue, or once the menu finishes.
respond_within_s
How long the line waits for an answer, measured on recorded calls. Use it to tune your platform’s turn-taking settings; it stays out of the prompt, because an AI model can’t time itself.
fallback
The other way through if a key or phrase isn’t accepted.
instructions
The whole route as numbered sentences, with each input as a variable like {{npi}}, ready to paste into your agent’s prompt or a flow node.
call_variables
Where the values go on your platform’s create-call request, ready to fill. TurnGraph never sees them.
  • REST and JSON
  • Bearer-token auth
  • Versioned at /v1
Request early access →
curl -G https://turngraph.com/v1/route \
  -H "Authorization: Bearer $TURNGRAPH_API_KEY" \
  --data-urlencode "phone_number=+18005550199" \
  --data-urlencode "goal=claim status" \
  --data-urlencode "platform=bland"
200 OKapplication/jsonGET /v1/route
{
  "object": "route",
  "phone_number": "+18005550199",
  "goal": "claim status",
  "platform": "bland",
  "inputs": [
    {
      "name": "npi",
      "variable": "{{npi}}",
      "label": "NPI",
      "format": "10 digits, then #",
      "method": "press",
      "asked_at": "step",
      "steps": [2],
      "prompt": "Please enter your 10-digit NPI, followed by pound."
    },
    {
      "name": "member_id",
      "variable": "{{member_id}}",
      "label": "member ID",
      "format": "letters as *, then #",
      "method": "press",
      "asked_at": "step",
      "steps": [4],
      "prompt": "Enter the member ID, followed by pound. For letters, press star."
    }
  ],
  "steps": [
    {
      "action": "press",
      "value": "2",
      "label": "Providers",
      "listen_for": "For providers, press 2.",
      "timing": "on_cue",
      "respond_within_s": 6,
      "instruction": "As soon as you hear “For providers, press 2”, press 2 right away, without waiting for the rest of the menu."
    },
    {
      "action": "press",
      "value": "{{npi}}#",
      "label": "Enter NPI",
      "listen_for": "Please enter your 10-digit NPI, followed by pound.",
      "input": "npi",
      "instruction": "When the line asks for the NPI (“Please enter your 10-digit NPI, followed by pound”), enter {{npi}} on the keypad (10 digits, then #)."
    },
    {
      "action": "say",
      "value": "claim status",
      "label": "Claim status",
      "listen_for": "Say claim status, eligibility, or prior authorization.",
      "timing": "after_menu",
      "respond_within_s": 5,
      "fallback": { "action": "press", "value": "1" },
      "instruction": "As soon as the menu that includes “Say claim status, eligibility, or prior authorization” finishes, say “claim status”. If that isn’t accepted, press 1."
    },
    {
      "action": "press",
      "value": "{{member_id}}#",
      "label": "Enter member ID",
      "listen_for": "Enter the member ID, followed by pound. For letters, press star.",
      "input": "member_id",
      "instruction": "When the line asks for the member ID (“Enter the member ID, followed by pound. For letters, press star”), enter {{member_id}} on the keypad (letters as *, then #)."
    }
  ],
  "destination": {
    "type": "human_queue",
    "label": "a claims representative"
  },
  "confidence": 0.94,
  "verified": { "by": "call", "at": "2026-10-02T14:31:07.000Z" },
  "instructions": "1. As soon as you hear “For providers, press 2”, press 2 right away, without waiting for the rest of the menu.\n2. When the line asks for the NPI (“Please enter your 10-digit NPI, followed by pound”), enter {{npi}} on the keypad (10 digits, then #).\n3. As soon as the menu that includes “Say claim status, eligibility, or prior authorization” finishes, say “claim status”. If that isn’t accepted, press 1.\n4. When the line asks for the member ID (“Enter the member ID, followed by pound. For letters, press star”), enter {{member_id}} on the keypad (letters as *, then #).\nThis reaches a claims representative.",
  "call_variables": {
    "request_data": { "npi": "", "member_id": "" }
  }
}

Built for Vapi, Retell, Bland and more.

Ask for your platform and the route comes back in its variable syntax. Paste instructions into your agent’s prompt or a flow node once per number, then pass the values on each call. Your agent presses keys with its platform’s own keypad tool.

Vapi
{{npi}} in the prompt, values in assistantOverrides.variableValues, keys with the dtmf tool
Retell
{{npi}} in the prompt or flow node, values in retell_llm_dynamic_variables, keys with press_digit
Bland
{{npi}} in the task or pathway node, values in request_data, with ivr_mode
ElevenLabs
{{npi}} in the prompt, values in dynamic_variables, keys with play_keypad_touch_tone
Synthflow
{npi} in the prompt or flow node, values in custom_variables
LiveKit, Pipecat
{npi} filled from job metadata in your own code, or {{ npi }} in Pipecat Flows nodes

Vapi, Retell, Bland, ElevenLabs, Synthflow, Pipecat and LiveKit are trademarks of their respective owners. TurnGraph is not affiliated with them.

// Prompt: paste route.instructions. Tools: add { type: "dtmf" }.
// Each call: POST https://api.vapi.ai/call
{
  assistantId: "your-assistant-id",
  phoneNumberId: "your-phone-number-id",
  customer: { number: "+18005550199" },
  assistantOverrides: {
    variableValues: { npi: provider.npi, member_id: patient.memberId },
  },
}
In your agent’s prompt or flow node
Navigate the phone menu exactly as follows:
1. As soon as you hear “For providers, press 2”, press 2 right away, without waiting for the rest of the menu.
2. When the line asks for the NPI (“Please enter your 10-digit NPI, followed by pound”), enter {{npi}} on the keypad (10 digits, then #).
3. As soon as the menu that includes “Say claim status, eligibility, or prior authorization” finishes, say “claim status”. If that isn’t accepted, press 1.
4. When the line asks for the member ID (“Enter the member ID, followed by pound. For letters, press star”), enter {{member_id}} on the keypad (letters as *, then #).
This reaches a claims representative.

Early access

Map the lines your agent calls.

Coverage is limited during early access. Tell us which numbers matter to you and we’ll map those first.

We’ll only use your details to contact you about early access. See our privacy policy.