Agent initiated SMS conversation
Summarize
Summary of Agent Initiated SMS conversation
ServiceNow Customer Service Management now supports SMS as an additional messaging channel, enabling agents to initiate and track SMS conversations with customers directly within the agent interaction interface. This functionality enhances communication flexibility and improves customer engagement by integrating SMS interactions seamlessly into the service workflow.
Show less
Requirements
- A configured messaging channel provider must be available to display the "Compose SMS" option for agents.
- Phone numbers are validated and converted to the E.164 international format using the REST endpoint
/api/now/initiatemessage/validatephonenumber, ensuring consistent and standardized phone number handling. - Customer profiles are validated via the REST endpoint
/api/now/initiatemessage/validateprofileto manage phone number associations with consumers, preventing conflicts when numbers are linked to multiple customers.
Agent Initiated SMS Conversations
Agents can start SMS conversations by selecting or entering a provider number. The system manages interactions as follows:
- No active SMS interaction: A new SMS interaction is created and assigned to the agent.
- Active interaction with the same agent: The new message is added to the existing conversation without reassignment.
- Active interaction with a Virtual Agent (VA): The existing interaction is closed, and a new one is created and assigned to the agent.
- Active interaction with a different contact or consumer: The current interaction is closed, the existing channel user profile is deactivated, a new user profile is created, and a new interaction is assigned to the agent.
Customization
The AgentInitiatedConversationUtil extension point allows customers to customize the logic for assigning "Send from" and "Send to" numbers in SMS conversations, adapting the default system behavior to specific business needs. For this purpose, the AgentInitiatedMessagingUtilExtPointImpl is configured to fetch these numbers appropriately.
Related Operational Tasks
- Monitoring agent presence and capacity
- Managing unassigned interactions and task work items
- Handling work items and Automatic Work Assignment (AWA) events
- Composing SMS conversations within the agent workspace
Customer Service Management supports additional messaging channel such as SMS which tracks interactions between the agent and customer.
Requirements
At least one provider configuration for messaging type channel must be available to view the Compose SMS option in the agent interaction screen. For more information about provider sys_cs_provider_application.list, see Create a channel identifier.
Phone number validation
REST endpoint /api/now/initiate_message/validate_phone_number is used to validate if the phone number is in the E.164 format. If the number of a known consumer is not in the E.164 format, the system converts it to the E.164 format based on for example, the location of the consumer. If the location is not found, it will by default convert the number to an E.164 format. For more information about E.164 formats and validation, see Phone number field type.Customer profile validation
REST endpoint /api/now/initiate_message/validate_profile is used to validate the channel user profile. When you send an SMS in reply to an interaction of type phone, the message is sent to a consumer originally associated with the interaction. If the same phone number is associated to a different consumer, and you send an SMS, you will get a message that the phone number is currently associated to another consumer and sending the new message will associate the phone number to the current user.
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 |
|
Customize the behaviour of send from and to numbers
The AgentInitiatedConversationUtil extension point is added to implement a customers' logic to change the default behaviour of the Send from and Send to fields. For more information, see Associating user profiles on messaging interactions. For this store application, AgentInitiatedMessagingUtilExtPointImpl extension point is configured for fetching the from and to numbers.