Loading...
Loading...
Loading...
As an administrator, you can use Genesys Cloud messaging to enable your customers to use Apple Messages for Business (AMB) to send direct messages. Apple Messages for Business requires organizations to meet Apple’s customer engagement and experience standards. To support a successful implementation and Apple Experience Review, Genesys assigns an AMB subject matter expert (SME) to guide organizations through implementation best practices and Apple’s review requirements.
Before you begin configuring AMB, contact your Genesys account or partner manager to request an AMB SME for your region.
You can configure Apple Messages by performing the following steps.
For more information about setup from Apple, see Onboarding with Apple Messages for Business.
Before you begin implementing Apple Messages for Business, contact your Genesys account or partner manager to request an AMB subject matter expert (SME) for your region.
Genesys assigns an SME to help your organization:
Work with your assigned SME throughout the implementation and review process to help ensure that your AMB experience meets Apple’s requirements.
Before configuring Apple Messages for Business, identify and document the customer engagement use cases that your organization plans to support.
Work with your assigned Genesys AMB SME to define your use cases and review Apple’s messaging experience requirements. Documenting use cases early helps establish the intended customer experience and can streamline the Apple Experience Review process.
To prepare your use cases:
For more information, see Apple’s Apple Messages for Business documentation.
Before you configure ACD messaging for AMB, you must have an Apple account for your business.
To set up your test Apple account, perform the following steps:
Next, register your test Apple business account to connect to Genesys Cloud as your Messaging Service Provider (MSP).
To register for an AMB account, perform the following steps:
| Genesys Cloud Region | AWS Region Name | MSP URL |
| Asia Pacific – Mumbai | ap-south-1 (APS1) | https://apple-messages.aps1.pure.cloud/api/v2/apple |
| Asia Pacific – Osaka | ap-northeast-3 (APNE3) | https://apple-messages.apne3.pure.cloud/api/v2/apple |
| Asia Pacific – Seoul | ap-northeast -2 (APNE2) | https://apple-messages.apne2.pure.cloud/api/v2/apple |
| Asia Pacific – Sydney | ap-southeast-2 (APSE2) | https://apple-messages.mypurecloud.com.au/api/v2/apple |
| Asia Pacific – Tokyo | ap-northeast-1 (APNE1) | https://apple-messages.mypurecloud.jp/api/v2/apple |
| Canada | ca-central-1 (CAC1) | https://apple-messages.cac1.pure.cloud/api/v2/apple |
| Europe – Frankfurt | eu-central-1 (EUC1) | https://apple-messages.mypurecloud.de/api/v2/apple |
| Europe – Ireland | eu-west-1 (EUW1) | https://apple-messages.mypurecloud.ie/api/v2/apple |
| Europe – London | eu-west-2 (EUW2) | https://apple-messages.euw2.pure.cloud/api/v2/apple |
| Europe – Zurich | eu-central-2 (EUC2 ) | https://apple-messages.euc2.pure.cloud/api/v2/apple |
| Middle East – UAE | me-central-1 (MEC1) | https://apple-messages.mec1.pure.cloud/api/v2/apple |
| South America – São Paulo | sa-east-1 (SAE1) | https://apple-messages.sae1.pure.cloud/api/v2/apple |
| US East – N. Virginia | us-east-1 (USE1) | https://apple-messages.mypurecloud.com/api/v2/apple |
| US West – Oregon | us-west-2 (USW2) | https://apple-messages.usw2.pure.cloud/api/v2/apple |
After you complete all steps, the status of the profile is under review. When Apple completes the review, the status of the profile changes to Active. Click the image to enlarge.
Set up your AMB integration manually if Genesys Cloud does not open automatically. To create the AMB integration manually, perform the following steps:
After you configure the Apple integration, you can configure message flows in Architect. For more information, see Inbound message flows overview. You can test your AMB using two methods:
To test your AMB account, perform the following steps:
Use the Authentication (Optional) section to configure OAuth2 settings for your AMB flows.
To set up authentication, perform the following steps:
| Genesys Cloud Region | AWS Region Name | MSP URL |
| Asia Pacific – Mumbai | ap-south-1 (APS1) | https://api.aps1.pure.cloud/api/v2/conversations/messaging/ oauth/apple/callback |
| Asia Pacific – Osaka | ap-northeast-3 (APNE3) | https://api apne3.pure.cloud/api/v2/conversations/messaging/ oauth/apple/callback |
| Asia Pacific – Seoul | ap-northeast -2 (APNE2) | https://api.apne2.pure.cloud/api/v2/conversations/messaging/ oauth/apple/callback |
| Asia Pacific – Sydney | ap-southeast-2 (APSE2) | https://api.mypurecloud.com.au/api/v2/conversations/messaging/ oauth/apple/callback |
| Asia Pacific – Tokyo | ap-northeast-1 (APNE1) | https://api.mypurecloud.jp/api/v2/conversations/messaging/ oauth/apple/callback |
| Canada | ca-central-1 (CAC1) | https://api.cac1.pure.cloud/api/v2/conversations/messaging/ oauth/apple/callback |
| Europe – Frankfurt | eu-central-1 (EUC1) | https://api.mypurecloud.de/api/v2/conversations/messaging/ oauth/apple/callback |
| Europe – Ireland | eu-west-1 (EUW1) | https://api.mypurecloud.ie/api/v2/conversations/messaging/ oauth/apple/callback |
| Europe – London | eu-west-2 (EUW2) | https://api.euw2.pure.clouddomain}/api/v2/conversations/messaging/ oauth/apple/callback |
| Europe – Zurich | eu-central-2 (EUC2 ) | https://api.euc2.pure.cloud/api/v2/conversations/messaging/ oauth/apple/callback |
| Middle East – UAE | me-central-1 (MEC1) | https://api.mec1.pure.cloud/api/v2/conversations/messaging/ oauth/apple/callback |
| South America – São Paulo | sa-east-1 (SAE1) | https://api.sae1.pure.cloud/api/v2/conversations/messaging/ oauth/apple/callback |
| US East – N. Virginia | us-east-1 (USE1) | https://api.mypurecloud.com/api/v2/conversations/messaging/ oauth/apple/callback |
| US West – Oregon | us-west-2 (USW2) | https://api.usw2.pure.cloud/api/v2/conversations/messaging/ oauth/apple/callback |
Use the iMessage App (Optional) section to configure iMessage application settings for AMB bot flows.
Use the Apple Pay (Optional) section to configure a merchant account for transmitting Apple Pay messages to your customers.
developer.apple.com. The URL you enter must match the domain name of the merchant account.merchant.pemmerchant.keyTo move your AMB account to production, you must submit your messaging experience to Apple for review and approval.
Plan to submit your experience at least three weeks before your planned go-live date to allow sufficient time for Apple’s review and any required adjustments. Work with your assigned Genesys AMB SME to prepare your experience for review. Ensure that your messaging experience reflects your documented use cases and follows Apple’s customer engagement guidelines. For more information about the experience review process, see Experience review process.
To pass the Apple experience review, perform the following steps:
After Apple approves your experience, you can proceed with creating your commercial Messages for Business account. For more information, see Step 13: Go Live.
After Apple approves your messaging experience, create a commercial Messages for Business account for your organization. During configuration and testing, you use an internal test account. Before going live, you must create a commercial account for production use.
Get user feedback about articles.