UseCases/Current/GenesysCloud/CE12 - Revision history

Shlandy93: UCC: Republished use case to include email capabilities

2022-11-22T12:35:31Z

UCC: Republished use case to include email capabilities

Show changes

Ed.jamer@genesys.com: Text replacement - "Genesys Cloud" to "Genesys Cloud CX"

2021-11-09T21:28:54Z

Text replacement - "Genesys Cloud" to "Genesys Cloud CX"

Shane.landy@genesys.com: UCC: Added Video

2021-05-26T10:04:18Z

UCC: Added Video

Shane.landy@genesys.com at 14:54, April 14, 2021

2021-04-14T14:54:06Z

Shane.landy@genesys.com: UCC: Updated link

2021-04-14T14:20:48Z

UCC: Updated link

Shane.landy@genesys.com: Published use case

2021-03-09T10:52:13Z

Published use case

New page

{{SMART UseCase
|ID=CE12
|Offering=GenesysEngage-cloud
|SMART_Benefits={{SMART Benefits
|UCBenefitID=Improved Customer Experience
|UCBenefit=Improve Net Promoter Score (NPS) by proactively notifying customers through SMS.
}}{{SMART Benefits
|UCBenefitID=Reduced Volume of Interactions
|UCBenefit=Decrease inbound interactions by proactively sending communications through SMS.
}}{{SMART Benefits
|UCBenefitID=Improved Employee Utilization
|UCBenefit=Reduce agent-assisted outbound calls by automatically sending communications through SMS.
}}{{SMART Benefits
|UCBenefitID=Improved Conversion Rates
|UCBenefit=Conversion rates, close rates, cross-sells, and up-sell rates improve through the ability to automatically generate outbound SMS messages and empower agents with single a searchable desktop application that shows customer context.
}}
|UCOverview=Consumers want businesses to send them proactive notifications when that information is personalized, timely, and relevant. The SMS channel is an efficient, quick way to notify customers of appointment reminders, delivery notifications, fraud alerts, coupons, loyalty program information, surveys, and much more. Many companies struggle with adding the SMS channel to their outbound notification strategy for marketing, care, or collections. This use case offers the ability to configure and run outbound SMS campaigns based on customer-provided contact lists.
|UCSummary=This use case illustrates how companies proactively send customer notifications using SMS for marketing, care, or collections purposes using contact lists. The lists include the appropriate contact details, such as contact name, mobile phone number, and contact reason. The system records delivery results to feed into reports. Public APIs are useful to send a message based on a one-time event, recurring events, or trigger-based events without needing to build and maintain a traditional "blast" campaign.

Outbound SMS notification examples include:
{{{!}} style="width: 695px;" border="1" data-mce-style="width: 695px;"
{{!}}-
! style="width: 186px;" data-mce-style="width: 186px;"{{!}}Financial Services
! style="width: 165px;" data-mce-style="width: 165px;"{{!}}Telecom
! style="width: 160px;" data-mce-style="width: 160px;"{{!}}Healthcare
! style="width: 158px;" data-mce-style="width: 158px;"{{!}}Utilities
{{!}}-
{{!}} style="width: 186px;" data-mce-style="width: 186px;"{{!}}
*New customer engagement
*Replenish prepaid card reminders
*Payment reminders
*Fraud alerts
{{!}} style="width: 165px;" data-mce-style="width: 165px;"{{!}}
*Review plan alerts
*Payment reminders
*Upgrade eligibility
*Customer win-back
{{!}} style="width: 160px;" data-mce-style="width: 160px;"{{!}}
*Appointment reminders
*Wellness updates
*Refill prescriptions
*Claim status updates
{{!}} style="width: 158px;" data-mce-style="width: 158px;"{{!}}
*Service call confirmation
*Planned downtime
*Outage status
*Payment reminders
{{!}}-
! style="width: 186px;" data-mce-style="width: 186px;"{{!}}Retail
! style="width: 165px;" data-mce-style="width: 165px;"{{!}}Insurance
! style="width: 160px;" data-mce-style="width: 160px;"{{!}}Collection Agencies
! style="width: 158px;" data-mce-style="width: 158px;"{{!}}Travel and Hospitality
{{!}}-
{{!}} style="width: 186px;" data-mce-style="width: 186px;"{{!}}
*Sales alerts
*Order confirmations
*Product recalls
*Loyalty program activity
*Shipment and delivery status
{{!}} style="width: 165px;" data-mce-style="width: 165px;"{{!}}
*Quote follow-up
*Payment reminders
*Claims status updates
*Renewal notice
{{!}} style="width: 160px;" data-mce-style="width: 160px;"{{!}}
*Payment reminders
*Late payment alterations
*Payment confirmations
{{!}} style="width: 158px;" data-mce-style="width: 158px;"{{!}}
*Booking confirmation
*Upselling service
*Payment reminders
*Travel updates
*Loyalty program activity
{{!}}}
|PainPoints=* Unable to keep customers informed about their accounts and the products and services they use
* Can’t engage with customers over their preferred channels
* Unable to deflect avoidable inbound contacts resulting in higher agent costs and lower satisfaction
|DesiredState=* Proactively sending timely and personalized alerts, confirmations, and reminders using multiple channels results in lower customer effort and fewer inbound interactions
* Contact consumers in accordance to their channel preferences (this use case assumes the company provides contact list with only opted-in customers)
* Reduce outreach costs by leveraging less expensive text messaging versus agent calls
|BuyerPersonas=Chief Digital Officer, Head of Customer Experience, Head of Customer Service
|MaturityLevel=Consistent
|BusinessImageFlow={{SMART BusinessImageFlow
|BusinessFlow=(1) Trigger-based SMS
|BusinessImage=https://www.lucidchart.com/documents/edit/41ff724d-36fb-48cc-a949-d42891c59a68/0
|BusinessFlowDescription=#Create or use an existing OAuth client
#*Customers need an OAuth client with the <code>Conversation:Message:Create</code> permission assigned to the OAuth client. See [https://help.mypurecloud.com/articles/create-an-oauth-client/ link] for more info.
#Generate an OAuth client token
#*To call the endpoint to send agentless outbound SMS notifications, customers need to use an OAuth client to [https://developer.mypurecloud.com/api/rest/authorization/use-client-credentials.html generate a token]. <br /> They need to make sure to build the basePath for the correct Genesys Cloud region they are working in. For more information, see [https://developer.mypurecloud.com/api/rest/ link].
#Use the OAuth client token to call the agentless outbound SMS endpoint. For more information reference the [https://developer.mypurecloud.com/api/tutorials/agentless-sms-notifications/ tutorial].

<br />
}}{{SMART BusinessImageFlow
|BusinessFlow=(2) Campaign-Based SMS
|BusinessImage=d78c4195-c2f7-44c3-97fe-d74c07ec6dd4
|BusinessFlowDescription=#An Admin (or Genesys PS) configures the campaign settings in Genesys.
#The organization either prepares a contact list from a third-party system (such as CRM) or configures their system to use Genesys REST APIs to insert contact records.
#*Batch Upload Option: Customer contacts are loaded through the User Interface using a .csv file.
#*API Upload Option: Customer contacts are loaded through a Genesys Cloud API call. Customers can set a flag in the API to add the contact to the top of the list.
#The customer can specify the SMS message body for each contact record by assigning a column in the list as the message column. Customers can also use a message content template to create a dynamic message using data from the contact list. Best practice recommends that if hyperlinks are used in the message body that the total message content is no greater than 160 characters to avoid splitting the hyperlink across multiple text messages. The consumer’s mobile phone provider determines the concatenation of an long message. Messages longer than 160 characters may be concatenated into one message by the mobile provider or may arrive as multiple messages.
#The campaign is started and begins contacting consumers based on the settings configured in the first step. The Genesys system checks each contact/record against the Do Not Call lists assigned to the campaign to filter out consumers who should not be contacted.
#Message send fail or success status is stored on the interaction.
#Consumer may decide to respond to the SMS message. Responses will thread with the original outbound SMS message for a configured amount of time with the available metadata from the SMS message to identify the consumer.
#*For a HELP keyword, a customer-specified help text is sent to the consumer.
#*For a STOP keyword, a default or customer-specified text is sent to the consumer, and the mobile number is added to a suppression list by the aggregator so further messages are blocked by the aggregator.
#*For a START or UNSTOP keyword, the aggregator begins allowing further messages to the consumer.
}}
|BusinessLogic=====Agentless SMS Notifications====
Customers typically use agentless SMS notifications when triggering an SMS based on an event such as: purchase, scheduled appointment, two factor authorization, and so on. The customer must have an external system invoking the API call to send the message. These trigger-based notifications are not sent all at once. As such, trigger-based notifications do not use traditional outbound campaigns. However, they are included within interaction views and reporting.

====Standard SMS Keywords====
Standard opt-out keywords include STOP and UNSUBSCRIBE and additional variations including: END, QUIT, CANCEL and STOPALL

Standard help keywords include HELP and INFO.

Standard opt-in keywords include START, YES and UNSTOP.

====SMS Campaigns====

====Contact List====

*The organization either prepares a contact list from a third-party system (such as CRM) or configures their system to use Genesys Cloud APIs to insert contact records.
*Batch Upload Option: Customer contacts are loaded through the User Interface using a .csv file.
*API Upload Option: Customer contacts are loaded through a Genesys Cloud API call. Customers can set a flag in the API to add the contact to the top of the list.

====Campaign====

*The campaign is started and begins contacting consumers based on the campaign settings configured. The Genesys Cloud system checks each contact record against the Do Not Call list(s) assigned to the campaign to filter out consumers who should not be contacted. The customer can specify the SMS message body for each contact record by assigning a column in the list as the message column. Alternatively the message body can be specified in a SMS campaign templated associated with the campaign. Best practice recommends that if hyperlinks are used in the message that the total message content is no more than 160 characters to avoid splitting the hyperlink across multiple text messages.
*The consumer’s mobile phone provider determines the concatenation of an long message. Messages longer than 160 characters may be concatenated into one message by the mobile provider or may arrive as multiple messages. Genesys stores the SMS sent success or failure status of a message on the interaction. Consumer may decide to respond to the SMS message. Responses will thread with the original outbound SMS message for a configured amount of time with the available metadata from the SMS message to identify the consumer. For a HELP keyword, a customer-specified help text is sent to the consumer. For a STOP keyword, a default or customer-specified text is sent to the consumer, the mobile number is added to a suppression list by the aggregator, and further messages are blocked by the aggregator. For a START or UNSTOP keyword, the aggregator begins allowing further messages to be sent to the consumer.
|DistributionLogic=This section is not applicable for this use case.
|CustomerInterfaceRequirements=This section is not applicable for this use case.
|AgentDeskRequirements=This section is not applicable for this use case.
|RealTimeReporting=Live messaging campaign information can be found on the Messaging Campaigns tab on the Campaign Management dashboard.

*Campaigns can be turned on/off
*Campaign progress is shown with the number of total contacts and the number of processed contacts
*Campaign attributes such as name, contact list, and division are also provided
|HistoricalReporting=Dialer Campaign Detailed Attempt History can be used to display the individual:

*Number of SMS attempts
*DateTime of SMS attempt
*Campaign and queue
*Contact ID
*Number of SMS messages rejected by the aggregator
*Number of SMS messages accepted by the aggregator

Further information about campaign results can be found by exporting the contact list such as:

*Records skipped, for example, the contact is listed on a "do not contact list" assigned to a campaign

Customers can have ultimate flexibility by using the Interactions View to show detailed results of a campaign, including applying filters and choosing data columns, and also export as .csv or .pdf. '''Note: This view is the only method available to see details when using the agentless API method of sending SMS messages.'''
|GeneralAssumptions=*The customer cannot use a third-party SMS aggregator.
*Our aggregator stores opt-out requests and blocks messages if a customer attempts to send them to a consumer. This is accomplished by the consumer using keywords such as STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, or QUIT. If the consumer wants to resume messages (opt-in), they can use keywords such as START, YES, and UNSTOP. Genesys also supports custom keywords for opt-in and opt-out requests.
*For SMS campaigns, customers must acquire a short code in North America.

<br />
|CustomerAssumptions=*Customer provides Genesys with the contact list from their own CRM, marketing, or collections database - either via uploading a .csv file in the user interface or using API endpoints to add contacts to a contact list.
*Compliance is handled by the customer. The customer has the responsibility for securing express consent from consumers (when required) before sending SMS messages, maintains an auditable list, and honors opt-out requests. The contact lists loaded into Genesys should contain only consumers to whom an SMS message can be sent according to the corresponding local compliance rules.
*The outbound solution is configured based on the customer's understanding and direction of compliance with local outbound SMS regulations at the site of installation as well as at the local regulations at the site of delivery of SMS messages. The customer is responsible for compliance with laws and regulations concerning outbound SMS and automatic sending of SMS. It is recommended that the customer's legal department assert that the organization is in full compliance with these regulations as SMS messages are sometimes considered the same as voice calls with regard to compliance.
*The sender number (dedicated short code or long code) is provisioned on the Genesys system.
*MMS is not included in the scope of this use case.
*SMS throughput is limited to one message per second when using long-codes. Genesys SMS campaigns can deliver up to 25/sec when using short codes.
|DocVersion=V 1.0.0
}}

