Conversational SMS service channel
Summarize
Summary of Conversational SMS service channel
The Conversational SMS service channel app, available on the ServiceNow Store, enables workspace agents to manage long-running SMS support conversations alongside other service channels. Requesters can start support conversations via SMS, and agents can initiate, continue, and receive SMS conversations directly within the Workspace Inbox. The app reduces system message clutter for requesters during extended interactions, improving communication clarity.
Show less
Messaging Profiles
Messaging profiles map incoming phone numbers to requesters to ensure accurate interaction tracking. The system automatically creates or associates messaging profiles based on whether the phone number matches records in the User [sysuser] table or existing messaging profiles. If no match exists, interactions are linked to a guest user until verified. Agents can manually verify and reassociate profiles to maintain correct user identification.
Messaging Actions
Messaging actions allow automated triggers based on conversation activity, such as messages sent by requesters or agents. Parameters include event type, duration for triggering actions, and filter conditions on interaction records. Possible actions include prompting agents or requesters with notifications, reassigning interactions, or changing interaction states, helping agents manage conversations efficiently.
Ongoing Conversations
Agents can view new SMS messages in the Agent Inbox and track ongoing conversations via the Ongoing tab. SMS conversations are distinct from chat as they can persist over time. Completed SMS conversations are excluded from ongoing views to keep the workspace focused on active dialogues.
Requester-Initiated SMS Conversations
When requesters start SMS support conversations, virtual or live agents handle them through Advanced Work Assignment routing. New conversations create new interactions assigned appropriately, while messages in existing interactions are injected into ongoing threads, maintaining continuity for both virtual and live agent scenarios.
Agent-Initiated SMS Conversations
Agents can begin SMS conversations by selecting or entering a provider number. If an active conversation exists with the requester, the system continues the existing interaction; otherwise, it creates a new one. The app manages transitions between live agents and virtual agents, including closing previous interactions and creating new profiles when necessary, ensuring clear and accurate conversation tracking.
Using the Conversational SMS service channel app on the ServiceNow Store, workspace agents can provide support for long-running SMS conversations and conversations that use multiple service channels.
Request apps on the Store
Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.
Overview
Requesters can initiate support conversations through SMS. Since these support conversations can be long-running, workspace agents need the ability to track ongoing conversations while also addressing requesters on other service channels. With the Conversational SMS service channel store app, workspace agents can initiate or continue SMS conversations and also accept SMS work items from the Workspace Inbox. Requesters in SMS conversations see a limited subset of system messages. This minimizes the number of system messages in case the conversation is long-running.
Messaging profiles
Messaging profiles provide a way to match an incoming phone number to a requester:
| If | Then |
|---|---|
| New SMS is received from a requester who is associated to a phone number on the User [sys_user] table but has no messaging profile match |
|
| New message received from a requester who does not have a phone number match in the User table but does have messaging profile match |
|
| New message received from a requester who does not have a phone number match in the User table or messaging profiles |
|
| New SMS from a requester that conflicts with an existing User table or messaging profile |
|
Messaging actions
Messaging actions provide a way to trigger actions based on messaging activity on a conversation.
| Messaging action parameters | Description |
|---|---|
Event
|
Sending of a message from a requester or agent starts a timer that can trigger an action |
| Duration | Time set to trigger an action based on the Event parameter being set |
| Filter conditions | Condition needed on the Interaction record for a messaging action to be triggered (for example, State is "On Hold") |
| Action | Possible actions include:
|
Ongoing conversations
The Agent Inbox displays new SMS messages and agents can locate currently assigned SMS conversations in the Ongoing tab. The tab indicator and record highlight indicate when an SMS conversation has a new message. Unlike chat conversations, SMS conversations can be long-running. Completed SMS conversations do not display in the Ongoing tab.
Requester initiated SMS conversations
When a requester initiates a support conversation, a virtual agent or a live agent addresses the conversation. Like other service channels, Advanced Work Assignment handles the routing of SMS conversations to live agents. This is how requester-initiated SMS conversations are handled:
| If | Then |
|---|---|
| There is no active SMS interaction |
|
| There is an active interaction involving a live agent |
|
| There is an active interaction involving a virtual agent |
|
An active SMS interaction represents an ongoing conversation between a requester's phone number and a company's phone number.
Agent initiated SMS conversations
To initiate an SMS conversation with a requester, agents can select a provider number for an outbound service or manually enter a provider number. If there is a current ongoing SMS conversation, it automatically appears. When an agent initiates an SMS conversation:
| If | Then |
|---|---|
| There is no active SMS interaction |
|
| There is an active interaction involving an agent |
|
| There is an active interaction involving VA |
|
| There is an active interaction involving a different contact/consumer/user |
|
An active SMS interaction represents an ongoing conversation between a requester’s phone number and a company’s phone number.