Configure WhatsApp channel

Release version: Australia
Updated October 8, 2026
5 minutes to read
Summarize
Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

Summary of Configure WhatsApp channel

This guide explains how ServiceNow customers can integrate WhatsApp as a consumer messaging channel within Customer Service Management (CSM) using the WhatsApp Cloud API or Twilio. The integration enables support teams to manage WhatsApp conversations directly in the CRM Workspace alongside other channels, improving interaction tracking, queue management, and routing. It also supports ServiceNow Otto - Virtual Agent - to automate responses and assist customers before agent involvement.

Show full answer Show less

Key Features

  • WhatsApp Cloud API Integration: Direct integration with WhatsApp's native Cloud API, providing full functionality and reducing reliance on third-party infrastructure. Requires Meta and ServiceNow accounts.
  • Twilio Integration: An alternative integration using Twilio as an intermediary. This method supports WhatsApp messaging but has limited features compared to the Cloud API. Requires Twilio, Meta, and ServiceNow accounts.
  • Common Omnichannel Setup: Both integration paths share foundational steps like creating service channels and queues, configuring Advanced Work Assignment (AWA) routing rules, setting agent presence states, and activating the channel in the CRM Workspace.
  • ServiceNow Otto Virtual Agent: Enhances WhatsApp conversations by automating responses to common customer questions, reducing agent workload and improving first-contact resolution.

Practical Configuration Steps

To enable WhatsApp messaging within ServiceNow CSM, administrators must:

  • Set up and verify a WhatsApp Business Account and phone number.
  • Register the organization with Meta to access WhatsApp Cloud API credentials (Cloud API path) or establish a Twilio account connected to WhatsApp (Twilio path).
  • Create service channels and queues in Omnichannel administration to route WhatsApp interactions.
  • Configure AWA assignment rules and groups to route conversations to appropriate agents.
  • Set agent presence states to ensure agents receive WhatsApp interactions.
  • Activate the WhatsApp channel in the CRM Workspace so agents can manage conversations.
  • Optionally, enable ServiceNow Otto Virtual Agent for automated customer engagement over WhatsApp.

Benefits for ServiceNow Customers

  • Unified workspace consolidates WhatsApp with other channels (chat, email, phone), eliminating silos.
  • Improved first-response time and support efficiency for WhatsApp-first customers.
  • Consistent data tracking and interaction categorization via wrap-up codes enhance reporting and analytics.
  • Flexible integration options to fit existing infrastructure and preferences.
  • Virtual Agent integration reduces agent load by automating common inquiries.

Configure WhatsApp as a consumer messaging channel within ServiceNow Customer Service Management using the WhatsApp Cloud API. WhatsApp integrates with ServiceNow Otto - Virtual Agent, to answer customer questions, with conversations routing to agents through the CRM Workspace. Twilio integration is also supported but offers more limited functionality than the Cloud API.

Here's an example of a customer service journey combining WhatsApp support with omnichannel.

Amara is a customer support director at a global e-commerce company managing support across multiple channels. Customers increasingly prefer WhatsApp for support, but the team was handling WhatsApp conversations outside of ServiceNow through a separate platform, creating data silos and inconsistent service levels.

After setting up WhatsApp channel integration through the WhatsApp Cloud API (or Twilio), the team can now receive WhatsApp conversations directly in the CRM Workspace. They get the same queue management, assignment routing, and interaction tracking as other channels.

After setting this up, the customer saw support friction drop for WhatsApp-first users, and three channels became one unified workspace. First-response time improved by 35%, and agents now see all customer interactions (WhatsApp, chat, email, phone) in a single queue.

The following diagram shows the WhatsApp configuration workflow for administrators, agents, and customers.

Figure 1. WhatsApp configuration workflow
Workflow diagram with three swim lanes showing Administrator setup, Agent handling, and Customer interaction steps for WhatsApp configuration.

Common configuration steps (required for WhatsApp)

Every channel (chat, email, WhatsApp) requires the following foundational setup.

Table 1. Common configuration steps
Configuration step Description Role
1 Create service channel Service channel is created automatically during plugin installation for each channel (chat, email, WhatsApp). This is the container that routes customer interactions. System (automatic)
2 Create a queue Create a queue under each service channel in Omnichannel > Administration > Queues. The queue holds interactions waiting for an available agent. Each queue has a name, description, and optional schedule for availability windows.

