Setting Up Agent CTAs
Last updated: July 22, 2026
Agent CTAs let your Marketing Agent show relevant call-to-action buttons during conversations. Use CTAs to send visitors to the right next step, such as a meeting page, upgrade page, support page, or other URL.
CTAs will also help your visitors to book meetings or show them relevant pages within the Docket agent's widget window.

Before You Start
You need access to app.docketai.com.
You need an existing Marketing Agent.
Know the URL you want each CTA to open.
Open Agent CTAs
Open Marketing Agent Configuration.
Select the agent you want to configure.
Open the Agent tab.
In Setup & Manage, open Agent CTAs.
Turn on the Agent CTAs switch.
Add a CTA

Click Add CTA.
Enter a Label. This is the button text visitors see in the widget.
Choose the Behavior. The public Docket help article documents two options: opening the URL in an iframe or opening it as a new tab.
Enter the URL.
Add Instructions that tell the agent when this CTA should be shown.
If this CTA should appear when no other CTA is applicable, select Set as default CTA.
Click Add.
Default CTA Behavior
You can have only one default CTA at a time. If no default CTA is configured, the agent may not show a CTA button when none of the CTA-specific instructions apply.
Use a default CTA for the broadest next step, such as booking a demo or contacting sales. Use specific CTAs for narrower cases, such as support, upgrade, pricing, or implementation questions.
Write Good CTA Instructions
CTA instructions should describe the visitor intent that should trigger the button.
Good examples:
Show this CTA when the visitor asks to book time with sales.
Show this CTA when the visitor asks about implementation or technical setup.
Show this CTA when the visitor asks where to find support documentation.
Avoid vague instructions like "show when useful." The agent needs clear criteria to choose between multiple CTAs.
Manage Existing CTAs
You can add multiple CTAs for one agent and delete CTAs from the same Agent CTAs screen.
After changing CTAs, click Save if the page requires it, then use Preview to confirm the agent shows the expected CTA for the right conversation scenario.
Verify CTA Behavior
Reload the Agent tab and reopen Agent CTAs.
Confirm each CTA label, URL, behavior, and instruction persisted.
In Preview, send a message that clearly matches one CTA's instructions.
Confirm the expected button appears, opens the correct URL, and uses the configured behavior.
Test a message that does not match a specific CTA. If a default CTA is configured, confirm that button appears instead.
The configuration is ready when each test prompt produces the intended CTA and no unrelated CTA appears.
Best Practices
Keep CTA labels short and action-oriented.
Use one CTA for one clear next step.
Make instructions mutually distinct so the agent can choose the right CTA.
Set a default CTA only when there is a safe general next step.
Test each CTA with a realistic visitor prompt before launch.
Troubleshooting
Issue | What to check |
|---|---|
CTA does not appear | Confirm Agent CTAs are enabled and the CTA instructions match the visitor scenario. |
Wrong CTA appears | Make the CTA instructions more specific and reduce overlap between CTAs. |
Default CTA does not appear | Confirm Set as default CTA is selected for exactly one CTA. |
CTA opens the wrong way | Check the selected Behavior for that CTA. |