Conversational SMS service channel
Summarize
Summary of Conversational SMS service channel
The Conversational SMS service channel app enables workspace agents in ServiceNow to manage and support long-running SMS conversations alongside other service channels. Requesters can initiate support requests via SMS, and agents can track, continue, and respond to these multi-session SMS interactions directly from the Workspace Inbox. The app minimizes system messages for requesters to enhance the SMS conversation experience.
Show less
Messaging Profiles
Messaging profiles link incoming phone numbers to requester records to streamline interaction management:
- If the phone number matches a user in the User [sysuser] table but lacks a messaging profile, the app creates one and associates the interaction with that user.
- If there’s no phone number match but a messaging profile exists, interactions associate with that profile, allowing agents to verify user details manually.
- If no matches exist, interactions associate with a guest user, and a messaging profile is created without a user association.
- Conflicts between profiles or users trigger association to the current profile, with agents able to manually correct associations.
Messaging Actions
Messaging actions automate responses or workflow changes based on message activity:
- Events trigger timers when messages are sent by requesters or agents without responses.
- Actions include prompting agents or requesters, reassigning interactions, or updating interaction states.
- Filters define conditions under which actions trigger, such as interaction state.
Managing Ongoing Conversations
The Agent Inbox features an Ongoing tab for SMS conversations, highlighting new messages. Because SMS support can span long durations, completed conversations are excluded from Ongoing to keep the workspace focused. This supports efficient multitasking across multiple channels.
Requester-Initiated SMS Conversations
When a requester sends an SMS:
- If no active SMS interaction exists, a new one is created and assigned to a virtual or live agent.
- If an active interaction exists with a live agent, the message continues in the current conversation.
- If an active interaction exists with a virtual agent, the conversation continues with that agent and topic.
Advanced Work Assignment routes SMS conversations like other service channels, ensuring efficient allocation.
Agent-Initiated SMS Conversations
Agents can start SMS conversations by selecting or entering a provider number. Handling depends on current interactions:
- No active interaction: creates a new interaction and assigns it to the agent.
- Active interaction with an agent: continues the conversation, adding the agent to the live group.
- Active interaction with a virtual agent: closes the existing interaction and starts a new one with the agent.
- Active interaction with a different user: closes the old interaction, creates a new user profile, and starts a new interaction.
Setup
To use these capabilities, customers must configure the Conversational SMS service channel app from the ServiceNow Store, enabling workspace agents to manage SMS conversations seamlessly within their existing workflows.
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.