- Newest
- Most votes
- Most comments
For outbound calls initiated from Amazon Connect Campaigns, contact attributes are typically set only after the call is established. This differs from single outbound calls where you can pass attributes in the initial request.
Currently, there isn't a direct way to pass dynamic attributes to an AWS Connect Campaign before dialing for each contact in the campaign list. For outbound calls, contact attributes are usually populated once the call transitions to the "Connected" state, which explains the latency you're experiencing.
To address your latency issue, you have a few potential workarounds:
-
Pre-store customer data in a more quickly accessible location (like DynamoDB) to reduce Lambda lookup time.
-
Use the caller ID number dynamically in your flow to help identify the customer. You can set the outbound caller ID number using an attribute in the Call phone number block. This attribute can be defined in a Set contact attributes block or returned from a Lambda function. The value must be a phone number from your instance in E.164 format.
-
For the dialed number identification, you can use the System attribute "Channel.Address" in your contact flow to identify which number was dialed, and then use a Check contact attributes block to route based on this information.
-
Consider implementing a caching mechanism in your Lambda function to speed up data retrieval.
The fundamental limitation is that for campaign-based outbound calls, the attributes are only available after connection, unlike single outbound calls where you can pass attributes in the initial API call. This behavior difference between campaign calls and single outbound calls is a known characteristic of Amazon Connect's architecture.
Sources
Contact Attributes not loading before call gets connected for outbound calling | AWS re:Post
Set up outbound caller ID in Amazon Connect - Amazon Connect
Question related to amazon connect flow | AWS re:Post
answered a year ago
Relevant content
asked a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 4 years ago
