Connect Twilio (Studio IVR + Programmable Voice)

A step-by-step guide with pictures, from the Speakvora agent's own Connect tab.

Short answer: This connects your own Twilio account to your Speakvora agent. Then a customer can text where is order 1234 and get the answer in seconds, and the agent can send status and tracking texts. The agent only reads. It can never create, change or delete anything in Twilio. Only the status word and the order number are.

Every key, number and name in the pictures is a made-up example. Nothing here asks you to share a real key with anyone but the app on your own computer.

This connects your own Twilio account to your Speakvora agent. Then a customer can text *where is order 1234* and get the answer in seconds, and the agent can send status and tracking texts. The agent only reads. It can never create, change or delete anything in Twilio. Only the status word and the order number are ever texted back, never names, prices, items or addresses.

TIP: You need about 15 minutes, a computer, and the sign-in for your Twilio account (the owner or a manager). You can't break anything: if a step does not work, nothing has changed and you can just try again. The keys and screens below are made-up examples.

NOTE: This guide was written from Twilio's public developer documentation (the addresses and sign-in style were read there) and has not been tried yet on a live Twilio account. If a screen looks different from what is described, press Connect, then Download report, and send it to support. We fix it for everyone.

Who this is for: ivr phone menus. How Twilio gives access: You create the key yourself in your own account; no approval is needed. What it costs you: Twilio API keys are free to create. Studio executions and calls are billed per Twilio pricing; reading them has no separate fee that the sources read state.

Part 1. Get your key from Twilio

Do this on your computer, in a new browser tab, signed in to Twilio.

  1. Sign in to the Twilio Console as an account owner or admin.
  2. Open [[Account > API keys & tokens, and press Create API key]].
  3. Name it Speakvora, choose key type Standard (use Main only if Twilio refuses Studio reads), and press Create.
  4. Copy the API Key SID (starts with SK) and the Secret now; the secret is shown only once.
  5. Open Studio from the left menu and open the flow that runs your phone menu.
  6. Copy the Flow SID (starts with FW) from the flow's address or settings.
  7. Paste the Flow SID, API Key SID and Secret into Speakvora.

WARNING: If Twilio asks which permissions to give, tick only the read-only ones: Standard API key (read of Studio flows and executions). Never give write or admin access.

TIP: To copy the key, click inside the box that shows it, press Command + C on a Mac or Ctrl + C on Windows (or right-click and choose Copy). Nothing will look different. It is now in your clipboard, ready to paste. Keep it private: anyone who has it can read your orders.

Part 2. Open the Connect tab in your agent

  1. Open your agent's dashboard (the page you open from the Start Speakvora Agent file).
  2. Press Connect in the menu. On a phone the menu is the bar along the top; slide it sideways if you do not see Connect.
  3. Step 1: press Connect (1)

  4. Under Your apps type Twilio in the box that says Find an app (1), or scroll down the list.
  5. Step 2: the Find an app box (1)

  6. Press Twilio (Studio IVR + Programmable Voice). A card slides up. (If you only see apps for your own kind of business, that is on purpose: your agent only shows the systems that make sense for it.)
  7. Step 3: an app's card. The Full Guide button (1) opens this page.

Part 3. Paste it in

3 boxes to fill in. Click inside a box, press Command + V on a Mac or Ctrl + V on Windows, then move to the next:

  1. Studio Flow SID. Studio, open your flow, the Flow SID (starts with FW) is shown in the flow's settings and in its web address.
  2. API Key SID. Starts with SK. Shown when you create the API key in the Twilio Console.
  3. API Key Secret (secret: it stays on this computer and is never shown again, only the last few characters). Shown only once when the API key is created. Copy it then.
  4. Part 3: each numbered box is one thing to paste. These are made-up examples.

TIP: Pasted by mistake into the wrong box? Click the box, press Command + A (Ctrl + A on Windows) to select all, then paste again.

Part 4. Test it

  1. Press the orange Save and test button.
  2. Twilio is asked for one harmless record, just to prove the key works. Nothing is changed in Twilio.
  3. Part 4: the green message under the buttons means it worked (1)

YOU SHOULD SEE: green words starting with Connected.

WARNING: Red words mean it did not work yet. Read them, then see If something is wrong below. Nothing bad happened.

What happens next

  • A customer texts something like where is order 1234. The agent answers *Your order 1234 is preparing.* (the status word from Twilio), or *I could not find that order. A team member will check and reply.*
  • Each person can ask five times an hour. If Twilio is down, the conversation carries on and the problem is written to Activity.
  • Mode: the agent asks Twilio when a customer asks.

If something is wrong

  • It says the key was refused (401 or 403): copy the key again from Twilio. Make sure there is no space before or after it, and that it is a live key for the right shop or location.
  • It cannot find an order (404): the number is not in Twilio, or Twilio uses a longer number than the one on the receipt.
  • It says too many requests (429): wait a minute and press Save and test again.
  • Twilio says you need a plan or approval: Reads one Studio Flow execution by its SID (starts with FW...). Status is only active or ended. Call-level status (queued, ringing, in-progress, completed, busy, failed, no-answer, canceled) is on the Voice Call resource at api.twilio.com/2010-04-01/Accounts/{AccountSid}/Calls/{Sid}.json, which this spec does not use. Basic auth with an API key is documented by Twilio's Studio and Call pages; the Standard key type is not stated to be enough for Studio, so a Main key may be needed.
  • Still stuck? Press Connect, then Download report, and email it to support. It never contains keys or customer messages.

If your plan has no API

  • Export call and execution logs from Twilio Console, Monitor, Logs.

Twilio's own instructions: https://www.twilio.com/docs/studio/rest-api/v2/execution

All help guides · Every agent feature · AI receptionist by industry

Questions

What if this happens: It says the key was refused (401 or 403)?

copy the key again from Twilio. Make sure there is no space before or after it, and that it is a live key for the right shop or location.

What if this happens: It cannot find an order (404)?

the number is not in Twilio, or Twilio uses a longer number than the one on the receipt.

What if this happens: It says too many requests (429)?

wait a minute and press Save and test again.

What if this happens: Twilio says you need a plan or approval?

Reads one Studio Flow execution by its SID (starts with FW...). Status is only active or ended. Call-level status (queued, ringing, in-progress, completed, busy, failed, no-answer, canceled) is on the Voice Call resource at api.twilio.com/2010-04-01/Accounts/{AccountSid}/Calls/{Sid}.json, which this spec does not use. Basic auth with an API key is documented by Twilio's Studio and Call pages; the Standard key type is not stated to be enough for Studio, so a Main key may be needed.

What if this happens: Still stuck??

Press Connect, then Download report, and email it to support. It never contains keys or customer messages.