Build Real-Time Voice & Messaging Automation with ServiceNow's Revamped Vonage Spoke

shreychaudhary · 55m ago

Whether you're a Flow Designer developer building complex voice orchestration, a citizen developer automating customer notifications, or a business leader looking to connect your telephony and messaging workflows to ServiceNow — this release is for you.

The revamped Vonage Spoke (live since April 9, 2026) brings three significant upgrades:

Granular NCCO call control directly in Flow Designer
RCS rich messaging — interactive cards, media, and text via Vonage's Messaging API v1.0
Six real-time event triggers covering the full call and SMS lifecycle

No custom scripting. No polling. No multiple connections.

What Could You NOT Do Before This Release?

Before this release, if you wanted to control individual steps of a voice call — route it, transfer it, pause it, or fire a mid-call notification — you had two options: write a custom REST step in Flow Designer, or hand it off to a developer to build a Scripted REST integration. Neither was accessible to citizen developers, and both required knowing Vonage's NCCO spec inside-out.

Similarly, real-time SMS and call event handling required polling or custom webhook plumbing outside of Integration Hub entirely.

This release changes both of those realities.

What Can You Build Now? Real-World Use Cases

Before diving into features, here's what this release actually unlocks in practice:

IT Operations — P1 Incident Call Routing

When a P1 incident fires in ServiceNow, automatically initiate a voice call to the on-call engineer via the Connect NCCO action. If unanswered, transfer to a backup using the Transfer action. The moment the call completes, the Voice Completed trigger fires — your flow logs the outcome, updates the incident, and sends an RCS status card to the incident manager.
Customer Service — Closed-Loop Case Resolution

When a customer service case is resolved, send an interactive RCS Card to the customer's phone with two options: "Confirm Resolved" or "Reopen." Their tap triggers a webhook back to ServiceNow — no agent involvement needed for the most common outcome.
HR / Onboarding — Welcome Communication Flow

The moment a new hire record is created in ServiceNow, trigger an RCS rich message with their onboarding checklist, links, and a media welcome card — significantly more engaging than a plain SMS, with no additional integration work.
Operations — SMS Delivery Failure Escalation

Using the SMS Failed trigger, automatically escalate to a voice call or create a task when a critical SMS notification fails to deliver — closing the gap that polling-based approaches always left open.

New & Enhanced Actions

1. NCCO Call Control — Granular Voice Orchestration

NCCO (Nexmo Call Control Object) is Vonage's instruction set for controlling voice calls in real time. The Vonage Spoke now exposes individual NCCO types as discrete, no-code Flow Designer actions — meaning any Flow Designer user, not just developers, can build sophisticated call flows.

New NCCO actions:

Action	What it does
Connect	Routes the call to a phone number, SIP URI, or WebSocket endpoint
Notify	Fires a webhook mid-call to trigger downstream ServiceNow logic
Wait	Pauses call execution for a defined duration
Transfer	Hands the call off to a new endpoint or NCCO instruction set

Enhanced existing actions: Talk, Conversation, and Record have been updated with additional input parameters for finer control.

Behind the scenes — Connect action example:

Flow Designer passes your endpoint parameters to the spoke.
The spoke constructs a valid NCCO JSON payload.
Vonage's Voice API receives the instruction and routes the call to your specified destination.

Before this release: Achieving this required a custom REST step, manual NCCO JSON construction, and developer involvement. Now it's a drag-and-drop action in Flow Designer.

2. RCS Messaging — Your Most Powerful New Channel

RCS (Rich Communication Services) is the next evolution of SMS — it supports images, video, interactive buttons, and structured cards, delivered natively to a user's messaging app on supported networks. Think of it as SMS with the interactivity of a mobile app.

The Vonage Spoke now supports three RCS action types via Vonage's Messaging API v1.0:

Action	What it delivers
Send RCS Text	Plain text over RCS (higher deliverability than SMS on supported networks)
Send RCS Media	Images or video inline in the message thread
Send RCS Card	Interactive rich cards with buttons, structured content, and deep links

Why RCS over SMS for business workflows?

Capability	SMS	RCS
Rich media (images, video)	❌	✅
Interactive buttons	❌	✅
Branded sender identity	❌	✅
Read receipts	❌	✅

Behind the scenes — RCS Card action example:

Your flow passes recipient, card content, and button definitions to the action.
The spoke calls Vonage's Messaging API v1.0 endpoint with your payload.
Vonage delivers the interactive card to the recipient's native messaging app.
Button interactions can webhook back into ServiceNow to continue the flow.

RCS is particularly impactful for customer-facing workflows where engagement and response rates matter — approvals, confirmations, status updates, and notifications.

New External Triggers — Real-Time Event-Driven Automation

The shift that matters: From polling-based status checks to instant, event-driven flows.

Previously, reacting to a Vonage call or SMS event in ServiceNow meant scheduled polling — checking for status changes at intervals, missing events in between, and burning unnecessary compute. This release replaces that with six real-time webhook-based triggers.

Here's what end-to-end looks like now:

A P1 incident fires → ServiceNow initiates a voice call → the Voice Ringing trigger fires and logs the attempt → the call is answered → Voice Answered trigger updates the incident with a timestamp → the call ends → Voice Completed trigger closes the loop, logs duration, and kicks off a follow-up SMS → the SMS is delivered → SMS Delivered trigger marks the notification complete.

Call Management Triggers

Trigger	When it fires
Voice Ringing	Call initiated, number is ringing
Voice Answered	Call picked up
Voice Completed	Call ends

SMS Management Triggers

Trigger	When it fires
SMS Delivered	SMS successfully delivered
SMS Failed	SMS delivery failed
SMS Accepted	Message accepted, delivery in progress

Behind the scenes — how triggers work:

Vonage fires a webhook to ServiceNow when the event occurs.
Integration Hub receives the payload and matches it to your configured trigger.
Your flow kicks off instantly with the full event data available as trigger outputs — no parsing, no custom scripts.

Important: Deprecation Notice for Existing Vonage Spoke Users

Legacy actions across the SMS, Number Management, Call Management, and WhatsApp categories have been removed in v2.0.

Before upgrading, you must:

Audit all active flows using the Vonage Spoke for deprecated action usage.
Remap deprecated actions to their updated equivalents in v2.0.
Test flows in a non-production environment before promoting to production.

Skipping this step will result in broken flows post-upgrade. If you're unsure which actions are deprecated, check the Vonage Spoke v2.0 release notes on the ServiceNow Store listing.

Key Takeaways

NCCO call control is now no-code — connect, transfer, notify, and wait actions are available to any Flow Designer user, no scripting required.
RCS unlocks a richer messaging channel — interactive cards and media, accessible in the same spoke as your existing SMS and WhatsApp flows.
Six real-time triggers replace polling — react instantly to call and SMS lifecycle events across the full Vonage event model.
One connection, all new capabilities — your existing Vonage connection alias works with every new action and trigger. No reconfiguration needed.
Existing users must audit before upgrading — legacy actions are deprecated in v2.0.

Getting Started

Head to the ServiceNow Store and search for Vonage Spoke.
Upgrade to v2.0 (review the deprecation notice above first if you're on a prior version).
Open Flow Designer — new NCCO actions, RCS actions, and triggers are available immediately after upgrade.
Check the updated Vonage Spoke documentation on docs.servicenow.com for action-level parameter references and authentication setup.