Proactive Voice Outreach Agent

Most voice agent demos stop at inbound. A customer calls in, the agent answers, tools fire, everyone is impressed. But the harder and more valuable problem is outbound - an agent that decides when to call, who to call, and what to say, all without a human pushing a button.

This blueprint solves that problem by combining three ChatBotKit primitives: a trigger integration that wakes an agent on a schedule, CRM abilities that let the agent inspect pipeline state, and the ElevenLabs SIP trunk call ability that lets the agent initiate a real phone call.

How it works

A Scheduler Agent runs every hour via a trigger integration. On each run it:

1. Searches HubSpot deals that are stalled, overdue, or in a stage that requires follow-up.
2. Fetches the associated contact details including phone number.
3. Evaluates whether a voice call is warranted based on deal value, days since last activity, and stage.
4. If conditions are met, initiates an outbound call via elevenlabs/sip-trunk-call/start, passing the contact phone number and injecting CRM context (deal name, value, stage) as dynamic variables so the ElevenLabs voice agent has full context.
5. Logs the outreach attempt to a shared workspace file for audit and deduplication.
6. Updates the HubSpot contact with a note recording that an automated call was placed.

The ElevenLabs voice agent handles the live conversation. It is configured on the ElevenLabs side with a prompt that references the dynamic variables injected at call time. ChatBotKit does not control the voice conversation itself - it controls when and why the call happens, and what context the voice agent receives.

Separation of concerns

The system uses three independent skillsets. The Voice Agent MCP Toolkit powers the MCP server that the ElevenLabs voice agent connects to during live calls. It provides limited, read-only deal and contact lookups plus a calendar scheduling ability - just enough for the voice agent to be useful on a call without exposing full CRM write access. The Voice Calling Toolkit powers the Scheduler Agent. It contains the ElevenLabs call ability with a hardcoded agent ID, read-only CRM lookups for deciding who to call, and workspace logging for audit and deduplication. The Pipeline CRM Toolkit powers the Pipeline Assistant bot with full CRM read/write access for the sales team.

The MCP layer

The MCP server exposes only the Voice Agent MCP Toolkit - a limited set of read-only tools the ElevenLabs voice agent can call during live conversations. It intentionally does not include calling abilities, CRM write access, or workspace operations. The voice agent gets just enough context to have a productive conversation without overstepping.

Safeguards

The scheduler writes a call log to the shared workspace before placing each call. On subsequent runs it reads the log to avoid calling the same contact twice within a configurable cooldown window. The backstory instructs the agent to never call outside business hours and to cap outbound calls per run.

Extending the system

• Add slack/message/send to notify your sales team when a call is placed.
• Add sendgrid/email/send to send a follow-up email after each call.
• Swap HubSpot for Salesforce or Pipedrive by changing the CRM abilities.
• Add a second trigger on a different schedule for different deal stages.
• Connect a Telegram or Slack integration to the scheduler bot so you can ask "who did you call today?" conversationally.

Backstory

Common information about the bot's experience, skills and personality. For more information, see the Backstory documentation.