Prerequisites

  • Genesys Cloud CX 1 Digital Add-on II, Genesys Cloud CX 2, Genesys Cloud CX 2 Digital, or Genesys Cloud CX 3 Digital license
  • Dedicated SMS number
  • OAuth client credentials
  • Conversation > Message > Create permission assigned to a role

    The agentless SMS notifications feature allows you to send SMS notifications without involving an agent. This feature allows Genesys Cloud to send SMS notifications from backend systems automatically, based on triggered events. The agentless SMS notifications feature also allows you to send SMS notifications from an Architect flow using a data action.

    For example, suppose that you want to notify your customer that you shipped a product that they ordered. You can configure Genesys Cloud to send an SMS message to your customer with shipping and tracking information. Or, suppose that you want to remind your customers of upcoming appointments. You can configure Genesys Cloud to send an SMS message to your customer with appointment confirmation details, such as date, time, or location.

    You access agentless SMS notifications using a public API. For more information, see the Conversations page and the Agentless SMS notifications page in the Developer Center.

    Trigger events

    To configure agentless SMS notifications based on triggered events from backend systems:

    1. Create or use an existing OAuth client. For more information, see Create an OAuth client.
    2. Use your OAuth client’s credentials to generate a token. For more information, see Grant – Client Credentials.
    3. Use your new token to call the new Agentless API endpoint. For more information, see the Agentless SMS API and the Agentless SMS Tutorial on the Developer Center.

    Architect flow

    To configure agentless SMS notifications from an Architect flow:

    1. Create a data action that calls the SMS notification API. For more information, see About the Genesys Cloud data actions integration.
    2. Use that data action within the flow. For more information, see Use data actions in Architect for integrations.
    Notes: 
    • Format destination numbers using the E.164 format.
    • Make sure to provision source numbers within the organization.
    • Only send messages to numbers where you collect and store the appropriate opt-in to SMS.
    • Standard SMS pricing applies to outbound SMS sent by the Agentless SMS API. 
    • The Agentless SMS API, by default, cannot send messages to a customer with a connected SMS conversation. A connected SMS conversation is an active conversation between a customer and your organization, either in flow, in-queue, or connected to an agent or a bot. Using an optional attribute on the API call, the default behavior can be changed to send an agentless message on a connected conversation. However, if the conversation is connected to a bot, the bot will interpret the message as received from the customer.