### Answer Based on the available sources, I can see you're experiencing issues with the Check Calendar Availability node in batch calls versus testing [(1) ]() . For the Check Calendar Availability function to work properly, you need to ensure you've configured it with the required Cal.com credentials : 1. API Key from Cal.com - obtained from Settings → Developer → API Keys 2. Event Type ID - the number in your Cal.com event type URL 3. Tool description (example: "Checks availability for 30-minute consultation calls") 4. (Optional) Timezone to be used in the function The sources indicate that when the agent is working in batch calls but behaving differently than in testing, this could be related to how variables are injected at call creation. One community discussion notes that "Retell will hallucinate dates unless availability is injected into the call context at call creation" [(2) ]() . The key issue highlighted is: "If GHL triggers the call before Make finishes, Retell will not read the latest availability" . For batch calls specifically, you may need to verify that: - The calendar configuration is properly saved in the agent settings - Dynamic variables are being passed correctly when the batch call is initiated [(3) ]() - The webhook timeout is sufficient for your calendar API to respond Since testing works but batch calls don't follow the conversation flow properly, I recommend checking if there's a timing or variable injection issue specific to how batch calls are initiated versus manual testing. If this doesn't resolve your issue, you may want to check the call history to see the exact error messages and review your webhook response times.

​ To learn more, see the sources I considered: [[1] Check Calendar Availability](https://docs.retellai.com/build/check-availability) [[2] GHL + Make + Retell](https://community.retellai.com/t/ghl-make-retell/806) [[3] Streamline Calls with Retell AI’s Batch Dialer | Retell AI](https://www.retellai.com/blog/boost-operation-efficiency-with-retell-ais-batch-calling) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer The agent is a duplicate of another agent that is working and booking meetings Since you duplicated an agent that works, but the duplicate shows "calendar not configured" during batch calls, here are specific troubleshooting steps: Verify Calendar Configuration in the Duplicate Agent: Even though it's a duplicate, the Check Calendar Availability function requires these specific credentials to be saved in each agent [(1) ]() : - Cal.com API Key - Event Type ID - Tool description - (Optional) Timezone Check Batch Call Variable Injection: The community has identified that batch calls can fail if variables aren't properly injected at call creation [(2) ]() . When creating batch calls, ensure you're passing any required dynamic variables through the API. When creating a batch call via API, the structure should include variables if needed [(3) ]() :

json
{
  "from_number": "+14157774444",
  "tasks": [{ 
    "to_number": "+12137774445",
    "retell_llm_dynamic_variables": {
      "customer_name": "John Doe"
    }
  }]
}

Prompt Configuration: Add explicit guidance in your global prompt about when to invoke the calendar function [(1) ]() :

When user stated a time range, please check the calendar availability by calling the `check_calendar_availability` function and let user know whether that range work or not.

Agent-Specific Settings: Check if the duplicate agent has its own webhook configuration that might differ from the working agent. Webhook settings can be configured at both account-level and agent-level [(4) ]() . If the agent has agent-level webhooks set, those take precedence over account-level webhooks . Since testing works but batch calls don't, this points to a difference in how the call context is initialized between test calls and batch calls, particularly around variable injection timing [(2) ]() .

​ To learn more, see the sources I considered: [[1] Check Calendar Availability](https://docs.retellai.com/build/check-availability) [[2] GHL + Make + Retell](https://community.retellai.com/t/ghl-make-retell/806) [[3] Create Batch Call](https://docs.retellai.com/api-references/create-batch-call) [[4] Webhook Overview](https://docs.retellai.com/features/webhook-overview) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.