Building contact center features on Twilio Flex yourself vs Floor Walker
Short answer: Twilio Flex is a programmable platform, so you can build almost any contact center feature yourself, but each one (a paced dialer, a screen recording pipeline, a reporting data model) is a project of its own that you then maintain across Flex UI releases. Floor Walker is a commercial set of ready-made Flex add-ons, hosted for you or installed in your own cloud or data center. Build when your needs are unusual and you have a standing Flex team; buy when you need the common features working soon and would rather spend your developers on what makes you different.
The comparison
| Area | Building it yourself | Floor Walker |
|---|---|---|
| Outbound dialer | Pacing logic, answering machine handling, retries, DNC and calling windows, live supervisor view | Preview, progressive, power and predictive modes, callbacks, SMS and WhatsApp campaigns, DNC lists, calling windows |
| Screen recording | Desktop capture app, encoding, upload, storage, per-task playback | Desktop recorder for Windows and macOS, per-task playback with coaching notes |
| Historical reporting | Event ingestion, a data model, metric definitions, report UI, exports | Reports on live Event Streams data, metric registry, exports, Metabase, MCP |
| Wallboards | Real-time aggregation, a TV display without a Flex login | Tile-based boards in Flex and on TVs through a revocable link |
| CRM | Customer profiles, identity across channels, cases, reminders | Embedded CRM, merging duplicates, custom fields, cases, tasks that return as Flex tasks |
| Localization and RTL | Your own string handling and right-to-left layout | English and Hebrew, right-to-left throughout |
| Flex UI upgrades | Your team tests and fixes every plugin | Delivered as product updates, applied by us or together with your IT team |
| Fit to your process | Exactly what you specify | What the product does, plus your own plugins next to it |
| Where it runs | Whatever you design and operate | Managed hosting by us, or installed in your cloud or data center |
Where the effort goes when you build
Dialer pacing and compliance
A predictive dialer is a control problem, not a loop that places calls. Floor Walker's pacer runs every second, learns per campaign how likely a human is to answer and how long answering takes, predicts which agents will free up soon, and adjusts a safety margin against a missed-wait target, with a breaker that drops to progressive mode on overshoot (Pacing). Every number is checked against DNC lists, calling windows in the lead's time zone, attempt limits and the business calendar, when the lead is picked and again just before dialing (Compliance and calling hours).
Building this yourself means writing and tuning that logic, and testing it without spamming real customers. Buying does not remove legal work: every consent, registry and calling-hours rule is a campaign setting, and you confirm the rules for your market with your own counsel. The dialer also has published limitations, such as voicemail drop not being built yet.
Screen recording pipeline
Screen recording is a small product of its own: a desktop app on every agent's computer, talking to the Flex plugin, plus upload, storage and a player. Floor Walker's recorder (Windows and macOS) uploads the recording in short parts as it goes, labels each part with the tasks open at the time, and lets supervisors replay a single conversation even when the agent handled several in parallel (How recording works). Pause for sensitive data, private storage, short-lived playback links and automatic retention are part of the design you would otherwise have to build.
Reporting data model
Reports start with modeling, not charts: folding TaskRouter and Studio events into queue visits, agent legs, contacts and IVR journeys, then defining metrics such as service level and abandons once so every screen agrees. See Floor Walker's Reports overview and metrics catalog for the scope.
Wallboards, CRM and localization
Wallboards need real-time aggregation and a way to show a board on a TV without a Flex login. A CRM inside Flex needs identity resolution across channels and reminders that come back as tasks. If your agents work in a right-to-left language, every screen needs to handle it (Languages and right-to-left).
Maintenance across Flex UI releases
Twilio releases minor Flex UI versions about five times a year, and accounts update to new minor versions automatically by default. Major versions bring backward-incompatible changes; Flex UI 1.x reached end of life on June 30, 2024 (How we release Flex, Flex UI migration guide). Every custom plugin is code you retest on each release, for as long as you run it.
When building it yourself is the better choice
- Your workflow is unusual. If your process does not look like a typical contact center, a product built for the common case may fight you.
- You need one feature, not a suite. A single focused plugin can be cheaper to build than to license and operate.
- You already have a Flex team. Developers who know Flex, TaskRouter and Studio can extend what they built and own its roadmap.
- You want full source control. Floor Walker is closed-source and commercial; its core features change through the vendor.
- You want a head start without a vendor. Twilio publishes the Flex Project Template and a Plugin Library as starting points.
When Floor Walker is the better choice
- You need several of these features. Dialer, CRM, AI insights, screen recording, wallboards, supervisor console and reports share one Flex plugin, one sign-in and one set of metric definitions.
- You want a say in where the data lives. Customer data, recordings and analytics are hosted for you in a dedicated environment, or kept in your own cloud or data center, encrypted in transit and at rest (Deployment, Security).
- Your developers have other priorities. The common features arrive working, and your team can still build its own plugins next to them.
- You work in Hebrew or need right-to-left. It is built in rather than retrofitted.
Buying still has costs: a license, another vendor to work with, and less control over the roadmap. If you install Floor Walker in your own infrastructure, your IT team also takes part in installation and updates.
FAQ
Can I add my own Flex plugins next to Floor Walker?
Yes. Flex supports multiple plugins, and Floor Walker's features are switched on per feature in the Flex configuration, so your own customizations can run alongside them.
Does Floor Walker run in Twilio's cloud?
The Flex plugin and the Twilio-side functions run in your Twilio account. The Floor Walker service, which keeps customer data, recordings, campaigns and reports, is hosted by us in a dedicated environment or installed in your own cloud or data center. Besides Twilio, the only outside services are the AI services configured for your installation.
Do I still need developers if I buy?
You need a Flex administrator who works with us during installation and configures Flex, TaskRouter and Studio. You do not need to write or maintain the features themselves.
Can I start with one product and add others later?
Yes. Each product is a feature switch in your Flex configuration, so you turn on the ones you bought. Ask us which combination fits your rollout.
Next steps
Book a demo: hello@floorwalker.dev