Integrating Lambda to Check Do Not Call List in Amazon Pinpoint Journey

Hello Kapil,

I understand you are trying to integrate a Lambda function into your Pinpoint journey to check if a user is on the Do Not Call list before initiating an outbound campaign through Connect. Below is a step-by-step guide on how you can set up this integration:

1. Write a Lambda function in your preferred language (Node.js, Python, etc.) that checks whether a given address (phone number or other identifier) is in the Do Not Call DynamoDB table.
2. Make sure your Lambda function returns a response indicating whether the user is on the Do Not Call list or not.

[+] https://docs.aws.amazon.com/pinpoint/latest/developerguide/tutorials-two-way-sms-part-3.html#tutorials-two-way-sms-part-3-create-register-function

3. In your Pinpoint journey, add a Yes/No split activity right before the Connect outbound campaign activity.
4. Connect the Yes/No split activity to the Lambda function by selecting "Check Do Not Call List".
5. In the split configuration, use the Lambda function as the decision endpoint.
6. Define conditions for both "Yes" and "No" outcomes based on the Lambda function response. For example, if the Lambda function indicates that the user is on the Do Not Call list, go to the "Yes" branch; otherwise, go to the "No" branch.
7. In the "Yes" branch, add an activity that sends the user to an endpoint with a message indicating they are on the Do Not Call list. This can be an SMS or any other appropriate channel for notification.
8. Connect No Branch to Connect Outbound Campaign Activity:
9. In the "No" branch, connect it to the Connect outbound campaign activity. This ensures that only users not on the Do Not Call list proceed to the outbound campaign.
10. Test the Journey:

Test the entire journey with a sample dataset that includes users both on and off the Do Not Call list. Monitor the execution of the Lambda function and the branching logic. In addition, I have found the below blogs which will give additional insights on various use cases.

[+] https://aws.amazon.com/blogs/contact-center/outbound-best-practices/

[+] https://aws.amazon.com/blogs/contact-center/event-based-outbound-campaigns-with-amazon-connect/

[+] https://aws.amazon.com/blogs/contact-center/caller-scheduled-callback-in-amazon-connect/

[+] https://aws.amazon.com/blogs/contact-center/creating-dynamic-personalized-experiences-in-amazon-connect/

If the Connect contact center is still triggered for users on the Do Not Call list, kindly review the Lambda function logs for potential issues. Ensure that the Lambda function is correctly evaluating the Do Not Call status and returning the expected results.