What we do
Tools
Industries
Department
How we workLet's talk →
Home/Twilio/Twilio Studio
Twilio

Twilio Studio: How Flows Start, Which Widgets Matter, and Where They Stop

Twilio Studio is a canvas for building call menus, SMS bots and chat flows out of widgets instead of code. A first flow takes an afternoon. Most of the trouble comes later, from a handful of limits and from the moment a flow needs data that lives in your own systems.

Studio in short

What starts a flow: an incoming call, an incoming message, a Conversations event, a REST API request from your system, or a webhook. Each run is called an execution.

What you build with: widgets such as Send & Wait For Reply, Gather Input On Call, Split Based On, Make HTTP Request, Run Function and Connect Call To.

What goes live: only the published revision. Edits stay in draft until you publish, and test users you list on the Trigger widget run the draft.

What it costs: a per-execution fee with a free monthly allowance, plus the normal Twilio rates for the texts, calls and Functions the flow uses.

The limits that end flows early

An HTTP call that takes longer than 10 seconds

How you'll know: The flow takes the fail path at random, usually at busy times.

Fix: Make HTTP Request and Run Function both stop waiting after 10 seconds. Make the endpoint answer fast, and do slow work after replying.

A retry loop that runs too often

How you'll know: "Sorry, I didn't get that" a few times, then the conversation simply stops.

Fix: An execution ends if one widget runs 10 times in a row, or after 1,000 steps in total. Count retries in a variable and route to a person after two or three.

Each reply starts a fresh conversation

How you'll know: The customer answers your question and gets the opening greeting again.

Fix: The flow is sending from a Messaging Service SID. Send from the phone number itself so replies return to the waiting execution.

REST API triggers rejected for some customers

How you'll know: Your system starts a flow for a contact and Twilio refuses it.

Fix: A contact can only be in one REST-triggered execution at a time. End the old one, or check before starting another. Outbound starts are also rate limited, so queue bulk sends.

Fixed it, but nothing changed

How you'll know: Your test works and customers still get the old flow.

Fix: You're a test user running the draft. Publish the revision.

A first SMS flow that checks something real

  1. 1

    Create the flow

    Studio Flows Create new Flow

    Start from scratch or a template. The canvas opens with a Trigger widget that has one connector per way the flow can start.

  2. 2

    Ask the question

    From Incoming Message, add Send & Wait For Reply: "Reply with your order number." The flow pauses until the customer answers or the wait times out.

  3. 3

    Look it up

    Add Make HTTP Request pointing at your own endpoint, passing the reply. A JSON answer can be read in later widgets through the widget's parsed response.

    Watch for: the 10-second timeout. If your system can't answer by then, the widget takes its fail path.

  4. 4

    Branch on the answer

    Add Split Based On to send different replies for shipped, delayed or not found, and a Connect Call To or handoff step for anything a person should handle.

  5. 5

    Publish and attach the number

    Publish the flow, then set the number's incoming messages to go to it. Use the phone number itself as the sender, not a Messaging Service, so replies stay in the same execution.

Studio or code?

Studio

When the flow is the product

  • A phone menu or SMS bot with a handful of branches.
  • Non-developers need to change wording and routing themselves.
  • You want to see every execution step by step when something goes wrong.
Functions, TwiML or your own server

When the logic is the product

  • Matching a caller to the right customer with any real certainty.
  • Rules that change by account, location or contract.
  • Anything that writes to several systems and has to succeed every time.

Most good builds use both: Studio for the conversation, code behind Make HTTP Request or Run Function for the decisions. More on raw call handling on our Twilio voice and IVR page.

The part behind the canvas

Studio can already ask, wait, branch and call out. What it can't supply is the answer. When a caller asks for the next free slot, something has to check your real schedule and reply inside 10 seconds. When a customer texts back a new address, something has to write it onto the job, not leave it in Studio's execution log.

That backend is where most of a Studio project's real work sits: an endpoint that knows your scheduling, dispatch or CRM data, answers quickly, handles a system that's down, and records what the flow collected. Your own system can also start flows through the REST API, so a confirmed booking or a shipped order begins a text conversation without the customer reaching out first.

n-frames builds and runs that layer: the endpoints and Functions a Studio flow calls, the write-back to your records, and the triggers that start flows from events in your business. For the inbound request format and signature checks, see our Twilio webhook setup guide, and the Twilio API page covers registration and delivery.

Questions people ask

What is Twilio Studio?

Twilio's visual builder for SMS, voice and chat workflows. You connect widgets on a canvas (send a message, gather a reply, branch on it, call an API) instead of writing the whole flow in code. It's mostly used for phone menus, SMS bots and automated follow-ups.

Do I still need to know how to code to use Twilio Studio?

Not for a simple flow. You do once the flow has to look up or update data somewhere else, because Make HTTP Request needs an endpoint to call and Run Function needs code behind it. That's the part n-frames writes for clients.

What's the difference between Twilio Studio and Twilio Functions?

Studio is the conversation: the sequence a caller or texter goes through. Functions is Twilio's serverless code, often called from a Studio flow through the Run Function widget for logic the widgets can't handle, like a database lookup. Both share the 10-second limit when called from a flow.

Can a Twilio Studio flow be triggered by something other than an incoming call or text?

Yes. Your system can start an execution through the REST API, so an order shipping or an appointment being confirmed can open a conversation. Flows can also start from Conversations and webhooks. A contact can only have one REST-triggered execution running at a time.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.