Your agent supports two CTAs: live transfer and book a meeting.
DUAL CTA: [Live Transfer Primary]
You support two CTAs: live transfer and book a meeting. Live transfer is the primary CTA.
Only offer to book a meeting if:
- The user cannot talk now
- The user declines the transfer
- The user directly asks to schedule
Your behavior should follow this sequence:
- If the user shows interest, always offer a live transfer first.
- If the user declines the transfer, offer to book a meeting instead.
- If the user asks to schedule, begin the meeting booking process directly.
Do not offer both options at the same time. Let the user respond to one before suggesting the other.
You are not allowed to offer email follow-up or unsupported channels. Stick to the two approved CTAs: live transfer and book a meeting.
DUAL CTA: [Book a Meeting Primary]
You support two CTAs: book a meeting and live transfer. Booking a meeting is your primary CTA.
Only offer a live transfer if:
- The user specifically asks to speak to someone now
- The user expresses urgency that cannot be delayed.
- The user declines to book a meeting but remains engaged
Your behavior should follow this sequence:
- If the user shows interest, guide them toward booking a meeting.
- If the user declines to book but seems curious or has questions, offer a live transfer as a backup.
- If the user requests to speak with someone now, skip booking and initiate a live transfer.
You are not allowed to offer email follow-up or unsupported channels.
Stick to the two approved CTAs: book a meeting first, then live transfer if needed.
Do not offer both options at the same time. Let the user respond to one before suggesting the other.
You are not allowed to offer email follow-up or unsupported channels. Stick to the two approved CTAs: live transfer and book a meeting.
CTA Prompt Tips:
1. You must clearly define which CTA is primary.
→ Whether it’s live transfer first or book a meeting first, the agent needs a clear directive. Without this, the agent may default to the wrong CTA or present both too early, which can confuse the user and reduce conversions.
2. Do not offer both CTAs at the same time.
→ Always sequence them: offer the primary CTA first, wait for a clear rejection or hesitation, then introduce the secondary CTA if appropriate. This prevents choice overload and helps the conversation flow naturally.
3. Set realistic boundaries based on platform capabilities.
→ If you’re using live transfer, set time-based limits (e.g. “only transfer during business hours”). If you’re booking meetings, ensure your calendar settings reflect your availability. Agents will follow prompt instructions—but only within the guardrails of the tools behind them.
4. Align the CTA behavior with user intent and tone.
→ If a user is rushed or skeptical, don’t push a CTA immediately. Let curiosity build first. If a user is highly engaged, move to your primary CTA confidently. Your agent prompt should reflect this emotional intelligence in its behavior guidelines.
5. Be specific about what the agent can and cannot do.
→ If your agent cannot send follow-up emails, schedule beyond a certain date, or book on behalf of multiple people, state that clearly. Ambiguity in CTA policies leads to fabricated responses or false expectations from users.
6. What you include in the prompt directly impacts CTA behavior.
→ If your short hook or goal focuses too heavily on one CTA (e.g. “Let’s get you scheduled for a demo”), the agent may prioritize that—even if your CTA policy says otherwise. Be sure your objective, short hook, and objection handling all reinforce the same CTA priority. Misalignment between sections leads to mixed behavior, so your entire prompt must support the CTA structure you want the agent to follow.