Agentless email notifications
Prerequisites
- Genesys Cloud CX 1 Digital Add-on II, Genesys Cloud CX 2, Genesys Cloud CX 3, Genesys Cloud CX 2 Digital, or Genesys Cloud CX 3 Digital license
- Provisioned campaign domain
- OAuth client credentials
- Conversation > Agentless Email > Send permission assigned to a role
The agentless email notifications allows you to send email notifications automatically without involving an agent. For example, you want to notify your customer about the shipment of a product that they ordered. You can configure Genesys Cloud to send an email 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 email message to your customer with appointment confirmation details, such as date, time, or location.
Features
- If you set up an inbound email domain, your customer can reply to your agentless emails. Genesys Cloud treats the reply email as an ACD email.
- When your customer replies to your agentless email within 30 days of the original email, Genesys Cloud threads the emails.
- If separate agentless emails have the same context of discussion, you can thread them with a single conversation ID from the API.
- SparkPost supports Sender Policy Framework (SPF), DomainKeys Identified Mail (DKIM), and Domain-based Message Authentication, Reporting & Conformance (DMARC). SPF is included with the CNAME record and DMARC is included with the TXT (DKIM) record.
- You can view the delivery receipt of emails from the Performance > Workspace > Interactions tab.
For more information about agentless email pricing, see Email pricing.
Access to agentless email
- If you have the Genesys Cloud CX 2 or Genesys Cloud CX 3 license after November 2, 2022, then you have access to Outbound Email Campaigns/Agentless Email by default.
- If you have the Genesys Cloud CX 2 or Genesys Cloud CX 3 license before this date, you can activate the feature in the Genesys AppFoundry:
If you are a direct customer or a partner, here are the steps you must take:
-
- After you log in to Genesys Cloud, go to the AppFoundry listing.
Note: Log in with your Genesys Cloud credentials.
- Review all details about the feature, including pricing.
- Click Purchase to agree to the terms and to enable the features in your organization.
- After you log in to Genesys Cloud, go to the AppFoundry listing.
If you are an indirect customer, and do not see the Purchase button after following the steps outlined above, contact your Genesys Partner.
Set up Genesys Cloud to send agentless emails
Genesys Cloud offers the ability to send email notifications in different ways:
- From back-end systems automatically based on triggered events.
- From an Architect flow using a data action.
- From an agent script using a data action (when you do not have to specify the user context in the API request). For more information, see Enable a script to use external data.
Send emails following trigger events
To configure agentless email notifications following the occurrence of triggered events from back-end systems:
- Set up a domain for outbound email campaigns. For more information, see Set up a domain for outbound email campaigns.
- Create or use an existing OAuth client. For more information, see Create an OAuth client.
- Use your OAuth client’s credentials to generate a token. For more information, see Grant – Client Credentials.
- Use your new token to call the new Agentless API endpoint.
Send emails from Architect flow
To configure agentless email notifications from an Architect flow:
- Create a data action that calls the email notification API. For more information, see About the Genesys Cloud data actions integration.
- Use that data action within the flow. For more information, see Use data actions in Architect for integrations.
Limits
The following limits apply to agentless emails:
Item | Limit |
---|---|
Rate of number of emails |
|
Rate of number of emails for agentless plus (campaign emails) |
|
Size |
|
Characters |
|
Email address |
Only one recipient email address at a time. |