Creating an AI Caller Bot
Each bot is configured with:Conversation Design
Output Variable Types
Each output variable specifies what kind of data to capture:
Each variable also includes a capture prompt — an instruction that tells the bot exactly what to listen for.
Voice & Audio Settings
Realtime Model
Choose which GPT Realtime model powers the conversation:Turn Detection
Controls how the bot recognizes when the candidate has finished speaking:Smooth Barge-in
When enabled, the bot uses local Silero-based VAD to detect when a candidate speaks over the bot, making the mid-sentence barge in feel more natural. Disabled by default.Summarization
A summary of the conversation is automatically generated after every call. A custom summary prompt can be provided to control what aspects of the conversation are highlighted.Conversation History
When enabled, the bot includes summaries from prior calls with the same candidate in its context — useful for multi-stage workflows or follow-up calls.Call Recording
Call recording requires a feature flag to be enabled for your account. Once enabled, recordings are stored securely and linked to the enrollment record. Even without the feature flag, recording can be enabled for individual test calls to review bot behaviour before going live.Data Access
The bot can optionally be granted access to the candidate’s full data profile, allowing it to reference application details, documents, and other information during the conversation.Tool Calling
Bots can invoke automations during a live call. Each linked automation (a Caller Bot Automation) is exposed to the AI as a callable tool.
The AI decides when to invoke a tool based on the conversation context and tool descriptions. Automations run asynchronously — the call continues while the automation executes.
Call Types
How Calls Are Triggered
Form Integration
When an AI Caller is embedded within a hiring flow form, admins configure form mappings:- Input mappings connect data from the candidate’s profile to the bot’s input variables
- Output mappings connect the bot’s captured responses to specific form fields
Call Logs & Monitoring
Every call generates a detailed enrollment record. Admins can review calls across three views:- Test Logs — Calls initiated from the admin test interface
- Automation Logs — Calls triggered by automations
- Application Logs — Calls triggered during form submission
Log Filters
Call Detail
Each call record includes:
Admins can re-trigger a test call or re-compute captured answers from the transcript.