Connecting an External Meeting Scheduler to Your Agent
Last updated: July 22, 2026
Add an external booking page to a Marketing Agent with an Agent CTA(Call to Action). The agent can offer the booking action when a visitor shows the intent or qualification signal you define.

Add the visitor-facing CTA Label.
Choose how the CTA opens under Behavior.
Enter the approved scheduler URL.
Define when the agent should show the CTA in Instructions.
Use Set as the default CTA only when the booking action should be the fallback.
The capture shows the empty app form exactly as opened. No scheduler URL, label, behavior, or instruction was inserted for the screenshot.
Choose the Right Booking Method
Goal | Use |
|---|---|
Open a Calendly, Chili Piper, or other approved booking URL | An Agent CTA configured in this article |
Let Docket route a visitor to an available host and create the meeting during the conversation. | The Google Calendar integration, plus Zoom when you want Zoom links. |
An Agent CTA opens the URL you provide. Native meeting routing uses the connected calendar, host availability, and the meeting platform configured for the agent.

When to trigger this CTA controls when the native booking action appears.
Meeting Settings controls the title, description, duration, and platform.
These native meeting controls are separate from the external URL CTA configured in the rest of this article.
Before You Start
You need permission to edit the Marketing Agent.
The external scheduler must have a working HTTPS booking URL.
Decide whether the scheduler supports iframe embedding or should open in a new tab.
Decide exactly when the agent should offer the meeting.
Open Agent CTAs
Open Marketing Agent Configuration.
Select the agent you want to update.
Open the Agent tab.
Expand Agent CTAs.
Select Add CTA.
Add the Booking CTA
Enter a short CTA Label, such as Book a Demo.
Paste the approved booking page into URL.
Choose iframe only when the scheduler supports embedding; otherwise choose the available new-tab behavior.
In Instructions, describe the visitor signal that should make the agent offer the CTA.
Select Set as the default CTA only when this should be the fallback action.
Select Add, then save the agent configuration.
An agent can have up to five configured CTAs. Keep each CTA's instructions distinct so the agent can choose the correct action.
Write Specific Instructions
Use a concrete visitor intent instead of a broad direction.
Recommended: Show this CTA after the visitor asks to schedule a product demonstration and confirms they want to speak with sales.
Avoid: Show this CTA to interested visitors.
Specific instructions reduce early or incorrect meeting offers.
Verify the Booking Experience
Open Preview for the agent.
Start a conversation that matches the CTA instructions.
Confirm the CTA label appears at the expected point in the conversation.
Open the CTA and confirm the correct booking page loads.
Repeat the test with a conversation that should not trigger the CTA.
If you selected iframe behavior, repeat the test in the deployed website experience.
Troubleshooting
Problem | What to check |
|---|---|
The CTA does not appear | Confirm Agent CTAs are enabled and make the instructions match a specific test conversation. |
The wrong CTA appears | Make the instructions for each CTA mutually distinct. |
The booking page is blank in an iframe | Switch the CTA to New tab; the scheduler may block embedding. |
The wrong booking page opens | Reopen the CTA and verify the complete HTTPS URL. |
The CTA appears too early | Add a stronger intent or qualification condition to the instructions. |