Agent initiated SMS conversation
Summarize
Summary of Agent Initiated SMS Conversation
ServiceNow's Customer Service Management now supports SMS as a messaging channel, enabling agents to track interactions with customers. This feature enhances communication efficiency by allowing SMS conversations to be initiated directly by agents.
Show less
Key Features
- Provider Configuration: At least one messaging provider must be configured to access the Compose SMS option on the agent interaction screen.
- Phone Number Validation: A REST endpoint validates phone numbers against the E.164 format, converting non-compliant numbers automatically.
- Customer Profile Validation: Another REST endpoint checks the association of phone numbers with customer profiles to ensure accurate communication.
- SMS Interaction Management: The system differentiates between active interactions, allowing for either new conversations or continuations of existing ones based on the context.
- Customization Options: The behavior of send from and to numbers can be customized through the AgentInitiatedConversationUtil extension point.
Key Outcomes
By utilizing the SMS conversation feature, agents can:
- Efficiently manage customer interactions through a familiar messaging platform.
- Ensure accurate communication by validating phone numbers and customer profiles.
- Streamline workflow by automatically associating phone numbers with the correct consumer profiles.
- Customize messaging behaviors to align with organizational needs.
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.