AWS connect documentation change
Summary
Terminology update from 'click-to-call' to 'choose-to-call'
Security assessment
Change reflects branding/terminology update without modifying security functionality. The caller context passing mechanism remains unchanged with no security implications.
Diff
diff --git a/connect/latest/adminguide/touchtone-buffering.md b/connect/latest/adminguide/touchtone-buffering.md index fa02bfbf2..04d75e16e 100644 --- a//connect/latest/adminguide/touchtone-buffering.md +++ b//connect/latest/adminguide/touchtone-buffering.md @@ -223 +223 @@ When touchtone buffering is enabled, flow logs for the following blocks indicate -### Passing caller context via click-to-call or app-to-call +### Passing caller context via choose-to-call or app-to-call @@ -225 +225 @@ When touchtone buffering is enabled, flow logs for the following blocks indicate -Touchtone buffering also enables applications to pass known caller context into a flow before the conversation starts. In click-to-call and app-to-call scenarios, the originating application can append a customer identifier, web session reference, or other context to the dial string. For example, `tel:+15555555555,1234567` sends the digits `1234567` into the buffer the moment the call connects. The flow can then use that input to identify the caller, look up session or account details, and provide that context to an AI agent. This gives AI self-service the information it needs to personalize the interaction from the first turn, without asking the caller to re-identify themselves or explain why they are calling. +Touchtone buffering also enables applications to pass known caller context into a flow before the conversation starts. In choose-to-call and app-to-call scenarios, the originating application can append a customer identifier, web session reference, or other context to the dial string. For example, `tel:+15555555555,1234567` sends the digits `1234567` into the buffer the moment the call connects. The flow can then use that input to identify the caller, look up session or account details, and provide that context to an AI agent. This gives AI self-service the information it needs to personalize the interaction from the first turn, without asking the caller to re-identify themselves or explain why they are calling.