@@ Line 89: / Line 89: @@
 #*Customers need an OAuth client with the <code>Conversation:Message:Create</code> permission assigned to the OAuth client. See [https://help.mypurecloud.com/articles/create-an-oauth-client/ link] for more info.
 #Generate an OAuth client token
-#*To call the endpoint to send agentless outbound SMS notifications, customers need to use an OAuth client to [https://developer.mypurecloud.com/api/rest/authorization/use-client-credentials.html generate a token].  <br /> They need to make sure to build the basePath for the correct Genesys Cloud region they are working in. For more information, see [https://developer.genesys.cloud/ link].
+#*To call the endpoint to send agentless outbound SMS notifications, customers need to use an OAuth client to [https://developer.genesys.cloud/api/rest/authorization/use-client-credentials.html generate a token].  <br /> They need to make sure to build the basePath for the correct Genesys Cloud region they are working in. For more information, see [https://developer.genesys.cloud/api/rest/ link].
-#Use the OAuth client token to call the agentless outbound SMS endpoint.  For more information reference the [https://developer.mypurecloud.com/api/tutorials/agentless-sms-notifications/ tutorial].
+#Use the OAuth client token to call the agentless outbound SMS endpoint.  For more information reference the [https://developer.genesys.cloud/api/tutorials/agentless-sms-notifications/ tutorial].
 <br />

