Twilio Flex

Twilio Flex's Per-User Pricing plan costs $150/agent/month. Twilio lists it as starting at $150, requires a contract, and bills the maximum number of named users on the account that month with no proration for mid-month changes. Channel usage is separate: voice at $0.014/min, messages at $0.0083 each, phone numbers from $1.15/mo. For comparison, Converge costs $49/month flat for up to 15 team members.

Twilio Flex is best suited for large enterprises with dedicated development teams and complex contact center needs. Its standout feature is programmable contact center with unlimited customization.

There are 49+ platforms you can compare with Twilio Flex in the messaging api platform category. Each comparison above shows detailed feature and pricing differences to help you choose.

Twilio Flex's User + usage plan starts at $35 per monthly active user, where a monthly active user is anyone who logs into Flex at least once that month. It is available only for Flex deployments on an existing Twilio account, not for Flex Accounts. The part that decides the real bill is the quota rule: Twilio's Flex pricing page (checked 16 September 2026, and stating its prices are current as of August 2026) says there are no free quotas, so Conversations, TaskRouter, Studio and Functions are each charged by individual usage on top of the $35. Treat $35 as an access fee rather than a per-agent price.

The break-even is 150 active user hours per person per month, because 150 hours at $1 each equals the $150 named-user rate. Below that line the active user hour model is cheaper, which is why Twilio positions it for seasonal traffic and part-time agents; above it, named-user pricing wins on base license cost. The two models also count people differently. Twilio charges active user hours only for users who log in, and its own example has 500 users provisioned with 20 logging in and only those 20 billed, while named-seat pricing charges the maximum number of named users on the account that month regardless of logins. Both rules are published on Twilio's Flex pricing page, checked 16 September 2026.

No. Twilio states that it does not mix and match Flex pricing plans and recommends choosing a plan based on expected use, which makes the model choice a commitment rather than a monthly optimization. That single sentence on Twilio's Flex pricing page (checked 16 September 2026) is the most consequential line on it, because the three models suit opposite staffing shapes: $1 per active user hour fits part-time and seasonal cover, $150 per named user fits stable full-time headcount, and $35 per monthly active user only exists for Flex on an existing Twilio account. You cannot run part-time staff on hours and full-time staff on seats in the same account, so price the busiest month you realistically expect before you pick, not the current one.

Twilio charges for the maximum number of named users on the account during the month and does not prorate seats added or deleted mid-month. In practice you pay your peak headcount rather than your average, so removing seats halfway through a month produces no credit for the rest of it. Twilio's worked example on its Flex pricing page (checked 16 September 2026): a customer starts the month with 50 users, removes 25 mid-month, then adds 25 replacements, and is billed for 50 named users — the peak — not the 75 seats that existed at some point. Named seats include admins, supervisors, agents and developers, meaning any TaskRouter worker, so provisioning a contractor for a one-week integration adds a full month's seat to that maximum. The one exception Twilio prorates is the move from a starter Flex project to the named seat model, to avoid double billing.

No, but they are forfeited the moment you choose a billing model. The 5,000 free active user hours are a one-time grant that does not expire, and selecting a billing model forfeits whatever is left — that is Twilio's own wording on its Flex pricing page, checked 16 September 2026. The grant arrives when a trial Flex project is upgraded to a starter Flex project on a new Flex account. Twilio will not add more once they are spent, and they cannot be attached to an existing Flex account. So the constraint on an evaluation is not the calendar, it is the decision: five full-time agents burn roughly 200 user-hours a week, which makes 5,000 hours about 25 weeks of runway, and committing to a plan in month one throws most of it away.

WhatsApp session messages and Facebook Messenger messages are included in the Flex license; WhatsApp template messages are charged separately. That split matters more than it first looks, because template messages are the ones sent outside WhatsApp's 24-hour customer service window — order updates, proactive notifications, re-engagement — so the outbound half of WhatsApp is the half that carries a per-message cost, while reactive support inside the window does not. Twilio also attaches a caveat to Messenger on its Flex pricing page (checked 16 September 2026): messages are included today, but if Facebook introduces a template-style fee for Messenger you would buy that from Facebook directly rather than through Twilio.

Agent Copilot costs $0.035 per minute on voice and $0.005 per message on digital channels, but it carries two caveats that belong in any budget: Twilio's Flex pricing page (checked 16 September 2026) marks it Public Beta, states the prices are subject to change, and warns that additional Professional Services may be required for deployment. At today's rates, 10,000 digital messages a month adds $50 and 2,000 voice minutes adds $70 — modest sums that are only fixed for as long as the beta pricing holds. The Professional Services line is the bigger unknown, because it means the AI add-on is not guaranteed to be a self-serve toggle on top of your existing plan.

The Flex plan buys the software; every conversation is billed separately at Twilio's standard product rates. In the US that is $0.0140 per minute to place a local call, $0.0083 per SMS segment, and $1.15 per month for a local phone number ($2.15 for toll-free), per Twilio Voice pricing and Twilio SMS pricing, both checked 16 September 2026. Two details make the headline rates understate a real bill. SMS is charged per segment, not per message, so anything past the character limit bills as two or more. And US carrier fees are added on top of Twilio's rate, varying by carrier: on long codes, outbound SMS carries $0.0035 for AT&T and $0.0045 for T-Mobile and Verizon. Receiving is billed too, at $0.0085 per minute on an inbound local call and $0.0083 per inbound SMS segment.