Loading...
Loading...
Loading...
The following FAQs provide guidance on WhatsApp onboarding, messaging behavior, integrations, limits, migrations, billing, compliance, and account management in Genesys Cloud.
The following table describes the most commonly encountered errors or scenarios during WhatsApp onboarding or when sending WhatsApp messages to your customers.
| Topic/category | Error and scenario | Suggested resolution |
|---|---|---|
| Embedded Signup Flow | An | If you are performing a migration, check if the two-factor authentication (2FA) is unavailable for your number in the source WABA. If you reintegrate a number that you previously integrated in Genesys Cloud; for example, in a different region or organization), make sure that you enter the six-digit PIN from the original integration. You can change the PIN for your number in WhatsApp Manager or you can request that Genesys change the PIN. |
| Template Messages – Per-User Marketing Message Limits | Error code: Description: Meta chose not to deliver the message. | WhatsApp limits the number of marketing template messages that a person receives from any business in a specified period. For more information, see Per-User Marketing Template Message Limit. |
| Template Messages – Marketing Experiments | Error code: Description: Message was not sent as part of an experiment. | WhatsApp does not send marketing messages to users who are part of the marketing message experiment. For more information, see Marketing Message Experiments. |
| Template Messages – Parameter Count Mismatch | Error Code: Description: The number of variable parameter values included in the request did not match the number of variable parameters defined in the template. | Your request must include all the variable parameter values that are defined in the template. |
| Template Messages – Template does not exist | Error Code: Description: The template does not exist in the specified language or the template has not been approved. | Check if the template you are using has been approved and the template name and language locale are correct. |
| Messages Not Delivered | For more information, see Support – Cloud API – Documentation – Meta for Developers | |
| Message Undeliverable | Error Code: Description: Meta cannot deliver the message. Reasons can include:
| If you are using communication methods other than WhatsApp, then:
|
If you do not have access to a Meta business portfolio, you cannot register WhatsApp numbers in Genesys Cloud. Also, Genesys Cloud requires Facebook/Meta Login to create WABAs and add phone numbers via the embedded signup flow.
For more information about Meta business portfolio or business manager account access, see:
If you are a partner and must access to your customer’s WABAs, work with your clients to gain access. Use either of the following options:
Add people to a business portfolio and assign a business asset. Clients can add individual people from the partner company to their business manager or portfolio and assign those individuals access to specific WABA assets.
Give a partner access to business assets. Clients can share their WABA with the partner without providing access to the Meta business account. This option is more secure. Here, the partner must have their own Meta business account. When the WABA is shared, they can view it from within their Meta account, depending on the assigned type of access.
Business verification confirms that your account belongs to a legitimate business or organization and that your business is a legal entity. Verification confirmation allows you to scale your traffic and qualify for higher messaging limits. Business verification provides:
For more information about Meta business verification, see:
You can register any phone number with a country and area code that can receive voice calls or SMS from international numbers. It can include:
Mobile phone numbers that you register on an Android or iOS WhatsApp Messenger or WhatsApp business app cannot migrate to the WhatsApp business platform. To reuse and register these numbers on the WhatsApp business platform through Genesys Cloud, you must first delete the WhatsApp mobile account first. Follow these instructions to delete the account from your mobile app permanently.
Submit your request to your Genesys Account Team. You can find that contact information in Orchestrators > Profile > My Contacts. Please include your Genesys Cloud region, Org ID, SMS number, and the voice-enabled number where you want to forward calls.
If your messages are sent before migration is complete or if you have undelivered messages sent before migration is complete, then your old solution partner is billed. If your messages are sent after the migration is complete, then your new solution partner will be billed.
No. You do not need to recreate templates in your destination WABA. They are automatically duplicated from your source WABA to the destination WABA and are granted the same quality ratings and statuses as their source counterparts. If you are migrating from Genesys Engage or another solutions provider, configure your templates as canned responses in Genesys Cloud.
To transfer your WhatsApp integration to the new region/org, perform the following steps:
OBAs have a green check mark or verified badge beside the display name in the Contacts view.
Navigate to Meta Business Support Home to check the status of your WhatsApp Business Accounts. Depending on WhatsApp’s Business or Commerce Policy violation, you can request a review of your restricted or inactive account.
For more information about reinstating your account, see Troubleshoot a restricted account
To change the display name for a phone number that is part of an existing embedded WABA review the display name guidelines and then perform the following steps:
You can manage your WhatsApp phone numbers and business profiles from the WhatsApp Manager within your Meta Business Portfolio/Manager. To update your business profile for your phone number, perform the following steps:
You can request message links or QR codes for your WhatsApp numbers from the WhatsApp Manager within your Meta Business Portfolio/Manager. For more information about how to manage QR codes, see Manage your WhatsApp Business platform QR code.
Yes, WhatsApp imposes a limit of 10 total buttons per template. If you configure more than 10 buttons in your canned response, the template message fails to deliver.
Only Utility and Marketing templates are currently supported in Genesys Cloud. These templates can contain the following components:
For more information about how to create a WhatsApp message template in your WABA, see Create message templates for your WhatsApp Business Account.
For more information, see:
For more information about adding and using the WhatsApp template messages, see Add a WhatsApp template message and Use a WhatsApp template message.
For more information about agentless WhatsApp notifications, see Agentless WhatsApp notifications. For more information about agent-initiated WhatsApp, Create and configure queues and Send an outbound message on behalf of a queue.
Yes, there are restrictions. For more information, see Country Restrictions. For more information about Meta’s data privacy, security, and compliance, see Data privacy and security, Compliance center, and Trust and safety.
You can run real time monitoring of messaging and spending analytics of your WhatsApp business account. You can also view the metrics of all conversations on the Insights tab of the WhatsApp Manager. The real time graphs enable you to look into the performance of each metric. For more information about how to view conversation insights for your WABA, see View conversation insights for your WhatsApp Business Account.
Yes, for all WhatsApp numbers registered through Genesys Cloud’s Embedded Signup process, Genesys’ credit line is attached to the WABA. Meta bills Genesys for all WhatsApp charges incurred for the WABA. Genesys passes these charges to customers or partners on invoices.
For more information about Genesys Cloud and WhatsApp pricing, see Messaging pricing and Pricing — WhatsApp Business Platform.
You can send an interactive template message on WhatsApp with a Call on WhatsApp action button to help consumers easily contact your support team. When a consumer taps this button, it starts a WhatsApp call to your business number just like tapping the call icon in the chat title bar. The button cannot be configured to call a different number.
You can set up the message by creating a template in WABA and when WhatsApp approves the temple, you can create and use it as a Canned Response in Genesys Cloud, just like any other message template.
Calling deep links are hyperlinks that let WhatsApp users directly call your business. The process to create a calling deep link is the same as creating a chat deep link.
Create the deep link in the following format: https://wa.me/call/<phone_number>. Replace <phone_number> with your full phone number in international format, including the country code.
https://wa.me/call/1XXXXXXXXXXhttps://wa.me/call/+001-(XXX)XXXXXXXYou can use calling deep links to promote WhatsApp calling for your business. For example, on your website, app, or marketing materials. You can also share them as QR codes to make calling even easier.
Also, you can send messages that include calling deep links, allowing WhatsApp users to contact a specific voice-enabled business number. The wa.me/call/<BUSINESS_PHONE_NUMBER> format is simple to copy, paste, and share and it doesn’t require creating a message template in WhatsApp business manager.
Yes. WhatsApp-imposed throughput limits apply independently of Genesys Cloud limits.
All inbound and outbound WhatsApp messages sent through Genesys Cloud are subject to WhatsApp Business Platform (Cloud API) throughput constraints per registered business phone number, regardless of any rate limits, throttling, or capacity configurations configured within Genesys Cloud.
By default, the WhatsApp Cloud API supports up to 80 messages per second (MPS) per business phone number (approximately 4,800 messages per minute). Sometimes, WhatsApp automatically upgrades throughput capacity up to 1,000 MPS.
Throughput limits apply to:
Even at higher throughput levels, business phone numbers remain subject to more WhatsApp constraints, including:
If message traffic exceeds the permitted throughput, WhatsApp enforces platform-level throttling. The Cloud API returns error code 130429 (Rate Limit Hit) until message traffic returns within allowed limits.
Customers running outbound campaigns—such as notifications, alerts, marketing messages, or large-scale proactive outreach—are responsible for designing campaign pacing, phone number strategy, and messaging volumes in accordance with WhatsApp’s throughput and rate-limit policies.
Yes. Genesys Cloud enforces outbound rate limits for WhatsApp messaging to ensure reliable delivery, controlled resource utilization, and compliance with platform and external provider constraints.
Customers planning high-volume outbound campaigns, notifications, alerts, or other proactive messaging use cases can request higher per-minute limits for their organization. To increase these limits, submit a request through Genesys Cloud Product Support.
The following limit applies to outbound WhatsApp campaigns at both the organization and per-campaign levels:
whatsapp.outbound.message.rate.per.minute
Agentless WhatsApp interactions have a separate rate limit, independent of campaign-based messaging:
agentless.outbound.whatsapp.message.rate.per.minute
Get user feedback about articles.