An appointment reminder seems like a small thing. A date, a time, a hospital department. Yet the useful question arrives after the message: what happens when the patient cannot come? A cancellation trapped in a telephone queue cannot easily become somebody else’s appointment. The communication has travelled. The work has barely moved.
- Webex Connect joins customer messages to business workflows.
- Its buyers include hospitals, banks and travel companies.
- The payoff depends on what a business can do with a reply.
A cancellation needs somewhere to go
Bolton NHS Foundation Trust had a familiar problem: missed appointments had climbed after the pandemic. Its earlier text-reminder service covered only some specialties. The trust wanted broader coverage and less dependence on postal reminders.
Using Webex CPaaS solutions, Bolton introduced SMS and voice reminders with options to confirm, cancel or rebook. Webex’s case study reports a 22% reduction in new missed appointments over three months. It also identifies 3,000 slots potentially reusable after cancellations and rebookings. Those are reported outcomes from one implementation, with a specific starting point.
A revealing detail precedes those results. Bolton had captured mobile numbers for 93% of patients through careful preparation. The lesson is pleasantly unglamorous: an automated reminder needs a working destination.
The business in the arrows
Webex CPaaS Solutions, the Cisco business formerly known as IMImobile, works in this gap between a message and an operational result. CPaaS stands for Communications Platform as a Service. Webex Connect, its central platform, lets enterprises build communication into existing processes through APIs and low-code tools.
Its documentation describes support for more than twelve channels. SMS, WhatsApp and email are among them. A hospital, retailer or bank can use that channel layer alongside its existing software rather than designing every conversation around a single messaging application.
The revealing screen is the visual flow builder. Users connect nodes that perform tasks: make an HTTP request, evaluate a condition, send a message. The arrows express what should happen next. A workflow can check a record before contacting someone, branch according to a response and route an exception elsewhere.
There is real engineering underneath the diagram. The builder exposes drafts, versions, warnings and debugging. Pre-built integrations connect applications such as Salesforce, Zendesk and Epic. The useful expertise lies in coordinating systems and communication logic, including the awkward cases that a cheerful demo tends to hurry past.
- 01Business eventAn appointment approaches
- 02Check & sendRead the record and contact preference
- 03Handle the replyConfirm, cancel or request help
- 04Complete the actionUpdate the system or involve staff
Why Cisco bought the plumbing
IMImobile’s story began in 1999 with founders Vishwanath Alluri and Shyam Bhat. Its roots were in services for mobile operators. By February 2021, Cisco was buying a business able to orchestrate customer communications at enterprise scale.
The announced purchase price was approximately $730 million, net of cash and including debt. Cisco completed the acquisition on February 19, 2021, bringing the team into its Contact Center business unit. The rationale was straightforward: combine cloud contact centers with programmable communications, artificial intelligence and experience management.
That history explains its place in the market. A contact-center agent encounters the customer during one part of a longer process. Connect can help trigger an interaction beforehand and coordinate what follows. The strategic value is the connection between those moments.
Buyers can also consider Twilio, Infobip, Sinch or Vonage. Twilio itself offers messaging and orchestration capabilities. Webex’s pitch therefore needs more substance than a list of channels. Its case rests on enterprise workflow tooling, existing-system integration and its relationship with Cisco’s contact-center portfolio. The right comparison starts with the buyer’s actual systems.
A sailing alert beats a sales pitch
Carnival Cruise Line supplies a different example. Its older phone-based outreach needed more ways to engage customers. With Connect, Carnival uses opt-in SMS communications, payment reminders and sailing alerts. Someone who booked a vacation months earlier may need a timely nudge about the final installment.
“We also use Webex Connect for payment reminders...”
Marcus Labra · Carnival Cruise Line
The same infrastructure can notify passengers about last-minute changes. These are mundane messages with consequences: money collected, information received, fewer surprises at the pier. Carnival’s published account describes improved engagement without supplying a numerical improvement that readers could independently compare.
Royal Bank of Canada’s motivation included securing customer messaging and improving visibility into delivery and engagement. It chose Connect with Branded Text and RCS. Webex’s account projected 20 million messages per month, with 24% expected over RCS. Those numbers describe an anticipated workload, rather than an audited traffic total.
The price of the next step
The business model combines enterprise subscriptions, activation and usage charges. A public UK procurement schedule dated May 2024 lists Connect Essential at £3,550 a month, Advanced at £6,200 and Premium at £8,900. It separately lists activation and channel fees, with a minimum twelve-month term for new licenses.
Essential£3,550
Advanced£6,200
Premium£8,900
These are dated procurement figures, not a current worldwide quote or a complete implementation budget. Today’s Webex pricing page directs CPaaS buyers to sales. Webex also offers business applications: Campaign for marketers, Notify for operational alerts and Engage for customer conversations. Different teams can buy tools closer to their daily work.
Start with the reply
The practical method is small enough to copy. Pick one recurring event. Establish which record triggers it, where permission and contact details live, and what a reply must change. Test failures and staff handoffs before expanding the flow.
The limitations are concrete. Unusable contact data, inaccessible systems and undefined exception handling undermine the chain. Channel rules also keep changing: an August 2026 Webex notice warned that noncompliant Apple Messages for Business payloads could be rejected. Even low-code communication requires maintenance. The sensible goal is a completed action that somebody can measure.