@@ Line 89: / Line 89: @@
 #*Customers need an OAuth client with the <code>Conversation:Message:Create</code> permission assigned to the OAuth client. See [https://help.mypurecloud.com/articles/create-an-oauth-client/ link] for more info.
 #Generate an OAuth client token
-#*To call the endpoint to send agentless outbound SMS notifications, customers need to use an OAuth client to [https://developer.genesys.cloud/api/rest/authorization/use-client-credentials.html generate a token].  <br /> They need to make sure to build the basePath for the correct Genesys Cloud region they are working in. For more information, see [https://developer.genesys.cloud/api/rest/ link].
+#*To call the endpoint to send agentless outbound SMS notifications, customers need to use an OAuth client to [https://developer.genesys.cloud/api/rest/authorization/use-client-credentials.html generate a token].  <br /> They need to make sure to build the basePath for the correct Genesys Cloud CX region they are working in. For more information, see [https://developer.genesys.cloud/api/rest/ link].
 #Use the OAuth client token to call the agentless outbound SMS endpoint.  For more information reference the [https://developer.genesys.cloud/api/tutorials/agentless-sms-notifications/ tutorial].
@@ Line 99: / Line 99: @@
 #The organization either prepares a contact list from a third-party system (such as CRM) or configures their system to use Genesys REST APIs to insert contact records.
 #*Batch Upload Option: Customer contacts are loaded through the User Interface using a .csv file.
