Calls to action, or CTAs, are buttons that can surface during visitor Conversations to help move a visitor toward a defined action.
The deployed interface describes them as buttons used to drive demos, sign-ups, purchases, or other targeted destinations.
Open the Agent and select CTAs.
The page heading is Calls to action and contains an Add a CTA form.
The user-facing form provides:
The internal Name helps workspace users identify the CTA configuration. It is separate from the visitor-facing Button label.
Use a clear internal identifier that describes the CTA's purpose.
The Button label is the action text a visitor sees.
Examples include:
Use wording that accurately describes what happens after the visitor selects the button.
The deployed CTA interface provides these Kinds:
Select the type that most closely matches the visitor action.
Enter the complete destination in Target URL.
Verify that the URL is correct, publicly reachable as intended, and points to the exact page the Button label promises.
The Existing section displays each CTA's visitor label, Kind, and destination.
This provides a quick way to verify where configured buttons will direct visitors.
Use the delete action beside the CTA and confirm the request.
Before deleting a CTA that may already be used in live visitor flows, confirm that its removal will not leave an important conversion path unavailable.
Use Playground to test realistic visitor questions that should cause a CTA to appear.
Playground renders CTA information with the response and lets you verify the visitor-facing Button label and destination before relying on the CTA in production.