ive been having problems with submitting batch calling jobs using whatsapp configurations, my whats | ElevenLabs | Page 1

AI-generated Answer for bividib

Short answer: based on the current public docs, WhatsApp call‑permission templates used by outbound calls (including batch calls) do not expose any documented way to pass template parameters. The batch/create and WhatsApp outbound‑call endpoints only accept the template name and language code, not a parameters array. The only WhatsApp endpoint that documents parameter passing is the outbound‑message API, which takes template_params explicitly. There is no official documentation stating that call‑permission template variables are read from conversation_initiation_client_data.dynamic_variables.

What the docs say

Batch calling submit accepts:
- call_name, agent_id, recipients[]
- Optional whatsapp_params: whatsapp_call_permission_request_template_name, whatsapp_call_permission_request_template_language_code, whatsapp_phone_number_id. No parameter list is defined here. (elevenlabs.io)
Each batch recipient can carry whatsapp_user_id and an optional conversation_initiation_client_data object for dynamic variables/overrides, but that structure is documented for personalizing the agent, not for filling WhatsApp template parameters. (elevenlabs.io)
The WhatsApp outbound‑call endpoint similarly requires whatsapp_call_permission_request_template_name and whatsapp_call_permission_request_template_language_code but documents no template parameters field. (elevenlabs.io)
The only WhatsApp API that documents template parameters is outbound‑message, which requires template_params (components/parameters mirroring Meta’s format). (elevenlabs.io)
General WhatsApp integration docs describe selecting a call‑permission request template for outbound calls, but do not describe parameter mapping. (elevenlabs.io)

Implication for your error

If your chosen call‑permission template has 3 variables, the batch/outbound‑call APIs provide no documented field to supply them; sending conversation_initiation_client_data.dynamic_variables is not documented as the source for those placeholders. The “0 instead of 3” error is therefore consistent with the absence of a supported parameters path in these endpoints per current docs. (elevenlabs.io)

What is documented to work today

Use a call‑permission template with zero variables when scheduling outbound calls or batch calls via WhatsApp (since the endpoints only let you set template name and language). (elevenlabs.io)
If you must send a templated WhatsApp message with parameters, use the WhatsApp outbound‑message endpoint, which accepts template_params explicitly, and then proceed with calling once the user has granted permission. Note: this parameterized messaging step is only documented on the outbound‑message endpoint. (elevenlabs.io)

If you need confirmation or a feature update (e.g., allowing parameters for call‑permission templates in batch/outbound‑call), please contact ElevenLabs Support with your request IDs and payload

#ive been having problems with submitting batch calling jobs using whatsapp configurations, my whats