All case studies

03 · fintech · contact center

Twilio Flex contact center: agent workflows

Agents work inbound and outbound calls with a verified caller and the full customer history, without leaving Flex.

  • Twilio Flex
  • React
  • TypeScript
  • Twilio Paste
  • Laravel
  • Laravel Reverb
  • Laravel Echo
Client
Stepping Stone Loans, a US consumer lender
Role
Senior full-stack & AI engineer
Period
Dec 2024 – present
Engagement
Long-term contract through Upwork

Problem

Call-center agents had to switch between tools to see who was calling, the state of their loan and what to say next.

The contact center was moving from an in-house browser call center to Twilio Flex, and the agent workflows had to move with it.

How it works

diagram · How an agent handles a call
  1. 01CallAn inbound call arrives, or the agent dials from the outbound queue.
  2. 02VerificationThe caller is identified and verified before account details appear.
  3. 03HistoryCalls, texts, chats and emails with this customer appear in one timeline.
  4. 04Agent actionThe agent completes the call and records its outcome.

What I built

  • Built an outbound-call work queue in Flex: sortable, filterable, one-click dialing and call dispositions.
  • Built an omnichannel customer-history tab that pulls voice, SMS, chat and email into one timeline.
  • Added caller identification and verification before account details appear, plus do-not-call and unreachable-number handling.
  • Stored call recordings privately and transcribed them asynchronously.
  • Added contact-center analytics to the admin panel: interactions by channel and direction, and a per-agent view.
  • Wrote the Laravel APIs behind these workflows, with feature tests.
  • Built real-time WebSocket notifications on Laravel Reverb and Echo, including live agent-availability and call-queue updates for the in-house call center that came before Flex.

Key decisions

Build inside Flex, not beside it
The outbound queue, customer history and caller verification are Flex plugin features, so agents never leave their workspace.
One timeline for every channel
Voice, SMS, chat and email history sit in one timeline, so an agent sees every past contact in one place.
AI drafting lives in the admin copilot
AI reply drafting moved out of the Flex plugin into the Laravel Nova copilot, so AI help sits in one panel across the back office.

Guardrails

  • Agents see account details only after the caller is verified.
  • Numbers on the do-not-call list are screened out of outbound call-backs.

Result

Agents stop switching tools mid-call: verification, the full contact history and the outbound queue live inside Flex, and managers see interactions by channel and per agent in the admin panel.

media note

The lender’s internal systems are private, so this case study uses words and a diagram instead of screenshots.