> For the complete documentation index, see [llms.txt](https://limechatai.gitbook.io/limechat-product-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://limechatai.gitbook.io/limechat-product-guide/whatsapp-marketing/flows/action-nodes/start-telephony-call.md).

# Start Telephony Call

**Action Node: Start Telephony Call**

***

#### Node Name:

Start Telephony Call

***

#### What it does:

Initiates a phone call with the user directly from the flow. The call can be handled by a configured voice agent that can converse with the user in a human-like manner.

***

#### When to Use:

* When you want to escalate from chat to a voice call<br>
* For high-intent scenarios (e.g., lead qualification, support resolution)<br>
* When automated voice interaction is preferred over text<br>
* For proactive outreach (e.g., reminders, onboarding calls)<br>

***

#### UI Inputs:

* **Name**
  * Type: Text (mapped from event field)<br>
  * Required: No<br>
  * Description: Name of the user to be used during the call<br>
  * Special Behavior: Can be dynamically passed from trigger event data<br>
* **CRM Inbox**
  * Type: Dropdown (server-fetched)<br>
  * Required: No<br>
  * Description: Select the CRM inbox through which the call will be managed<br>
  * Special Behavior:
    * Options are fetched dynamically<br>
    * Refresh button available to reload latest inboxes<br>
* **Voice Agent**
  * Type: Dropdown (server-fetched)<br>
  * Required: Yes<br>
  * Description: Select the voice agent that will handle the call and interact with the user<br>
  * Special Behavior:
    * Options are fetched dynamically from available voice agents<br>
    * Refresh button available<br>
* **Registration Number**
  * Type: Text (mapped from event field)<br>
  * Required: No<br>
  * Description: Any identifier (e.g., lead ID, user ID) to associate with the call<br>
  * Special Behavior:
    * Supports dynamic values from trigger event<br>
    * Useful for tracking or backend mapping<br>

***

#### Outputs:

* **successful**
  * Type: Boolean<br>
  * Meaning:
    * true → Call was successfully initiated<br>
    * false → Call initiation failed<br>
* **call\_id**
  * Type: Text<br>
  * Meaning: Unique identifier of the initiated call (can be used for tracking or downstream actions)<br>

***

#### Requirements:

* **Supported Events:**
  * All events (*all*)<br>
* **Required Integrations:**
  * None explicitly required<br>
  * (However, voice agents must be pre-configured in the system)<br>

***

#### Notes:

* Voice Agent is mandatory — the call cannot be initiated without selecting one<br>
* This node enables a shift from chat-based automation to voice-based interaction<br>
* Typically used in mid or end stages of flows where deeper interaction is needed<br>
* Ensure voice agents are properly configured before using this node