CSM Admin
3 Configure AWA routing Create an assignment rule in Advanced Work Assignment that determines how interactions are routed to agents. Examples: Most Capacity (assigns to agent with most free time), Least Busy, Round Robin. Create an assignment group with agents who have the required roles (sn_customerservice_agent, sn_customerservice.consumer_agent, awa_agent). Link the rules and group to the queue. CSM Admin
4 Set agent presence state Add the channel to the Available presence state, so agents are eligible to receive interactions from that channel. Without this step, the queue has no target agents. CSM Admin
5 5. Activate channel in workspace Verify that the channel appears in the CRM Workspace. To confirm, assign a test interaction to an agent; the WhatsApp messaging UI appears only once an interaction is assigned. Agents must see the channel in their workspace interface to receive and manage interactions. CSM Admin
6 Configure wrap-up codes Navigate to Interaction > Wrap Up Codes to create categorization codes for interactions. Then navigate to Interaction > Wrap-up configuration to assign these codes so agents can categorize interactions for reporting. CSM Admin

WhatsApp integration options

WhatsApp configuration follows two separate paths: WhatsApp Cloud API or Twilio. Both paths share configuration steps.

WhatsApp via Cloud API

Use this path for direct integration with WhatsApp's native Cloud API. This approach skips the Twilio go-between and relies less on outside infrastructure. Customers must maintain two separate accounts: a Meta account and a ServiceNow instance.

See Integrating WhatsApp with Customer Service Management using the WhatsApp Cloud API.

Table 2. WhatsApp via Cloud API configuration steps
Configuration step Description Role
1 Setup WhatsApp business account Create and verify your WhatsApp Business Account and phone number with WhatsApp directly.Yuo must complete this before configuring ServiceNow. External (WhatsApp)
2 Register with Meta Register your organization with Meta (WhatsApp's parent company) to access the WhatsApp Cloud API. Meta provides API credentials and endpoint access needed for ServiceNow integration. Copy and save these credentials in a secure location; they might not be accessible again after setup. External / CSM Admin
3 Configure omnichannel (shared steps) Complete the common configuration steps in the Common configuration steps table: create queue, configure AWA routing with assignment rule and group, set channel to Available presence state, and activate channel in workspace. CSM Admin
4 Activate Virtual Agent (optional) For conversational integration with WhatsApp via Cloud API, enable Virtual Agent for Customer Service so predefined topics are available over WhatsApp. CSM Admin

WhatsApp via Twilio

Use this path if your organization already works with Twilio or prefers their integration model. Twilio sits between WhatsApp and ServiceNow, handling message delivery, failover, and policy compliance. This approach doesn't support the full control features (for example, list pickers, typing indicators, or geo-location specific features) available through the Cloud API. Customers must maintain three separate accounts: Twilio, Meta, and ServiceNow.

See Integrating WhatsApp with Customer Service Management through Twilio.

Table 3. WhatsApp via Twilio configuration steps
Configuration step Description Role
1 Establish Twilio account Set up a Twilio account and connect it to your WhatsApp Business Account. Twilio provides the messaging infrastructure between WhatsApp and ServiceNow. External (Twilio)
2 Setup WhatsApp business account Create and verify your WhatsApp Business Account and phone number with WhatsApp directly. This is a prerequisite for Twilio integration and must be completed before configuring ServiceNow. External (WhatsApp)
3 Create message templates Submit message templates for approval with WhatsApp. Any outbound message that isn't a direct reply within the 24-hour customer service window requires a pre-approved template. External / CSM Admin
4 Configure omnichannel (shared steps) Complete the common configuration steps in the Common configuration steps table: create queue, configure AWA routing with assignment rule and group, set channel to Available presence state, and activate channel in workspace. CSM Admin
5 Activate Virtual Agent (optional) For conversational integration with WhatsApp via Twilio, enable Virtual Agent for Customer Service so predefined topics are available over WhatsApp. CSM Admin

ServiceNow Otto in Virtual Agent

Extend the WhatsApp channel with ServiceNow Otto in Virtual Agent so common customer questions resolve automatically before an interaction reaches an agent. Customers may also be able to access AI agents directly through WhatsApp self-service, without needing to reach a live agent first. The Otto branding shows that ServiceNow is bringing its AI capabilities into one interface, instead of keeping them as separate products.

Before you configure this capability, activate the ServiceNow Otto for CSM and Now Assist in Virtual Agent plugins. For more information, see Configure ServiceNow Otto for Customer Service Management (CSM) in Virtual Agent.