- Newest
- Most votes
- Most comments
Thank you for your questions about using StartOutboundVoiceContact API with Amazon Connect and integrating it with SNS. I'll address each of your questions:
- Regarding using an SNS topic to get phone numbers for outbound calls:
Unfortunately, there isn't a direct way to extract phone numbers from SNS topic subscriptions to use with StartOutboundVoiceContact. SNS topics are primarily designed for sending notifications, not for storing contact information for outbound calls.
If you need to manage a list of phone numbers for outbound calls, you might consider using a different AWS service like Amazon DynamoDB to store the phone numbers. You could then use a Lambda function to retrieve these numbers and initiate calls using StartOutboundVoiceContact.
- Regarding making simultaneous calls with StartOutboundVoiceContact:
The StartOutboundVoiceContact API is designed to initiate a single outbound call at a time. There isn't a built-in option to make multiple simultaneous calls with a single API call.
To make multiple calls, you would indeed need to implement a loop in your Lambda function. Using AWS Step Functions could be a good approach for managing this process, especially if you need to handle a large number of calls or implement complex workflows.
Here's a high-level approach you could consider:
- Store your list of phone numbers in a database or queue.
- Use a Lambda function to retrieve phone numbers and call StartOutboundVoiceContact for each number.
- Implement this Lambda function as part of a Step Functions workflow to manage the process, handle retries, and control the rate of outbound calls.
Remember to consider any applicable service quotas and implement appropriate error handling and rate limiting in your solution to ensure compliance with Amazon Connect's limits and best practices for outbound calling.
Sources
StartOutboundVoiceContact - Amazon Connect
Integrate AWS Lambda in a Step Functions state machine with Amazon SQS and Amazon SNS - AWS Step Functions
answered 2 years ago
Relevant content
- AWS OFFICIALUpdated 4 months ago

Since you mention it, what could be the problem with AWS Connect quotas? It happens that calls could be triggered for different processes at the same time, and calls would have to be generated to several phone numbers per process. I imagine that when using a Lambda function with a Step Functions the calls have a small delay, but what would be the real impact on quotas?