Enterprise clients were maintaining separate API integrations for every messaging channel. A Fortune 500 e-commerce company spent six months integrating five messaging vendors. I designed the UI for a unified platform covering SMS, RCS, WhatsApp, Viber, MMS, and Email with a single API. Implementation time dropped 50%.
Three different users. Three entirely different definitions of the problem.
Enterprise developers said: "We maintain seven different API integrations for messaging. Each has different authentication and response formats. When one fails, we have no automatic fallback."
Marketing teams said: "We create rich RCS messages with buttons and images. Then we manually create stripped-down SMS versions. Keeping them in sync is a nightmare."
Compliance officers said: "Every country has different messaging rules. We fear violating TCPA, GDPR, or regional regulations we do not fully understand."
The same product needed to solve three fundamentally different problems for three different users without forcing any of them to understand the others' workflow. That was the actual design challenge.
I also researched RCS closely. It was about to launch on iOS 18, giving early adopters a measurable engagement advantage. RCS delivered 22.2 percent click-through rates versus three percent for standard SMS. The platform needed to be built for where messaging was heading, not where it had been.
Design once, deploy to all channels. Embed compliance at creation, not review.
The central design decision was the template architecture. A single template needed to produce six different outputs: a rich RCS message with video and interactive buttons, a WhatsApp card, a Viber message, an MMS, a plain SMS, and an email.
The rejected direction: separate template editors per channel with a sync function. Every client we interviewed had already tried building this internally. The sync always broke.
The chosen direction: one visual template builder that previewed all six outputs simultaneously. The system auto-generated channel-appropriate versions. Marketers designed for the richest channel and watched the degradation in real time. Non-technical users never touched JSON.
Compliance was embedded into template creation, not bolted on afterward. Regulatory requirements for the destination country appeared in real time as templates were built, stopping violations before they were committed rather than flagging them after. Making constraints visible early is not just a usability principle — in high-compliance environments, it is a risk management decision.
Real-time preview was technically the hardest part. It was also the most important.
The initial template builder required JSON knowledge. Marketing teams could not use it. I built a drag-and-drop visual builder that auto-generated the JSON in the background.
Compliance warnings appeared after template creation in the first version, forcing teams to rebuild from scratch. I moved compliance validation inline, flagging issues during creation, not after. A financial services client gave the most useful feedback: "We need to know exactly why a message failed. Was it a carrier issue, a compliance block, or a user opt-out?" I redesigned the delivery status interface with detailed failure categorization covering ten distinct failure types.
Three user groups tested separately. The consistent finding across all three: when constraints were visible at the point of decision, users worked with them. When constraints appeared as post-creation errors, users looked for workarounds.
Enterprise implementation time dropped 50%. RCS adoption drove 22.2% click-through rates.
Enterprise clients who previously spent four to six months integrating multiple messaging vendors completed implementation in two to three months.
RCS campaigns delivered 22.2% click-through rates compared to 3% for standard SMS. Early adopters built a measurable engagement advantage before RCS became broadly available on iOS 18.
Message delivery rates improved 15 to 20 percent through intelligent channel cascading. The platform contributed to 42 percent annual revenue growth, supporting TeleSign's growth to a $1.3 billion valuation at acquisition.
The template library: one template, six channel outputs, approval status visible inline. What previously required five separate vendor dashboards now lives in one interface.
The ecosystem is the product. You cannot design one part without designing all of it.
The most important design decision in this project was embedding compliance into the creation flow rather than the review flow. Every alternative I considered would have surfaced regulatory issues after teams had already built their templates. That would have created rework, frustration, and eventually workarounds that bypassed the guardrails entirely.
Serving three audiences with fundamentally different needs on a single platform required a navigation architecture that felt like three different tools while sharing one underlying data model. The hardest part was not the interface design. It was convincing stakeholders that the developer experience and the marketer experience did not need to look like the same product.
I would advocate earlier for a developer sandbox environment next time. We shipped it in Phase 2. Several integration delays in Phase 1 would have been avoided if it had existed from day one.