What Building Overly Complex Twilio Flex Solutions Taught Me About CX

When I was at Waterfield Technologies, I built some genuinely impressive contact center environments on Twilio Flex. I also built some that were way too complicated for their own good.

The IVRs were the first place I learned this lesson. Early on I'd build out these intricate call flows — nested menus, conditional routing logic, edge case handling for scenarios that might happen once a year. The architecture was clean. The logic was sound. And customers would demo it and love it, right up until their agents actually had to use it.

The agent desktop UI was the same story. I'd build custom Flex components that surfaced all kinds of contextual data — call history, CRM records, sentiment indicators, previous interaction summaries. Useful information. But I'd pack it all into one screen because I could, and agents would sit there overwhelmed trying to figure out what to look at while a customer was waiting on the line.

The thing nobody tells you when you're building CX solutions is that the person using it most is usually not the person who bought it. The VP of Customer Experience signs the contract. The frontline agent lives with what you built eight hours a day.

The best environments I deployed were the ones where I forced myself to ask one question before adding anything: does this make the agent's job easier or harder in the first ten seconds of a call? If the answer wasn't clearly easier, it didn't make the cut.

Complexity is easy to build. Restraint is harder. And in contact center design, restraint is almost always what the customer actually needed.