-#*API Upload Option: Customer contacts are loaded through a Genesys Cloud API call. Customers can set a flag in the API to add the contact to the top of the list.
+#*API Upload Option: Customer contacts are loaded through a Genesys Cloud CX API call. Customers can set a flag in the API to add the contact to the top of the list.
 #The customer can specify the SMS message body for each contact record by assigning a column in the list as the message column. Customers can also use a message content template to create a dynamic message using data from the contact list.  Best practice recommends that if hyperlinks are used in the message body that the total message content is no greater than 160 characters to avoid splitting the hyperlink across multiple text messages. The consumer’s mobile phone provider determines the concatenation of an long message. Messages longer than 160 characters may be concatenated into one message by the mobile provider or may arrive as multiple messages.
 #The campaign is started and begins contacting consumers based on the settings configured in the first step. The Genesys system checks each contact/record against the Do Not Call lists assigned to the campaign to filter out consumers who should not be contacted.
@@ Line 122: / Line 122: @@
 ====Contact List====
-*The organization either prepares a contact list from a third-party system (such as CRM) or configures their system to use Genesys Cloud APIs to insert contact records.
+*The organization either prepares a contact list from a third-party system (such as CRM) or configures their system to use Genesys Cloud CX APIs to insert contact records.
 *Batch Upload Option: Customer contacts are loaded through the User Interface using a .csv file.
