Select Language:
If you’ve set up a WhatsApp Business Account (WABA) on AWS End User Messaging and linked it to an AWS Connect instance, but you can’t see the phone number in your Connect dashboard, here are some steps to troubleshoot and resolve the issue:
First, confirm that your WABA is in an active state. Even if it appears active, ensure that all setup steps were completed correctly, and the registration process with the third-party Italian SIM card was successful.
Next, verify that the destination event in your setup points correctly to your AWS Connect instance. It’s good that switching the destination to an SNS topic that forwards emails worked—this shows the messaging and event flow are functioning properly overall, just not connecting to Connect.
Since you already tried switching the destination back to Connect without success and your IAM policies seem to have the proper permissions, the next step is to double-check the Connect instance configuration:
– Make sure the Connect instance is correctly configured to accept messages from the WABA. Sometimes, specific settings or permissions within Connect need to be enabled.
– Check if the phone number associated with WABA is correctly linked or registered within your Connect instance. This may involve verifying the number format and registration status.
– Review your Connect contact flow and routing profiles to see if anything is blocking or filtering incoming messages from your WABA number.
– Ensure your AWS region and account settings are consistent across all components so that there are no mismatches.
If everything seems correct but the number still doesn’t appear, consider contacting AWS support. They can review your specific setup and logs to identify any hidden issues that might prevent the number from appearing in Connect.
By carefully reviewing your configuration, ensuring proper registration, and confirming permissions and settings within AWS Connect, you should be able to resolve the visibility issue of your WhatsApp number.





