Setting up chat and messaging channels in Amazon Connect
Amazon Connect
Verified 2026-10-01 · 73 sources · tier 2
For Amazon Connect administrators with a working instance, agents, queues and flows who are adding chat, and optionally SMS and Apple Messages for Business.
Chat is enabled at the Amazon Connect instance level when an Amazon S3 bucket for chat transcripts is configured, and Apple Messages for Business contacts use the same configuration, routing and agent workspace as chat 12 5. SMS is added by procuring an SMS-enabled number in AWS End User Messaging SMS, enabling two-way SMS on it and importing it into Amazon Connect, and persistent chat lets a returning customer resume a previous conversation with its transcript carried forward 40 18.
Before you start
- AWS documentation states that the legacy Amazon Connect contact centre product is now called Amazon Connect Customer 64.
- An instance includes a default routing profile named Basic routing profile and a default standard queue named BasicQueue 65.
- By default, instance creation creates Amazon S3 buckets for call recordings, chat transcripts, exported reports, flow logs and email messages, with data encrypted using AWS KMS 66.
- Apple Messages for Business, SMS, WhatsApp Business Messaging and push notifications integrations are not available in AWS GovCloud (US-West) 67.
- If you plan SMS, some countries require number registration that can take up to 15 business days, and the number cannot send messages until registration is approved 34.
See also Setting up an Amazon Connect instance.
See also Setting up queues and routing profiles in Amazon Connect.
See also Amazon Connect contact flows and routing profiles.
See also Amazon Lex bots in Amazon Connect.
See also Troubleshooting business SMS that is not delivered.
What changes by situation
Pick your answers to see only your path. Nothing is sent anywhere until you make a plan.
Four questions. One permanent page you can send to your manager.
Step 1 Configure the chat transcript bucket
Do
In the Amazon Connect console, open the instance's Data storage page, choose Chat transcripts, then Edit, and set the chat transcript bucket and KMS key 52. Configuring this bucket is what enables chat at the instance level 12. Use a single transcript bucket and keep the transcript file names Amazon Connect generates, because persistent chat fails to retrieve past transcripts if the instance uses multiple chat transcript buckets or the file names are changed 22. If you need up to 6 participants on a chat or want supervisors to barge chats, turn on the instance option Enable Multi-Party Chats and Enhanced Monitoring for Chat 16.
Verify
Suggested check: reopen the data storage page and confirm a bucket is listed for chat transcripts. The admin website's Channels, Test chat page simulates a customer web page beside the agent CCP 47.
Step 2 Build the chat inbound flow and a disconnect flow
Do
In the inbound flow for chat, add a Set disconnect flow block that names the flow to run when the agent or Lex bot has left the chat and only the customer remains 10. In that disconnect flow, add a Wait block, which branches on timeout or on customer return 10. A chat lasts at most 25 hours by default 7. AWS advises setting the Wait block time well below the chat duration, because a customer who resumes near the duration limit can be cut off when the chat ends 53. If the flow uses Amazon Lex, the default Lex session timeout is 5 minutes and a Lex session cannot exceed 24 hours 15. In the flow designer, Save stores a draft and Publish activates the flow immediately, and every connector must be attached to a block before a flow can be published 68.
Verify
On the Channels, Test chat page, choose this flow under Test Settings, since the page otherwise runs the Sample inbound flow 47. Suggested check: have the agent leave the test chat, send another message as the customer, and confirm the customer-return branch of the Wait block runs.
Rollback
The flow designer exposes previously published versions through a Latest: Published dropdown, and you roll back by opening a previous version and choosing Publish 69.
Step 3 Add chat to queues and routing profiles and set concurrency
Do
Open the routing profile in the admin website under Users, Routing profiles 70. Enable the chat channel and set Maximum contacts per agent for chat, which can be set up to 10 simultaneous chats 27. Set cross-channel concurrency for chat to either No other channels or Allow other channels concurrently 28. Add each chat queue with the Chat channel, and make sure chat is also enabled in the profile's Channel Settings, otherwise chat contacts are not routed to the profile's agents 26. Each agent is assigned exactly one routing profile, so the change applies to every agent on that profile 29.
Verify
The Channels, Test chat environment uses BasicQueue and the Basic Routing Profile, which is set up for 2 concurrent chats 46. Suggested check: open several test chats at once and confirm an agent on the edited profile is offered up to the configured number.
Rollback
Removing a channel from Channel availability on a routing profile stops that channel's contacts to the profile's agents across every queue in the profile, and re-selecting it restores them 71.
Step 4 Set idle and auto-disconnect timeouts
Do
Use the UpdateParticipantRoleConfig action to set any of the customer idle, customer auto-disconnect, agent idle and agent auto-disconnect timers, each in minutes from 2 to 480 51. AWS recommends calling UpdateParticipantRoleConfig from a Lambda function in the flow, placed at the start of the flow or just before the contact is routed to a queue 50. On an auto-disconnect, every participant other than the customer is disconnected, and the chat is routed to the disconnect flow named in the Set disconnect flow block 49.
Verify
A timer configuration changed while an agent and customer are already connected is stored but applies only when a new agent or custom participant joins the chat 48. Suggested check: start a fresh test chat, leave it idle past the configured timer, and confirm the idle or disconnect behaviour occurs.
Rollback
Suggested rollback: remove the timer call from the flow and publish the flow again. Chats already connected keep their stored timer configuration until a new agent or custom participant joins 48.
Step 5 Build the customer entry point
The communications widget hosted by Amazon Connect, embedded with a snippet
Do
In the admin website, go to Customize communications widget, Add communications widget, and give the widget a name that is unique within the instance 55. To offer a pre-chat form, first create a view with a connect action button that selects the StartChatContact action 63. Add your website domains, up to 50 per widget, because the widget loads only on allowlisted domains 57. Subdomains and all URL paths of an allowed domain are allowed automatically, but the http:// or https:// protocol must match the configured entry exactly 56. Choosing Yes for widget security makes Amazon Connect issue a 44-character security key and add an authenticate callback that your website must implement to supply a JWT for each new chat 60. Sign those JWTs with HS256, put the widget ID in the sub claim, and set an expiration of at most 10 minutes 61. Embed the widget's snippet on your site; Amazon Connect hosts the widget, so the latest version is always live on a site that embeds it 59.
Verify
Test from Chrome 85.0, Safari 13.1, Edge 85 or Firefox 81.0 or later, which the widget supports 54. Suggested check: start a chat from an allowlisted page, then load a page from a domain that is not allowlisted and confirm the widget does not appear. Saved widget changes reach customers within a few minutes, but icon changes produce a new code snippet that must be placed on the website 58.
Rollback
Remove the domain from the allowlist, since the widget loads only on allowlisted domains 57. If you rotate an exposed security key, Amazon Connect issues a new key and keeps the previous key valid until you delete it 62.
Your own web or mobile chat UI that calls StartChatContact
Do
Build a backend that calls StartChatContact with InstanceId, ContactFlowId set to the chat inbound flow, and ParticipantDetails, which the API requires 44. AWS's open source chat example links to a CloudFormation template that creates an Amazon API Gateway endpoint invoking a Lambda function, which an app calls to start a chat 9. The client must call CreateParticipantConnection with WEBSOCKET and CONNECTION_CREDENTIALS within 5 minutes of the chat being created 42. Always include text/plain in SupportedMessagingContentTypes, and include the interactive message type if the flow uses the Show view block 43. To change the default 25-hour chat length, set ChatDurationInMinutes from 60 to 10,080 minutes 7. A 400 error on ChatDurationInMinutes may mean the account does not support custom chat durations, which AWS says to raise with Support 11.
Verify
Suggested check: call the backend, confirm the client connects, and confirm the chat reaches an agent. A chat started through the API has initiation method API and is not counted in Contacts Incoming until it is transferred to an agent 6.
Rollback
Suggested rollback: disable the start-chat call in the client or take the backend endpoint offline.
Step 6 Decide how chats continue across sessions
Yes, rehydrate past transcripts into new chats + The communications widget hosted by Amazon Connect, embedded with a snippet
Do
Amazon Connect does not supply the previous contact ID automatically, and AWS recommends keeping a repository of contact IDs per customer, filled from chat message streaming or from contact events through Lambda 23. Enable persistent chat with the Create persistent contact association flow block, and do not also pass the same source contact as SourceContactId in StartChatContact 19. Choose a rehydration type: ENTIRE_PAST_SESSION rehydrates all segments of past sessions, and FROM_SEGMENT rehydrates from a specified past segment 25. For ENTIRE_PAST_SESSION, the source contact ID must be the first contact ID of the past chat session 13. Only ended chats can be rehydrated, and AWS says to wait 30-60 seconds after a chat ends before rehydrating from it 20.
Verify
Suggested check: end a test chat, wait at least a minute, and start a new chat as the same customer. For a persistent chat, the earlier contact ID appears as RelatedContactId in the new contact record 8. Agents see the whole history because context, metadata and transcript are carried forward 18.
Rollback
Suggested rollback: remove the association block from the flow and publish it, so new chats start without history.
Yes, rehydrate past transcripts into new chats + Your own web or mobile chat UI that calls StartChatContact
Do
Amazon Connect does not supply the previous contact ID automatically, and AWS recommends keeping a repository of contact IDs per customer, filled from chat message streaming or from contact events through Lambda 23. Enable persistent chat either by passing the previous contact ID as SourceContactId in StartChatContact or by using the Create persistent contact association flow block, but not both for the same source contact 19. Do not send RelatedContactId in a StartChatContact request that also provides PersistentChat 21. Choose a rehydration type: ENTIRE_PAST_SESSION rehydrates all segments of past sessions, and FROM_SEGMENT rehydrates from a specified past segment 25. For ENTIRE_PAST_SESSION, SourceContactId must be the first contact ID of the past chat session 13. Only ended chats can be rehydrated, and AWS says to wait 30-60 seconds after a chat ends before rehydrating from it 20. Show the past transcript in your client by calling GetTranscript with the returned NextToken and ScanDirection set to BACKWARD 17.
Verify
Suggested check: end a test chat, wait at least a minute, and start a new chat as the same customer. The StartChatContact response returns ContinuedFromContactId, and the same contact ID appears as RelatedContactId in the new contact record 8. Agents see the whole history because context, metadata and transcript are carried forward 18.
Rollback
Suggested rollback: stop sending a source contact ID from the backend, so new chats start without history.
No, each chat is a new conversation
Do
Size the Wait block time in the disconnect flow well below the chat duration, as AWS advises, so a customer who steps away within one chat is not cut off 53. An idle chat whose customer has gone silent still counts against the concurrent active chats quota, and AWS recommends persistent chat to avoid this 14.
Verify
The disconnect flow's Wait block branches on customer return or timeout 10. Suggested check: return as the customer within the Wait time and confirm the same chat resumes, then return after the chat ends and confirm a new chat starts with no earlier transcript.
Step 7 Add the SMS channel
No SMS channel
Do
Leave your numbers unchanged, since SMS for Amazon Connect is only set up by procuring an SMS-enabled number in AWS End User Messaging SMS, enabling two-way SMS on it and importing it 40.
Verify
Suggested check: confirm no number attached to the instance is configured for two-way text messaging.
Add SMS through AWS End User Messaging SMS
Do
Start registration early, because some countries require it, approval can take up to 15 business days, the number cannot send until approved, and its monthly lease is billed regardless 34. In AWS End User Messaging SMS, request a number with the SMS capability, which cannot be changed after the number is purchased 31. Use a number separate from your voice numbers, because one number for both voice and SMS is not supported 32. On the number's Two-way SMS tab, enable two-way SMS with destination type Amazon Connect and an existing IAM role, then import the number into your instance 39. In the admin website, go to Channels, Phone numbers, Edit, and attach the chat inbound flow under Flow/IVR 30. Only published flows appear in the Flow / IVR list 72. To give SMS contacts their own path, add a Check contact attributes block testing Segment attributes key Subtype equal to connect:SMS 38. Before production, move out of the SMS/MMS sandbox, complete registration, confirm the spend quota and check opt-out lists 33. Enable self-managed opt-out only if you will answer HELP and STOP and track and honour opt-outs yourself 36.
Verify
The number is usable only when its status changes from Pending to Active 30. While the number is in the SMS sandbox, it can only exchange test messages with verified destination numbers 35. Do not test with STOP or HELP, because AWS End User Messaging SMS answers those keywords itself without forwarding them to Amazon Connect, and STOP adds the sender to the opt-out list 37. Suggested check: set a test agent to Available, text the number from a verified mobile phone, and confirm the message reaches the agent.
Rollback
Suggested rollback: detach the number from the flow, or turn off two-way messaging on the number.
Step 8 Add Apple Messages for Business
No Apple Messages for Business
Do
Do not start registration, since Apple Messages for Business setup begins by registering the business with Apple and selecting Amazon Connect as the Messaging Service Provider 4.
Verify
Suggested check: confirm no business messaging account has been linked to the instance through a support ticket.
Add Apple Messages for Business
Do
Register the business with Apple and select Amazon Connect as the Messaging Service Provider, which yields an Apple Messages for Business Account ID once approved 4. Next, open an AWS Support ticket giving the Apple account ID, Apple token, instance ARN and the chat inbound flow ID, with Apple's readiness and use-case forms attached 3. Design the conversation so a live agent is reachable whenever the customer texts help, and so an automated agent that cannot understand a request hands over to a live agent, as AWS's experience-review guidance requires 2. Finally, record the customer-side experience and submit it by Support ticket for review by Amazon Connect and Apple 1.
Verify
Apple Messages for Business contacts use the same configuration, analytics, routing and agent workspace as chat 5. Final approval comes after the experience review recording is submitted 1. Suggested check: send a test message from a customer device and confirm it lands in the expected chat queue.
Step 9 Check chat capacity quotas and API rates
Do
Compare expected peak chats with the Concurrent active chats per instance quota, which defaults to 500, is adjustable, and counts SMS, WhatsApp and Apple Messages for Business chats as well as waiting chats 24. Idle chats whose customer has gone silent still count against that quota 14. StartChatContact and CreatePersistentContactAssociation each default to 5 requests per second with a burst of 8, shared per account and Region 45.
Verify
Suggested check: look up the quota value applied to your account and compare it with the documented default. StartChatContact returns HTTP 429 as TooManyRequests when the rate limit is exceeded and as LimitExceededException when the concurrent active chats quota is exceeded 41.
Step 10 Test end to end before go-live
Do
On Channels, Test chat, choose the production chat flow under Test Settings and run a conversation 47. The test environment's Basic Routing Profile is set up for 2 concurrent chats, so a second chat exercises concurrency 46.
Verify
Agents have 20 seconds to accept a chat contact, after which their status becomes Missed and the contact routes to the next available agent 73. Suggested check: repeat the test through the real customer entry point and every messaging channel you enabled, and confirm each chat reaches the expected queue and agent. Suggested check: confirm the configured timeouts fire and the disconnect flow handles a returning customer. For a persistent chat, the earlier contact ID appears as RelatedContactId in the new contact record 8.
Applicability
Apple Messages for Business, SMS, WhatsApp Business Messaging and push notifications integrations are not available in AWS GovCloud (US-West) 67. Applies to: Amazon Web Services Amazon Connect, Amazon Web Services Amazon Lex, Amazon Web Services AWS End User Messaging SMS, Amazon Web Services Amazon Connect Customer, and AWS Amazon Connect. Deployments: multi-tenant. Sources checked 2026-10-01.
What remains uncertain
Which AWS Regions other than AWS GovCloud (US-West) support two-way SMS and Apple Messages for Business is not covered by the sources below. How to turn chat off at the instance level once a transcript bucket is configured is not covered by the sources below. How to unlink an Apple Messages for Business account from an instance is not covered by the sources below. Whether the hosted communications widget can pass a persistent-chat source contact ID directly is not covered by the sources below. Apple's own eligibility criteria for business registration are not covered by the sources below. WhatsApp Business messaging setup, email, tasks, chat attachments, post-chat surveys, Customer Profiles, Lex bot design, mobile chat SDKs and pricing are not covered by the sources below.
See also
Depends on
- Setting up an Amazon Connect instance — Chat is enabled on an existing instance via its chat transcript bucket.
Related to
- Amazon Connect contact flows and routing profiles — Chat inbound and disconnect flows; Set disconnect flow; Wait and Create persistent contact association blocks.
- Setting up queues and routing profiles in Amazon Connectstub — Chat channel; concurrency and cross-channel settings live in routing profiles.
Referenced by
- Troubleshooting business SMS that is not delivered — Amazon Connect SMS uses AWS End User Messaging SMS origination identities; registration statuses and event types documented here apply to the underlying numbers.
Sources
- 1Before final approval, the business records the customer-side Apple Messages for Business experience and submits it by Support ticket for review by Amazon Connect and Apple.Enable Apple Messages for Business with Connect Customer · Step 4: Create and Submit Experience Review Recording · Checked 2026-10-01
- 2AWS's experience-review guidance says a live agent must be reachable whenever the customer texts help, and an automated agent that cannot understand a request must hand over to a live agent.Enable Apple Messages for Business with Connect Customer · Step 4, Tips for developing the user experience, 'Allow switching from an automated to a live agent' · Checked 2026-10-01
- 3The Apple Messages for Business account is linked to Amazon Connect through an AWS Support ticket giving the Apple account ID, Apple token, instance ARN and inbound flow ID, with Apple's readiness and use-case forms attached.Enable Apple Messages for Business with Connect Customer · Step 2: Gather required information and Step 3: Link your Apple Messages for Business ID · Checked 2026-10-01
- 4Apple Messages for Business setup starts by registering the business with Apple and selecting Amazon Connect as the Messaging Service Provider, which yields an Apple Messages for Business Account ID once approved.Enable Apple Messages for Business with Connect Customer · Step 1: Register with Apple, and Step 2 item 1 · Checked 2026-10-01
- 5Apple Messages for Business contacts in Amazon Connect use the same configuration, analytics, routing and agent workspace as Amazon Connect chat.Enable Apple Messages for Business with Connect Customer · introduction, third paragraph · Checked 2026-10-01
- 6A chat started through the API has initiation method API and is not counted in the Contacts Incoming metric until it is transferred to an agent.Start chats in your applications by using Connect Customer APIs · second and final paragraphs · Checked 2026-10-01
- 7A chat lasts at most 25 hours by default, and the StartChatContact ChatDurationInMinutes parameter can set it from 60 to 10,080 minutes (7 days).The chat/SMS channel in Connect Customer · When do chats end?, first paragraph · Checked 2026-10-01
- 8For a persistent chat, the StartChatContact response returns ContinuedFromContactId, and the same contact ID appears as RelatedContactId in the new contact record.Enable customers to resume chat conversations in Connect Customer · Example use cases, Note on cumulative chat linkages · Checked 2026-10-01
- 9AWS's open source chat example links to a CloudFormation template that creates an Amazon API Gateway endpoint invoking a Lambda function, which an app calls to start a chat and pass the response to the chat widget.Customize chat with the Connect Customer open source example · bulleted list 'Here's how it works' · Checked 2026-10-01
- 10A Set disconnect flow block in the inbound flow names the flow that runs when the agent or Lex bot has left a chat and only the customer remains, and a Wait block in that flow branches on timeout or customer return.The chat/SMS channel in Connect Customer · Example chat scenario, steps 1-3 · Checked 2026-10-01
- 11A 400 error when using ChatDurationInMinutes may mean the AWS account does not support custom chat durations, which AWS says to raise with Support.StartChatContact - Amazon Connect API Reference · API description, paragraph beginning 'If you use the ChatDurationInMinutes parameter' · Checked 2026-10-01
- 12Chat is enabled at the Amazon Connect instance level when an Amazon S3 bucket for storing chat transcripts is configured.The chat/SMS channel in Connect Customer · Getting started, first bullet · Checked 2026-10-01
- 13For the ENTIRE_PAST_SESSION rehydration type, SourceContactId must be the first contact ID of the past chat session.Enable customers to resume chat conversations in Connect Customer · Example use cases, Use case 2, Note · Checked 2026-10-01
- 14An idle chat whose customer has gone silent still counts against the concurrent active chats quota, and AWS recommends persistent chat to avoid this.Connect Customer service quotas · Connect Customer quotas table, Concurrent active chats per instance, second paragraph · Checked 2026-10-01
- 15When Amazon Lex is used with chat, the default Lex session timeout is 5 minutes and a Lex session cannot exceed 24 hours.The chat/SMS channel in Connect Customer · When do chats end?, Tip · Checked 2026-10-01
- 16The instance option Enable Multi-Party Chats and Enhanced Monitoring for Chat allows up to six participants on a chat and lets supervisors barge chats.Update settings for your Connect Customer instance · Update telephony and chat options, item 6 · Checked 2026-10-01
- 17A custom chat client reads the rehydrated past transcript by calling GetTranscript with the returned NextToken and ScanDirection set to BACKWARD.Enable customers to resume chat conversations in Connect Customer · How to access past chat contact transcript for a persistent chat · Checked 2026-10-01
- 18Persistent chat lets a returning customer resume a previous conversation with its context, metadata and transcript carried forward, so agents see the whole history.Enable customers to resume chat conversations in Connect Customer · introduction, second paragraph · Checked 2026-10-01
- 19Persistent chat is enabled either by passing a previous contact ID as SourceContactId in StartChatContact or by using the Create persistent contact association flow block, but not both for the same source contact.Enable customers to resume chat conversations in Connect Customer · How to enable persistent chat, list and Note · Checked 2026-10-01
- 20Only chat sessions that have ended can be rehydrated into a new chat, and AWS says to wait 30-60 seconds after a chat ends before rehydrating from it.Enable customers to resume chat conversations in Connect Customer · Chat rehydration, Important box · Checked 2026-10-01
- 22Persistent chat fails to retrieve past transcripts if the instance uses multiple chat transcript buckets or if the transcript file names generated by Amazon Connect are changed.Enable customers to resume chat conversations in Connect Customer · How to enable persistent chat, final paragraph and list · Checked 2026-10-01
- 23Amazon Connect does not supply the previous contact ID automatically, and AWS recommends keeping a repository of contact IDs per customer, filled from chat message streaming or from contact events through Lambda.Enable customers to resume chat conversations in Connect Customer · How to enable persistent chat, paragraphs after the Note · Checked 2026-10-01
- 24The default Concurrent active chats per instance quota is 500, is adjustable, and counts SMS, WhatsApp and Apple Messages for Business chats as well as chats that are waiting.Connect Customer service quotas · Connect Customer quotas table, Concurrent active chats per instance · Checked 2026-10-01
- 25Persistent chat supports two rehydration types: ENTIRE_PAST_SESSION, which rehydrates all segments of past sessions, and FROM_SEGMENT, which rehydrates from a specified past segment.Enable customers to resume chat conversations in Connect Customer · Chat rehydration, list of rehydration types · Checked 2026-10-01
- 26A queue's channel in a routing profile must also be enabled in the profile's Channel Settings, otherwise contacts from that channel are not routed to its agents.Create a routing profile in Connect Customer to link queues to agents · To create a routing profile, Queues table, Channels row · Checked 2026-10-01
- 27In a routing profile, Maximum contacts per agent for the chat channel can be set up to 10 simultaneous chats.Create a routing profile in Connect Customer to link queues to agents · To create a routing profile, Channel Settings table, Maximum contacts per agent · Checked 2026-10-01
- 28Cross-channel concurrency per channel is either No other channels while the agent is on that channel or Allow other channels concurrently.Create a routing profile in Connect Customer to link queues to agents · To create a routing profile, Channel Settings table, Cross-channel concurrency · Checked 2026-10-01
- 29Each Amazon Connect agent is assigned exactly one routing profile.Create a routing profile in Connect Customer to link queues to agents · introduction, 'Each agent is assigned to one routing profile.' · Checked 2026-10-01
- 30An imported SMS number is attached to a flow in the admin website under Channels, Phone numbers, Edit, Flow/IVR, and it becomes usable only when its status changes from Pending to Active.Set up SMS messaging in Connect Customer · Step 3, items 4-5 and Tip · Checked 2026-10-01
- 31The SMS or Voice capability chosen when requesting a number in AWS End User Messaging SMS cannot be changed after the number is purchased.Set up SMS messaging in Connect Customer · Step 1: Request a number, item 4, Important box · Checked 2026-10-01
- 33Before production SMS, AWS lists four prerequisites: move out of the SMS/MMS sandbox, complete registration, confirm the spend quota, and check opt-out lists.Set up SMS messaging in Connect Customer · Step 5: Prerequisites for going into production · Checked 2026-10-01
- 34Some countries require SMS number registration that can take up to 15 business days, the number cannot send messages until registration is approved, and its monthly lease is billed regardless.Set up SMS messaging in Connect Customer · Step 1: Request a number, opening Important box and item 9 Important box · Checked 2026-10-01
- 35While an SMS number is in the SMS sandbox, it can only exchange test messages with verified destination numbers.Set up SMS messaging in Connect Customer · Step 4, item 2 Tip · Checked 2026-10-01
- 36If self-managed opt-out is enabled on an SMS number, the business becomes responsible for answering HELP and STOP and for tracking and honouring opt-outs.Set up SMS messaging in Connect Customer · Step 6: (Optional) Set up self-managed opt-out, Important box · Checked 2026-10-01
- 37By default AWS End User Messaging SMS answers reserved keywords such as STOP and HELP itself and does not forward them to Amazon Connect, and STOP adds the sender to the opt-out list.Set up SMS messaging in Connect Customer · Step 4: Test sending and receiving SMS messages, Important box · Checked 2026-10-01
- 38A flow can branch SMS contacts with a Check contact attributes block testing Segment attributes key Subtype equal to connect:SMS.Set up SMS messaging in Connect Customer · Step 3: Update flows to branch on SMS contacts, items 1-3 · Checked 2026-10-01
- 39Two-way SMS is enabled on the number's Two-way SMS tab in the AWS SMS console with destination type Amazon Connect and an existing IAM role, after which the number is imported into the chosen Connect instance.Set up SMS messaging in Connect Customer · Step 2: Enable two-way SMS on the phone number, items 4-10 · Checked 2026-10-01
- 40SMS for Amazon Connect is set up by procuring an SMS-enabled number in AWS End User Messaging SMS, enabling two-way SMS on it, and importing it into Amazon Connect.Set up SMS messaging in Connect Customer · introduction, second paragraph · Checked 2026-10-01
- 41StartChatContact returns HTTP 429 either as TooManyRequests when the API rate limit is exceeded or as LimitExceededException when the concurrent active chats quota is exceeded.StartChatContact - Amazon Connect API Reference · API description, 'A 429 error occurs in the following situations' · Checked 2026-10-01
- 42After StartChatContact creates a chat, the client must subscribe to the participant connection within 5 minutes by calling CreateParticipantConnection with WEBSOCKET and CONNECTION_CREDENTIALS.StartChatContact - Amazon Connect API Reference · API description, second paragraph · Checked 2026-10-01
- 43SupportedMessagingContentTypes must always include text/plain, and the interactive message type is required to use the Show view flow block.StartChatContact - Amazon Connect API Reference · Request Body: SupportedMessagingContentTypes · Checked 2026-10-01
- 44The StartChatContact API requires InstanceId, ContactFlowId and ParticipantDetails, and it starts the named flow for the new chat.StartChatContact - Amazon Connect API Reference · Request Body: ContactFlowId, InstanceId, ParticipantDetails ('Required: Yes') · Checked 2026-10-01
- 45StartChatContact and CreatePersistentContactAssociation each have a default rate limit of 5 requests per second and a burst limit of 8, shared per account and Region.Connect Customer service quotas · API throttling quotas, Connect Customer API throttling quotas table · Checked 2026-10-01
- 46The test chat environment uses BasicQueue and the Basic Routing Profile, which is set up for 2 concurrent chats.Test voice, chat, and task experiences in Connect Customer · Test chat, item 7 Tip · Checked 2026-10-01
- 47The admin website's Channels, Test chat page simulates a customer web page beside the agent CCP and runs the Sample inbound flow unless another flow is chosen under Test Settings.Test voice, chat, and task experiences in Connect Customer · Test chat, items 1-4 · Checked 2026-10-01
- 48A timer configuration changed while an agent and customer are already connected is stored but only applies when a new agent or custom participant joins the chat.Set up chat timeouts for chat participants · How chat timers work, seventh bullet · Checked 2026-10-01
- 49On an auto-disconnect, every participant other than the customer is disconnected, and if a Set disconnect flow block was configured the chat is routed to that disconnect flow.Set up chat timeouts for chat participants · How chat timers work, final bullet · Checked 2026-10-01
- 50AWS recommends calling UpdateParticipantRoleConfig from a Lambda function in the flow, placed at the start of the flow or just before the contact is routed to a queue.Set up chat timeouts for chat participants · Recommended usage · Checked 2026-10-01
- 51Chat timeouts offer customer idle, customer auto-disconnect, agent idle and agent auto-disconnect timers, each set in minutes from 2 to 480 through the UpdateParticipantRoleConfig action.Set up chat timeouts for chat participants · introduction, timer table and 'Specify all timers in minutes' list · Checked 2026-10-01
- 52The chat transcript bucket and KMS key are set in the Amazon Connect console under the instance's Data storage page, Chat transcripts, Edit.Update settings for your Connect Customer instance · Update data storage, Chat transcripts bullet · Checked 2026-10-01
- 53AWS advises setting the Wait block time well below the chat duration, because a customer who resumes near the duration limit can be cut off when the chat ends.The chat/SMS channel in Connect Customer · When do chats end?, third paragraph · Checked 2026-10-01
- 54The pre-built communications widget supports Chrome 85.0, Safari 13.1, Edge 85 and Firefox 81.0 and later.Add a chat user interface to your website hosted by Connect Customer · Supported browsers · Checked 2026-10-01
- 55A communications widget is created in the Amazon Connect admin website under Customize communications widget, Add communications widget, and its name must be unique within the instance.Add a chat user interface to your website hosted by Connect Customer · Step 1: Customize your communications widget, items 1-3 · Checked 2026-10-01
- 56In the widget domain allowlist, subdomains and all URL paths of an allowed domain are automatically allowed, but the http:// or https:// protocol must match the configured entry exactly.Add a chat user interface to your website hosted by Connect Customer · Step 2: Specify the website domains, 'Domain allowlist behavior' list · Checked 2026-10-01
- 57The communications widget loads only on allowlisted website domains, and up to 50 domains can be added per widget.Add a chat user interface to your website hosted by Connect Customer · Step 2: Specify the website domains, item 1 · Checked 2026-10-01
- 58Saved widget configuration changes reach customers within a few minutes, but changes to widget icons produce a new code snippet that must be placed on the website.Add a chat user interface to your website hosted by Connect Customer · Step 3, Communications widget script, Note and following paragraph · Checked 2026-10-01
- 59Amazon Connect hosts the communications widget, so the latest widget version is always live on the website that embeds its snippet.Add a chat user interface to your website hosted by Connect Customer · introduction, paragraph beginning 'Because Connect Customer hosts the widget' · Checked 2026-10-01
- 60Choosing Yes for widget security makes Amazon Connect issue a 44-character security key and add an authenticate callback to the embed script that the website must implement to supply a JWT for each new chat.Add a chat user interface to your website hosted by Connect Customer · Step 2: Specify the website domains, item 2 (Add security for your communications widget) · Checked 2026-10-01
- 61Widget JWTs are signed with HS256, carry the widget ID in the sub claim, and have an expiration of at most 10 minutes.Add a chat user interface to your website hosted by Connect Customer · Step 3, Security key, 'JSON Web Token specifics' · Checked 2026-10-01
- 62When the widget security key is rotated, Amazon Connect issues a new key and keeps the previous key valid until the administrator deletes it.Add a chat user interface to your website hosted by Connect Customer · Step 3, Security key, first paragraph · Checked 2026-10-01
- 63Enabling a pre-chat form on the communications widget first requires a view with a connect action button that selects the StartChatContact action.Add a chat user interface to your website hosted by Connect Customer · Step 1: Customize your communications widget, item 4 (Communications options) · Checked 2026-10-01
- 64AWS documentation states that the legacy Amazon Connect contact centre product is now called Amazon Connect Customer, and that Amazon Connect now refers to a portfolio of agentic solutions for business functions.What is Connect Customer? · Note callout immediately under the heading What is Connect Customer? · Checked 2026-09-07
- 65An Amazon Connect instance includes a default routing profile named Basic routing profile and a default standard queue named BasicQueue.How Connect Customer uses routing profiles · Default routing profile: Basic routing profile · Checked 2026-10-01
- 66By default instance creation creates Amazon S3 buckets for call recordings, chat transcripts, exported reports, flow logs and email messages, with data encrypted using AWS KMS.Create a Connect Customer instance · Step 4: Data storage, first paragraphs and bold note 'By default, Connect Customer creates buckets' · Checked 2026-09-30
- 67Apple Messages for Business, SMS, WhatsApp Business Messaging and push notifications integrations are not available in AWS GovCloud (US-West).Availability of Connect Customer features by Region · Messaging integrations table, AWS GovCloud (US-West) row · Checked 2026-09-30
- 68In the flow designer, Save stores a draft of the flow and Publish activates it immediately, and every connector must be attached to a block before a flow can be published.Use the flow designer in Connect Customer to create flows · Section Create an inbound flow, final numbered step and the following Note · Checked 2026-09-07
- 69The flow designer exposes previously published versions of a flow through a Latest: Published dropdown, and a rollback is performed by opening a previous version and choosing Publish.Flow version control: Roll back a flow · Sections View a previous version of a flow and Roll back a flow · Checked 2026-09-07
- 71Removing a channel such as Voice from Channel availability on a routing profile stops that channel's contacts to the profile's agents across every queue in the profile, and re-selecting it restores them.Create a routing profile in Connect Customer to link queues to agents · Tips for setting up channels and concurrency, first bullet · Checked 2026-10-01
- 72A claimed or ported number is attached to a flow under Channels, Phone numbers, choosing the number and selecting the flow in Flow / IVR, and only published flows appear in that list.Attach a claimed or ported phone number to a flow in Connect Customer · To associate a claimed or ported phone number with a published flow, items 1-4 · Checked 2026-09-30
- 73Agents have 20 seconds to accept a voice or chat contact (30 seconds for a task), after which their status becomes Missed and the contact routes to the next available agent; this window is not configurable.Configure agent settings in Connect Customer · Note above 'To configure agent settings' · Checked 2026-09-30
Documents
Add a chat user interface to your website hosted by Connect Customer
Attach a claimed or ported phone number to a flow in Connect Customer
Availability of Connect Customer features by Region
Configure agent settings in Connect Customer
Connect Customer service quotas
Create a Connect Customer instance
Create a routing profile in Connect Customer to link queues to agents
Customize chat with the Connect Customer open source example
Enable Apple Messages for Business with Connect Customer
Enable customers to resume chat conversations in Connect Customer
Flow version control: Roll back a flow
How Connect Customer uses routing profiles
Set up chat timeouts for chat participants
Set up SMS messaging in Connect Customer
Start chats in your applications by using Connect Customer APIs
StartChatContact - Amazon Connect API Reference
Test voice, chat, and task experiences in Connect Customer
The chat/SMS channel in Connect Customer
Update settings for your Connect Customer instance
Use the flow designer in Connect Customer to create flows
What is Connect Customer?
Cite this page
APA
WarmTransfer. (2026, October 1). Setting up chat and messaging channels in Amazon Connect. WarmTransfer. https://warmtransfer.net/guides/amazon-connect-chat-setup
BibTeX
@misc{warmtransfer-amazon-connect-chat-setup,
title = {Setting up chat and messaging channels in Amazon Connect},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/guides/amazon-connect-chat-setup},
note = {Verified 2026-10-01}
}