Skip to main content
The Start Call node is the first thing that runs when a call connects. It controls the agent’s name, how it greets the caller, what it says in the opening turn, and what data it collects or fetches before the conversation begins.
Every agent must have exactly one Start Call node. You cannot delete it or add more than one.

​
Settings

Name A short label shown on the canvas and in call logs. Use a clear name so you can identify the node at a glance — for example, Opening or Cold Call Opener.
Greeting Type Controls how the agent delivers its opening message before the main prompt runs.
  • Text (TTS) — The agent reads the Greeting Text aloud using its voice
  • Pre-recorded audio — Plays a fixed audio file instead of generated speech
Greeting Text The exact words spoken when the call connects. This plays before the agent’s prompt logic runs. Supports {{template_variables}} so you can personalise the greeting with customer data. Example:
Leave this empty to skip the greeting and go straight to the prompt.
Prompt The agent’s instructions for the opening turn of the conversation. Write what the agent should do, say, and how to handle the first few exchanges. Supports {{template_variables}} from Pre-Call Data Fetch and Initial Context. This is where you define the tone, the opening script, when to move to the next node, and how to handle edge cases like wrong numbers or hesitant callers.
Allow Interruption
  • On (default) — The caller can speak while the agent is talking and the agent will stop and listen immediately
  • Off — The agent finishes speaking before it listens, even if the caller tries to say something
Add Global Prompt When turned on, the Global Node instructions are prepended to this node’s prompt at runtime. Recommended to keep on so the agent’s tone and behaviour rules apply from the very first word.
Delayed Start When turned on, the agent waits a moment before speaking after the call connects. Useful for outbound calls where the called party needs a second to settle after picking up. Keep off for inbound calls.
Enable Variable Extraction When turned on, the agent extracts specific data points from the conversation during this node. You define what to look for — for example, the caller’s name, their intent, or whether they confirmed an appointment. Variables extracted here:
  • Appear in the Leads page so you can track what was captured for each call
  • Can be used as conditions in the Follow-up node to decide whether and how to follow up
Use this when you need to capture key information early in the call — like the caller’s identity or their response to the opening — before the conversation moves forward.
Tools Attach tools the agent can call during the opening turn — for example, checking availability, looking up a customer record, or verifying a phone number. Tools added here are available only during this node’s turn. See Tools for how to create and manage tools.
Knowledge Base Documents Attach documents the agent can reference while handling the opening. Useful if the agent needs to answer basic questions about your product or company during the greeting phase. See Knowledge Base for how to upload and manage documents.
Pre-Call Data Fetch When turned on, Voicerix makes a POST request to an external API before the call starts. The JSON response is merged into the call context as template variables. Use this to pull live customer data — like name, account details, or outstanding balance — so the agent can personalise the conversation from the very first line. Example: if your API returns { "first_name": "Rahul", "emi_amount": "8500" }, you can use {{first_name}} and {{emi_amount}} anywhere in the prompt.

​
Conditions

Conditions are the arrows connecting this node to the next one on the canvas. Typically the Start Call node has one condition leading to the first Agent Node where the main conversation begins. See Conditions for a full explanation of Condition Label, Condition, and Transition Speech.