-*API Upload Option: Customer contacts are loaded through a Genesys Cloud API call. Customers can set a flag in the API to add the contact to the top of the list.
+*API Upload Option: Customer contacts are loaded through a Genesys Cloud CX API call. Customers can set a flag in the API to add the contact to the top of the list.
 ====Campaign====
-*The campaign is started and begins contacting consumers based on the campaign settings configured. The Genesys Cloud system checks each contact record against the Do Not Call list(s) assigned to the campaign to filter out consumers who should not be contacted.	 The customer can specify the SMS message body for each contact record by assigning a column in the list as the message column.  Alternatively the message body can be specified in a SMS campaign templated associated with the campaign.  Best practice recommends that if hyperlinks are used in the message that the total message content is no more than 160 characters to avoid splitting the hyperlink across multiple text messages.
+*The campaign is started and begins contacting consumers based on the campaign settings configured. The Genesys Cloud CX system checks each contact record against the Do Not Call list(s) assigned to the campaign to filter out consumers who should not be contacted.	 The customer can specify the SMS message body for each contact record by assigning a column in the list as the message column.  Alternatively the message body can be specified in a SMS campaign templated associated with the campaign.  Best practice recommends that if hyperlinks are used in the message that the total message content is no more than 160 characters to avoid splitting the hyperlink across multiple text messages.
 *The consumer’s mobile phone provider determines the concatenation of an long message.  Messages longer than 160 characters may be concatenated into one message by the mobile provider or may arrive as multiple messages. 	 Genesys stores the SMS sent success or failure status of a message on the interaction. Consumer may decide to respond to the SMS message. Responses will thread with the original outbound SMS message for a configured amount of time with the available metadata from the SMS message to identify the consumer.	 For a HELP keyword, a customer-specified help text is sent to the consumer.	 For a STOP keyword, a default or customer-specified text is sent to the consumer, the mobile number is added to a suppression list by the aggregator, and further messages are blocked by the aggregator.	 For a START or UNSTOP keyword, the aggregator begins allowing further messages to be sent to the consumer.
 |DistributionLogic=This section is not applicable for this use case.

@@ Line 163: / Line 163: @@
 *MMS is not included in the scope of this use case.
 *SMS throughput is limited to one message per second when using long-codes. Genesys SMS campaigns can deliver up to 25/sec when using short codes.
-|DocVersion=V 1.0.0
+|DocVersion=1.0.1
 }}