Multi-Provider Authentication Message Delivery
Role
UX Designer (Solo)
Organization
Broadcom (CA Technologies)
Duration
3 months
3 Channels
SMS · Email · Voice
4 Providers
Clickatell, TeleSign, SAP, Nexmo
Failover
Automatic provider fallback built-in
Shelved
Broadcom acquisition halted development
The Product
The Authentication Message Delivery Service is an administration console for managing third-party message delivery providers across SMS, Email, and Voice channels. Administrators register providers (Clickatell, TeleSign, SAP, Nexmo), configure API credentials, set failover behaviour, and monitor delivery performance — all within a single interface integrated into the CA Technologies authentication platform.
Profile & Provider Management
The profile page gives administrators a consolidated view of all registered providers across all three channels, with per-provider success/fail rate donuts and a combined usage trend chart. New providers can be registered inline without leaving the page.
Provider Configuration
CORE DESIGN DECISION — PROVIDER PERFORMANCE ALWAYS VISIBLE
Administrators configuring message providers needed more than a settings form — they needed to know whether their configuration was actually working. Embedding provider performance (usage bar charts + success/fail rate donut) directly on the profile and configuration pages meant admins could see delivery reliability without navigating to a separate reporting view.
The failover toggle on the provider configuration page is a direct consequence of this visibility: once admins could see that a provider had a 27% failure rate, the case for enabling failover became self-evident. Data surfaced the decision rather than the UI instructing the user what to do.
Outcome & Learning
The product was shelved when Broadcom acquired CA Technologies. Development was underway but not yet shipped.
The command-style search (@billing:november, @profile:email, @transaction:july) was an early experiment in power-user search — predating widespread adoption of command palette patterns in SaaS products. In retrospect, this was ahead of the curve for enterprise admin tooling, but would have needed significantly more discoverability work for the pattern to land well with non-technical administrators.
Selected Works

