i have made a batch call through my app in retell...
# ❓・ai-evy-supportc
Client Nexus
12/30/2025, 1:54 PM@AI Evy i have made a batch call through my app in retell but a lot of calls were voicemail and that automatic voice replying press 1 to speak with someone or even wrost a inifinity press x number menu how can we avoid this? i want to set as option that the ai can choose one of the options to talk with someone? or and if this is not possible that when is this type of call we hang up, including voicemail , also i watn to return the reuslts of this call the reason for hang up in my app like, voicemail, the automatic menu recorded and etc
a
AI Evy
12/30/2025, 1:54 PMThanks for tagging me @Client Nexus. I'll look through relevant sources and get back to you shortly.
AI Evy
12/30/2025, 1:55 PM### Answer
---
You can handle these scenarios with a few Retell features:
## Voicemail Detection
Navigate to your agent settings → call settings and enable "Voicemail Detection". [(1) ]()
You can choose one of two behaviors:
- **Hang up**: The agent will disconnect when it detects a voicemail
- **Leave a message**: The agent will leave a message after it's the agent's turn to speak
If the call is detected as voicemail and the action was taken successfully, the call will have a disconnection reason of
voicemail_reacheddisconnection_reasonvoicemail_reacheduser_hangupagent_hangupdial_busydial_no_answer Copy code
javascript
const callResponse = await client.call.retrieve('119c3f8e47135a29e65947eeb34cf12d') ;
console.log(callResponse.disconnection_reason) ;call_analysisin_voicemailAI Evy
12/30/2025, 1:55 PM
To learn more, see the sources I considered:
[[1] Handle voicemail](https://docs.retellai.com/build/handle-voicemail)
[[2] Platform Changelogs | Retell AI](https://www.retellai.com/changelog)
[[3] Get Call](https://docs.retellai.com/api-references/get-call)
AI Evy
12/30/2025, 1:55 PMFeel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
c
Client Nexus
12/30/2025, 4:15 PM@AI Evy n Retell batch call details, is there any field like metadata / external_id / custom_id that we can set per lead (e.g., campaign_lead_id)?
a
AI Evy
12/30/2025, 4:15 PMThanks for the follow-up, @Client Nexus. I'll get back to you soon.
AI Evy
12/30/2025, 4:16 PM### Answer
Yes, in the Create Batch Call API, each task in the
tasksretell_llm_dynamic_variablescampaign_lead_idmetadata Copy code
javascript
tasks: [
{
to_number: '+12137774445',
retell_llm_dynamic_variables: {
customer_name: 'John Doe',
campaign_lead_id: 'your_lead_id_here'
}
}
]metadataretell_llm_dynamic_variablesAI Evy
12/30/2025, 4:16 PM
To learn more, see the sources I considered:
[[1] Create Batch Call](https://docs.retellai.com/api-references/create-batch-call)
[[2] Create Phone Call](https://docs.retellai.com/api-references/create-phone-call)
AI Evy
12/30/2025, 4:16 PMFeel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
c
Client Nexus
12/30/2025, 4:17 PM@AI Evy We run outbound AI calls from Retell. In our app (Supabase + edge functions), campaigns/leads remain “pending” although Retell shows completed calls and recordings.
Campaign: “Cold Call Sky 001 [99]” on subaccount “New Sky AI”. Retell batch_call_id: batch_call_298104f7ff9bcf636cb11.
We need a reliable way to map Retell call results back to our leads.
Questions:
Does batch call API return per-call fields including recording_url, duration, outcome, error, and a stable lead identifier?
Can we pass a per-lead metadata or external_id when creating batch calls, and will it be echoed back in webhook events / batch results?
What webhook event(s) should we subscribe to for batch call completion & per-call updates? Please share payload examples.
a
AI Evy
12/30/2025, 4:17 PMThanks for the follow-up, @Client Nexus. I'll get back to you soon.
AI Evy
12/30/2025, 4:17 PM### Answer
---
## 1. Per-Call Fields from the Get Call API
Yes, you can retrieve detailed per-call fields using the Get Call API. The response includes: [(1) ]()
-
recording_urlduration_msdisconnection_reasonagent_hangupuser_hangupdial_failedvoicemail_reachedcall_idmetadataretell_llm_dynamic_variables Copy code
javascript
import Retell from 'retell-sdk';
const client = new Retell({
apiKey: 'YOUR_RETELL_API_KEY',
}) ;
const callResponse = await client.call.retrieve('119c3f8e47135a29e65947eeb34cf12d') ;
console.log(callResponse) ;AI Evy
12/30/2025, 4:17 PM## 2. Passing Per-Lead Metadata in Batch Calls
Based on community feedback, the batch call API does not currently support passing
metadataoverride_agent_idretell_llm_dynamic_variablescampaign_lead_idcall_startedcall_endedcall_analyzedcall_endedcall_analysis Copy code
json
{
"event": "call_ended",
"call": {
"call_type": "phone_call",
"from_number": "+12137771234",
"to_number": "+12137771235",
"direction": "inbound",
"call_id": "Jabr9TXYYJHfvl6Syypi88rdAHYHmcq6",
"agent_id": "oBeDLoLOeuAbiuaMFXRtDOLriTJ5tSxD",
"call_status": "registered",
"metadata": {},
"retell_llm_dynamic_variables": {
"customer_name": "John Doe"
},
"start_timestamp": 1714608475945,
"end_timestamp": 1714608491736,
"disconnection_reason": "user_hangup",
"transcript": "..."
}
}AI Evy
12/30/2025, 4:17 PMKey notes:
- The webhook has a 10-second timeout and retries up to 3 times if no 2xx response is received
- If
metadataretell_llm_dynamic_variablesmetadataretell_llm_dynamic_variablescampaign_lead_idcall_endedAI Evy
12/30/2025, 4:17 PM
To learn more, see the sources I considered:
[[1] Get Call](https://docs.retellai.com/api-references/get-call)
[[2] Discord message from @gabe9001 on 2025-05-05](https://discord.com/channels/1186424376300679209/1186462578310910112/1368978866374181067)
[[3] Webhook Overview](https://docs.retellai.com/features/webhook-overview)
AI Evy
12/30/2025, 4:17 PMFeel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
c
Client Nexus
12/30/2025, 5:20 PM@AI Evy what else besides ivr and voicemail detection rtell have to avoid calls that are not good, like much time with no response, no lead reply and etc?
a
AI Evy
12/30/2025, 5:20 PMThanks for the follow-up, @Client Nexus. I'll get back to you soon.
AI Evy
12/30/2025, 5:20 PM### Answer
---
Beyond IVR navigation and voicemail detection, Retell offers several agent settings to handle unproductive calls:
## End Call After Silence
If users stay silent for a period after agent speech, the call will automatically end. [(1) ]()
- Minimum value: 10,000 ms (10 seconds)
- Default: 600,000 ms (10 minutes)
You can configure
end_call_after_silence_msreminder_trigger_msreminder_max_countmax_call_duration_msvoicemail_detection_timeout_msdisconnection_reasonAI Evy
12/30/2025, 5:20 PM
To learn more, see the sources I considered:
[[1] List Voice Agents](https://docs.retellai.com/api-references/list-agents)
[[2] Get Agent Versions](https://docs.retellai.com/api-references/get-agent-versions)
AI Evy
12/30/2025, 5:20 PMFeel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
c
Client Nexus
12/30/2025, 5:31 PM@AI Evy can you confirm if i have the correct set up?
Retell API Integration - Verified Correct:
Feature Retell API Parameter Our Implementation Status
Voicemail Detection enable_voicemail_detection ✅ Lines 206-226 in sync-agent Correct
Voicemail Action voicemail_option.action.type ✅ hang_up or static_text Correct
Voicemail Timeout voicemail_detection_timeout_ms ✅ Line 208 Correct
Silence Reminder reminder_trigger_ms ✅ Line 230 Correct
Reminder Count reminder_max_count ✅ Line 231 Correct
End After Silence end_call_after_silence_ms ✅ Line 236 Correct
Webhook Handling - Verified:
handleCallEnded (lines 1709-1757) checks for voicemail_reached in disconnection_reason and correctly sets callOutcome = 'voicemail'
Campaign leads are updated with the correct outcome
One Minor Gap Found: The IVR handling UI exists but Retell's API doesn't have a direct parameter for IVR digit navigation - this is handled by Retell internally. The settings are stored for potential future use.
Summary: The implementation is correct. Voicemail detection, silence reminders, and end-call-after-silence will sync to Retell and work when you save an agent. The webhook correctly tracks voicemail outcomes.
a
AI Evy
12/30/2025, 5:31 PMThanks for the follow-up, @Client Nexus. I'll get back to you soon.
AI Evy
12/30/2025, 5:31 PM### Answer
Based on the Retell AI API documentation, your parameter mapping looks correct. Here's confirmation against the documented fields:
Voicemail Settings:
-
enable_voicemail_detectionvoicemail_option.action.typestatic_texthang_upvoicemail_detection_timeout_msreminder_trigger_msreminder_max_countend_call_after_silence_ms Copy code
json
{
"action": {
"type": "static_text",
"text": "Please give us a callback tomorrow at 10am."
}
}disconnection_reasonvoicemail_reachedAI Evy
12/30/2025, 5:31 PM
To learn more, see the sources I considered:
[[1] Get Agent Versions](https://docs.retellai.com/api-references/get-agent-versions)
[[2] Create Voice Agent](https://docs.retellai.com/api-references/create-agent)
AI Evy
12/30/2025, 5:31 PMFeel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
c
Client Nexus
12/30/2025, 6:03 PM@AI Evy Here's how delays between campaign steps work, check below and let me know fi will work with retell batch campaigns?
Step Configuration: Each step in a campaign has waitTime and waitUnit properties (e.g., waitTime: 2, waitUnit: 'days')
After Step Completion: When a step completes (e.g., call ends), the retell-call-webhook calculates the next step's scheduled time:
waitMs = waitTime × unit_multiplier
scheduledFor = now + waitMs
minutes → waitTime × 60,000 ms
hours → waitTime × 3,600,000 ms
days → waitTime × 86,400,000 ms
Scheduling: A record is inserted into scheduled_campaign_steps with scheduled_for timestamp and status: 'pending'
Processing: The process-campaign-steps function (runs on cron) queries for pending steps where scheduled_for <= now() and executes them
Stop Conditions: Before execution, it checks if:
Campaign is still active
Contact has replied (if stopOnReply enabled)
Contact was manually stopped
The delay is per-step (configured in each step's waitTime/waitUnit), not the campaign-level delay_minutes which is for rotation between accounts.
Here's how delays between campaign steps work:
Step Configuration: Each step in a campaign has waitTime and waitUnit properties (e.g., waitTime: 2, waitUnit: 'days')
After Step Completion: When a step completes (e.g., call ends), the retell-call-webhook calculates the next step's scheduled time:
waitMs = waitTime × unit_multiplier
scheduledFor = now + waitMs
minutes → waitTime × 60,000 ms
hours → waitTime × 3,600,000 ms
days → waitTime × 86,400,000 ms
Scheduling: A record is inserted into scheduled_campaign_steps with scheduled_for timestamp and status: 'pending'
Processing: The process-campaign-steps function (runs on cron) queries for pending steps where scheduled_for <= now() and executes them
Stop Conditions: Before execution, it checks if:
Campaign is still active
Contact has replied (if stopOnReply enabled)
Contact was manually stopped
The delay is per-step (configured in each step's
a
AI Evy
12/30/2025, 6:03 PMThanks for the follow-up, @Client Nexus. I'll get back to you soon.
AI Evy
12/30/2025, 6:03 PM### Answer
Your multi-step campaign workflow approach is compatible with Retell batch calls, but you'll need to orchestrate the delays and scheduling on your side since Retell's batch call feature doesn't natively handle multi-step sequences with delays between steps.
What Retell Batch Call Supports:
- Immediate dispatch ("Send Now") or single scheduled time (
trigger_timestamp Copy code
javascript
const batchCallResponse = await client.batchCall.createBatchCall({
from_number: '+14157774444',
tasks: [{ to_number: '+12137774445' }],
}) ;call_endedprocess-campaign-stepsscheduled_for <= now()retell_llm_dynamic_variablescampaign_lead_idcall_endedscheduled_campaign_stepsscheduledForAI Evy
12/30/2025, 6:03 PM
To learn more, see the sources I considered:
[[1] Create Batch Call](https://docs.retellai.com/api-references/create-batch-call)
[[2] Platform Changelogs | Retell AI](https://www.retellai.com/changelog)
AI Evy
12/30/2025, 6:03 PMFeel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
c
Client Nexus
12/30/2025, 6:48 PM@AI Evy can you advise us in the below
1. CALENDAR FILTER INSTRUCTIONS (AI Selects Calendar)
We have a "Filtered" calendar mode where the AI should intelligently select which calendar to book based on natural language instructions (e.g., "Use Sales Calendar for enterprise clients, Support Calendar for existing customers").
Options we're considering:
A) System Prompt Injection: Include the filter instructions directly in the system prompt
B) Tool Description: Add the instructions to the check_available_timeslots tool description
C) Dynamic Variable: Pass as retell_llm_dynamic_variables with key like calendar_selection_rules
Question: Which approach works best for the LLM to understand and apply calendar selection logic? Should the AI return a calendar_id parameter when calling the booking tool, or should it pass selection criteria that our backend interprets?
a
AI Evy
12/30/2025, 6:48 PMThanks for the follow-up, @Client Nexus. I'll get back to you soon.
AI Evy
12/30/2025, 6:49 PM### Answer
Based on Retell's documented features, here's guidance for your calendar selection approach:
## Recommended Approach: Combine System Prompt + Tool Description
*Option A (System Prompt) * is best for defining the overall logic and decision criteria. The prompt engineering guide recommends structuring prompts with clear task instructions and using explicit tool calling instructions. [(1) ]()
*Option B (Tool Description) * should include explicit triggers for when to call the tool and what parameters to pass. The documentation states: "Always specify exact conditions for tool usage in your prompts. Reference tools by their exact names."
Example structure in your prompt:
Copy code
///## Tool Usage Instructions
1. Gather initial information about the customer's issue. Copy code
json
{
"customer_name": "John Smith",
"customer_type": "enterprise"
}AI Evy
12/30/2025, 6:49 PMFeel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
AI Evy
12/30/2025, 6:50 PM
To learn more, see the sources I considered:
[[1] Prompt Engineering Guide](https://docs.retellai.com/build/prompt-engineering-guide)
[[2] Dynamic Variables](https://docs.retellai.com/build/dynamic-variables)
[[3] Check Calendar Availability](https://docs.retellai.com/build/check-availability)
AI Evy
12/30/2025, 6:50 PMDynamic variables work in tool descriptions, so you could reference
{{customer_type}}calendar_idevent_type_idAI Evy
12/30/2025, 6:51 PM### Answer
---
## Recommended Pattern: Conversation Flow + Tool Parameters
Based on Retell's architecture, *Option B (Conversation Flow) * combined with *Option A (Tool Parameters) * is the recommended approach.
### Using Conversation Flow for Data Collection
Conversation flows let you split complex conversations into distinct stages, each with its own prompt and allowed tools. [(1) ]()
You can create nodes that sequentially collect information before reaching the booking tool:
Copy code
javascript
nodes: [
{
id: 'collect_info',
type: 'conversation',
instruction: {
type: 'prompt',
text: 'Ask the customer for their name and contact information.'
}
}
]states Copy code
javascript
states: [
{
name: 'information_collection',
state_prompt: 'You will follow the steps below to collect information...',
edges: [
{
destination_state_name: 'appointment_booking',
description: 'Transition to book an appointment.'
}
]
}
] Copy code
javascript
parameters: {
type: 'object',
properties: {
message: {
type: 'string',AI Evy
12/30/2025, 6:51 PM
To learn more, see the sources I considered:
[[1] Create Conversation Flow](https://docs.retellai.com/api-references/create-conversation-flow)
[[2] Create Retell LLM](https://docs.retellai.com/api-references/create-retell-llm)
[[3] Integrate Function Calling](https://docs.retellai.com/integrate-llm/integrate-function-calling)
AI Evy
12/30/2025, 6:51 PMThanks for the follow-up, @Client Nexus. I'll get back to you soon.
c
Client Nexus
12/30/2025, 6:51 PM@AI Evy 2. RESTAURANT/BAR BOOKING - DATA COLLECTION
For restaurant reservations, we need the AI to collect: party size, special requests (allergies, accessibility), reservation type (dining, bar, private event), and time preferences.
Options we're considering:
A) Tool Parameters: Add these as required/optional parameters in the book_appointment tool definition
B) Pre-Booking Questions: Use a separate conversation flow before calling the booking tool
C) Conversation Context: Let the AI collect naturally in conversation, then pass all data in a single booking_details object
Question: What's the recommended pattern for collecting multiple booking details before executing a tool? Should each field be a separate tool parameter, or should we use a nested object structure?
a
AI Evy
12/30/2025, 6:51 PMYou can define each field as a separate property within the
parametersAI Evy
12/30/2025, 6:52 PMFeel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
AI Evy
12/30/2025, 6:52 PMThanks for the follow-up, @Client Nexus. I'll get back to you soon.
c
Client Nexus
12/30/2025, 6:52 PM@AI Evy 3. CALENDAR SELECTION FLOW
When AI needs to select from multiple calendars based on context:
Options we're considering:
A) AI Selects Calendar ID: AI determines and passes specific calendar_id to booking tool
B) AI Provides Criteria: AI passes criteria (e.g., client_type: "enterprise"), backend selects calendar
C) Two-Step Flow: First call get_available_calendars tool, then call check_availability with selected calendar
Question: Which flow provides the best accuracy and reliability? Does Retell support multi-step tool calling where the second call depends on the first call's response?
a
AI Evy
12/30/2025, 6:52 PM[(2) ]()
The LLM receives this result and can then decide to call another tool based on the returned data.
Accuracy consideration: Option B (backend selection) is most reliable for deterministic outcomes since your backend logic handles the mapping, but Option C gives the AI more context to make informed decisions during the conversation.
AI Evy
12/30/2025, 6:52 PM
To learn more, see the sources I considered:
[[1] Integrate Function Calling](https://docs.retellai.com/integrate-llm/integrate-function-calling)
[[2] LLM WebSocket](https://docs.retellai.com/api-references/llm-websocket)
[[3] Check Calendar Availability](https://docs.retellai.com/build/check-availability)
AI Evy
12/30/2025, 6:55 PMFeel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
AI Evy
12/30/2025, 6:55 PM### Answer
## Multi-Step Tool Calling Support
Yes, Retell supports multi-step tool calling where subsequent calls depend on previous results. The function calling integration allows the LLM to intelligently choose to output JSON containing arguments to call one or many functions. [(1) ]()
When a tool call completes, you can send the result back and the LLM can then make additional tool calls based on that response. [(2) ]()
## Recommended Approach: Option A or C
*Option A (AI Selects Calendar ID) * is simpler and works well if you include clear selection criteria in your prompt. The Cal.com integration requires an
event_type_idget_available_calendarscheck_calendar_availabilitybook_appointmentevent_type_id Copy code
json
{
"response_type": "tool_call_result",
"tool_call_id": "unique_id",
"content": "result_string"
}AI Evy
12/30/2025, 6:56 PM### Answer
## Recommended Approach: Option B or C
For tool call responses (like your booking tool) , return structured data that the AI can use to generate a natural confirmation. [(1) ]()
### Tool Call Response Structure
When your booking tool completes, return the result as a string in the
content Copy code
json
{
"confirmation_number": "RES-12345",
"status": "confirmed",
"party_size": 4,
"date": "2025-01-15",
"time": "7:00 PM",
"special_requests": "window seat, dairy allergy",
"next_steps": "Arrive 10 minutes early. Cancellation requires 24-hour notice."
}speak_messagenext_stepsAI Evy
12/30/2025, 6:56 PM
To learn more, see the sources I considered:
[[1] Inbound webhook](https://docs.retellai.com/features/inbound-call-webhook)
c
Client Nexus
12/30/2025, 6:56 PM@AI Evy 4. WEBHOOK RESPONSE DATA
After successful restaurant booking, what data should we return in the webhook response?
Options we're considering:
A) Confirmation Only: Just confirmation number and status
B) Full Booking Details: Confirmation + all collected details (party size, requests, etc.)
C) Confirmation + Follow-up: Include next steps or additional instructions for the AI to communicate
Question: What's the optimal response structure for the AI to naturally confirm the booking with the customer? Should we include a speak_message field for the AI to read verbatim, or let it generate confirmation naturally from the data?
a
AI Evy
12/30/2025, 6:56 PMThanks for the follow-up, @Client Nexus. I'll get back to you soon.
AI Evy
12/30/2025, 6:58 PMFeel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
AI Evy
12/30/2025, 6:58 PM### Answer
## Recommended Approach: Handle Default in Backend
Based on Retell's Cal.com integration, the
check_calendar_availabilitytimezoneAI Evy
12/30/2025, 6:58 PM
To learn more, see the sources I considered:
[[1] Check Calendar Availability](https://docs.retellai.com/build/check-availability)
AI Evy
12/30/2025, 6:58 PM### Answer
Your tool definitions align with Retell's Cal.com integration structure. Here's confirmation:
## Check Availability Tool
The documented setup includes:
[(1) ]()
- API Key from cal.com
- Event Type ID
- Tool description
- (optional) : add a timezone to be used in the function
## Book Appointment Tool
The documented structure shows:
[(2) ]()
- API Key from cal.com
- Event Type ID
- Tool description
- (optional) : add a timezone to be used in the function
## API Response Structure Reference
From the Retell LLM API, the
book_appointment_cal Copy code
json
{
"type": "book_appointment_cal",
"name": "book_appointment",
"description": "Book an annual check up.",
"cal_api_key": "cal_live_xxxxxxxxxxxx",
"event_type_id": 60444,
"timezone": "America/Los_Angeles"
}{{current_time}}{{current_time}}{{current_time}}{{current_time}}{{current_time}}AI Evy
12/30/2025, 6:58 PM
To learn more, see the sources I considered:
[[1] Check Calendar Availability](https://docs.retellai.com/build/check-availability)
[[2] Book Calendar](https://docs.retellai.com/build/book-calendar)
[[3] List Retell LLMs](https://docs.retellai.com/api-references/list-retell-llms)
[[4] Issue with book_appointment function](https://discord.com/channels/1186424376300679209/1341725205445476413)
[[5] Discord message from @melvinglenford on 2025-03-06](https://discord.com/channels/1186424376300679209/1186462578310910112/1347206753783250995)
AI Evy
12/30/2025, 6:58 PMThanks for the follow-up, @Client Nexus. I'll get back to you soon.
AI Evy
12/30/2025, 6:58 PMFeel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
c
Client Nexus
12/30/2025, 6:58 PM@AI Evy Current Tool Definitions Reference:
{
"check_available_timeslots": {
"parameters": {
"date": "required - YYYY-MM-DD format",
"timezone": "conditionally required based on agent config"
}
},
"book_appointment": {
"parameters": {
"date": "required",
"time": "required",
"timezone": "required",
"customer_name": "required",
"customer_email": "optional",
"customer_phone": "optional"
}
}
}
Client Nexus
12/30/2025, 6:58 PM@AI Evy 5. TIMEZONE HANDLING CONFIRMATION
We currently have two modes:
Auto-detect: AI asks customer for timezone if not known
Default timezone: Use business default without asking
We implement this by conditionally including timezone as a required parameter in the check_available_timeslots tool.
Question: Is conditionally modifying tool parameters (required vs optional) the correct approach, or should we always include timezone and handle the default in our backend?
a
AI Evy
12/30/2025, 6:58 PMFeel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
AI Evy
12/30/2025, 6:58 PMThanks for the follow-up, @Client Nexus. I'll get back to you soon.
c
Client Nexus
12/31/2025, 6:55 PM@AI Evy is this correct? we had an issue where we launch the campaign in our app but ithe emtrics were not update there even though it was in retell
📋 Retell Batch Call Integration Setup
Outbound Flow (Your App → Retell)
execute-campaign → Retell create-batch-call API
Payload sent to Retell:
{
"from_number": "+14159425808",
"override_agent_id": "agent_xxx",
"name": "Campaign: Campaign Name (timestamp)",
"tasks": [
{
"to_number": "+1234567890",
"retell_llm_dynamic_variables": {
"__subaccount_id__": "uuid",
"__agent_id__": "uuid",
"__contact_id__": "uuid",
"campaign_lead_id": "uuid", // Key for tracking
"campaign_id": "uuid",
"contact_name": "John Doe",
// ... other variables
},
"metadata": {
"campaign_id": "uuid",
"contact_id": "uuid",
"subaccount_id": "uuid",
"source": "batch_campaign"
}
}
]
}
Inbound Flow (Retell → Your App)
Retell sends webhooks to retell-webhook-handler:
call_started → Creates/updates call record with campaign metadata
call_ended → Updates campaign_leads with outcome, duration, recording
call_analyzed → Adds transcript and AI summary
Manual Sync (sync-batch-call-results)
Call this to pull latest results from Retell:
POST /functions/v1/sync-batch-call-results
{ "campaignId": "uuid" }
a
AI Evy
12/31/2025, 6:55 PMThanks for the follow-up, @Client Nexus. I'll get back to you soon.
AI Evy
12/31/2025, 6:55 PM### Answer
---
Your batch call payload structure looks correct based on the documented API. [(1) ]()
## Create Batch Call API Structure
The required fields are:
-
from_numbertasksnameto_numberretell_llm_dynamic_variablesmetadatacall_startedcall_endedcall_analyzeddial_failedcall_startedcall_endedcall_analyzedmetadataretell_llm_dynamic_variablescall_idAI Evy
12/31/2025, 6:55 PM505937952/1337135932528136287) You'd need to track individual
call_endedAI Evy
12/31/2025, 6:55 PM
To learn more, see the sources I considered:
[[1] Create Batch Call](https://docs.retellai.com/api-references/create-batch-call)
[[2] Webhook Overview](https://docs.retellai.com/features/webhook-overview)
[[3] Get Call](https://docs.retellai.com/api-references/get-call)
[[4] List Calls](https://docs.retellai.com/api-references/list-calls)
[[5] Discord message from @vilewired on 2025-02-06](https://discord.com/channels/1186424376300679209/1294891368505937952/1337135932528136287)
AI Evy
12/31/2025, 6:55 PMFeel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.