ts8466
03/21/2026, 11:54 PMAI Evy
03/21/2026, 11:54 PMAI Evy
03/21/2026, 11:55 PMAI Evy
03/21/2026, 11:55 PMfirst_name can be referenced as {{first_name}})
3. Configure the time window to define batch call time windows
4. Choose between "Send Now" to start calls immediately or "Schedule" for a future time
Pricing:
$0.005 per dial (20k calls for $100) [(1) ]() [(3) ]()
The automation streamlines communication workflows and is particularly useful for campaigns, updates, or any situation requiAI Evy
03/21/2026, 11:55 PMts8466
03/22/2026, 12:02 AMAI Evy
03/22/2026, 12:02 AMAI Evy
03/22/2026, 12:03 AMjavascript
import Retell from 'retell-sdk';
const client = new Retell({
apiKey: 'YOUR_RETELL_API_KEY',
}) ;
const batchCallResponse = await client.batchCall.createBatchCall({
from_number: '+14157774444',
tasks: [{ to_number: '+12137774445' }],
}) ;
console.log(batchCallResponse.batch_call_id) ;
Points importants :
- Les numéros doivent être au format E.164 (ex: +14157774444)
- Vous pouvez inclure des variables dynamiques dans chaque tâche
- Vous pouvez définir trigger_timestamp pour planifier l'envoi ou omettre ce paramètre pour un envoi immédiat
- Le coût est de $0.005 par appel [(2) ]() [(3) ]()
La documentation officielle de l'API Create Batch Call fournit tous les détails nécessaires pour l'intégration [(1) ]() .AI Evy
03/22/2026, 12:03 AMAI Evy
03/22/2026, 12:03 AMts8466
03/25/2026, 8:45 PMAI Evy
03/25/2026, 8:45 PMAI Evy
03/25/2026, 8:46 PMAuthorization - Header Value : Bearer YOUR_RETELL_API_KEY - Body : JSON avec la structure suivante : json { "from_number": "+14157774444", "tasks": [ { "to_number": "+12137774445" } ] } Points importants : - Le from_number doit être un numéro acheté ou importé dans Retell au format E.164 - Pour chaque ligne du CSV, créez une tâche dans le tableau tasks - Vous pouvez ajouter trigger_timestamp (en millisecondes Unix) pour planifier l'envoi, sinon les appels partent immédiatement - Pour des variables dynamiques personnalisées, ajoutez-les dans chaque objet task du tableau Conseil : Assurez-vous que vos numéros de téléphone dans le CSV sont au bon format avant l'envoi [(2) ]() . Les problèmes de formatage sont une cause fréquente d'erreurs . Le coût est de $0.005 par appel [(3) ]() .AI Evy
03/25/2026, 8:46 PMAI Evy
03/25/2026, 8:46 PMts8466
04/11/2026, 8:19 PMAI Evy
04/11/2026, 8:19 PMAI Evy
04/11/2026, 8:19 PMAI Evy
04/11/2026, 8:19 PMsend_now: true, but scheduled_timestamp is set to a future time (1775936837776 milliseconds = April 11, 2026) [(1) ]() . This creates a conflict.
Potential issues:
1. **Phone number permissions**: Your from_number (+33423565435 in the response, though you sent +33423500621) must be a number purchased from Retell or imported to Retell . If this French number isn't properly configured in your account, calls won't initiate [(2) ]() .
2. **International calling**: France (+33) may require specific permissions. International calling is supported for 14 countries, but you need to verify France is enabled for your account [(3) ]() .
3. **Scheduled timestamp conflict**: The scheduled_timestamp field represents a Unix timestamp in milliseconds for when to send the batch call [(1) ]() . If you want immediate execution with send_now, you should omit trigger_timestamp in your request .
4. **Recent platform issues**: There was a reported incident where scheduled batch calls didn't run from 2:35 PM to 5:15 PM PST on January 27 [(4) ]() . Additionally, other users have reported batch calls going to "ONGOING" status but never dialing [(5) ]() .
Recommended fixes:
- Verify your French number is properly imported and has outbound permissions enabled
- Remove trigger_timestamp from your payload if you want immediate execution
- Check that France is in your allowed outbound country list [(2) ](AI Evy
04/11/2026, 8:19 PMAI Evy
04/11/2026, 8:19 PMts8466
04/11/2026, 8:24 PMAI Evy
04/11/2026, 8:24 PMAI Evy
04/11/2026, 8:24 PMscheduled_timestamp is an output field from the API response, not something you send. [(1) ]()
The real issue is likely your phone number configuration:
Your from_number (+33423565435) must be:
- A number purchased from Retell or imported to Retell
- Properly bound to an agent to enable batch calls [(2) ]()
Key troubleshooting steps:
1. **Verify number binding**: Ensure the number is bound to agents to enable batch calls
2. **Check concurrency**: With a concurrency limit of 20, Retell automatically queues batch calls and starts a new call whenever one ends, keeping max 20 active calls at a time until all leads are completed [(3) ]()
3. **Monitor batch status**: Currently, there is no API to pull batch calling status data (success count, failed count, remaining calls) [(4) ]() - you'll need to monitor through the dashboard
4. **Time window configuration**: If you configured a call time window when creating the batch, calls will only execute during those allowed hours and days [(1) ]() [(2) ]()
Your payload looks correct - the issue is most likely that your French number isn't properly configured in your Retell account for outbound batch calling. Verify in your dashboard that this number is imported and bound to an agent.AI Evy
04/11/2026, 8:24 PMAI Evy
04/11/2026, 8:24 PMts8466
04/11/2026, 8:35 PMAI Evy
04/11/2026, 8:35 PMAI Evy
04/11/2026, 8:36 PM"total_task_count": 1 and "sent": 0, which means your batch call was created successfully but hasn't started executing yet. [(1) ]()
The issue is the scheduled timestamp:
Your response shows "scheduled_timestamp": 1775939465107 (April 11, 2026 at approximately 7:24 PM PST) with "send_now": true. Even though you set send_now: true, the system scheduled it for a future time based on your timezone setting ("timezone": "America/Los_Angeles") .
Why tasks show 0 sent:
From Saturday, April 11, 2026 (the current date) , the scheduled timestamp of 1775939465107 milliseconds converts to April 11, 2026 at 7:24 PM PST - which is in the future. The batch is in "planned" status waiting for that time to arrive before executing.
Solutions:
1. **Wait for execution time**: The batch will automatically start when the scheduled time arrives (7:24 PM PST)
2. **Check call time windows**: If you configured a call_time_window when creating the batch, calls will only execute during those allowed hours and days [(1) ]() [(2) ]()
3. **Verify number configuration**: Ensure your from_number (+33423500621) is bound to an agent in your dashboard to enable batch calls [(2) ]()
4. **Monitor in dashboard**: Navigate to the Batch Call tab to see real-time status updates
The batch call was created successfully - it's just waiting for the scheduled time or allowed calling window to begin execution.AI Evy
04/11/2026, 8:36 PMAI Evy
04/11/2026, 8:36 PMts8466
04/11/2026, 8:38 PMAI Evy
04/11/2026, 8:38 PMAI Evy
04/11/2026, 8:38 PMcall_time_window pour créer un batch call : [(1) ]()
javascript
import Retell from 'retell-sdk';
const client = new Retell({
apiKey: 'YOUR_RETELL_API_KEY',
}) ;
const batchCallResponse = await client.batchCall.createBatchCall({
from_number: '+14157774444',
tasks: [{ to_number: '+12137774445' }],
}) ;
console.log(batchCallResponse.batch_call_id) ;
Structure du call_time_window : [(2) ]() [(1) ]()
Le call_time_window définit les fenêtres horaires autorisées dans un fuseau horaire spécifique. [(1) ]() Chaque fenêtre est un intervalle semi-ouvert [startMin, endMin) en minutes depuis 00:00 heure locale.
Points importants :
- Les fenêtres ne peuvent pas traverser minuit (startMin < endMin doit être respecté)
- endMin = 1440 (24:00) est valide
- Les fenêtres sont exprimées en minutes locales depuis minuit
Exemple de réponse API avec call_time_window :
json
{
"batch_call_id": "batch_call_dbcc4412483ebfc348abb",
"name": "First batch call",
"from_number": "+14157774444",
"scheduled_timestamp": 1735718400,
"total_task_count": 123,
"call_time_window": {
"windows": [
{
"start": 540,
"end": 1020
}
],
"timezone": "<string>",
"day": [
"Monday"
]
}
}
Dans cet exemple, les appels sont autorisés le lundi entre 540 minutes (9:00) et 1020 minutes (17:00) depuis minuit dans le fuseau horaire spécifié.AI Evy
04/11/2026, 8:38 PMAI Evy
04/11/2026, 8:38 PMts8466
04/11/2026, 8:39 PMAI Evy
04/11/2026, 8:39 PMAI Evy
04/11/2026, 8:40 PMcall_time_window pour un envoi immédiat avec le fuseau horaire français (Europe/Paris) : [(1) ]()
json
{
"from_number": "+33423500621",
"tasks": [
{
"to_number": "+33612345678",
"retell_llm_dynamic_variables": {
"prenom": "jean",
"nom": "dupont"
}
}
],
"call_time_window": {
"windows": [
{
"start": 540,
"end": 1020
}
],
"timezone": "Europe/Paris",
"day": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"]
}
}
Explication du call_time_window :
- windows : Définit les plages horaires autorisées en minutes depuis minuit
- start: 540 = 9h00 (540 minutes depuis minuit)
- end: 1020 = 17h00 (1020 minutes depuis minuit)
- timezone : Utilisez "Europe/Paris" pour le fuseau horaire français
- day : Jours de la semaine autorisés (Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday)
Pour un envoi immédiat sans restriction horaire, omettez complètement le champ call_time_window de votre payload :
json
{
"from_number": "+33423500621",
"tasks": [
{
"to_number": "+33612345678",
"retell_llm_dynamic_variables": {
"prenom": "jean",
"nom": "dupont"
}
}
]
}
Si vous omettez call_time_window, les appels partiront immédiatement sans restriction de plage horaire.AI Evy
04/11/2026, 8:40 PMAI Evy
04/11/2026, 8:40 PM