> 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/reorder-call.md).

# Reorder Call

**Node Name:**\
Reorder Call

***

**What it does:**\
Initiates an automated telephonic call to the user during an ongoing conversation, specifically aimed at encouraging or assisting with reordering a previously purchased product. The call is handled by a configurable AI voice agent that can converse naturally with the user.

***

**When to Use:**

* To drive repeat purchases by reminding users to reorder past items<br>
* In post-purchase or retention flows (e.g., after a certain number of days since last order)<br>
* When you want proactive outbound engagement via voice instead of WhatsApp text<br>
* For personalized upsell/cross-sell using past order context<br>

***

**UI Inputs:**

* **CRM Inbox**
  * Type: Dropdown (server-fetched)<br>
  * Required: No<br>
  * Description: Select the CRM inbox through which the call context is managed<br>
  * Special Behavior: Dynamic list with refresh option<br>
* **Voice Agent**
  * Type: Dropdown (server-fetched)<br>
  * Required: Yes<br>
  * Description: Select the AI voice agent that will make and handle the call<br>
  * Special Behavior: Dynamically fetched list of available voice agents<br>
* **Customer Name**
  * Type: Event Field Mapping (Text)<br>
  * Required: Yes<br>
  * Description: Name of the customer to personalize the call conversation<br>
  * Special Behavior: Pulled from trigger event data<br>
* **Offer Discount**
  * Type: Text Input<br>
  * Required: No<br>
  * Description: Optional discount value to incentivize reorder during the call<br>
  * Special Behavior: Manually entered<br>
* **Last Order Date**
  * Type: Event Field Mapping (Text)<br>
  * Required: No<br>
  * Description: Date of the user’s last order<br>
  * Special Behavior: Pulled from trigger event data<br>
* **Shipping Address**
  * Type: Event Field Mapping (Text)<br>
  * Required: No<br>
  * Description: Customer’s delivery address for reference during call<br>
  * Special Behavior: Pulled from trigger event data<br>
* **Last Ordered Item Names**
  * Type: Event Field Mapping (Text)<br>
  * Required: Yes<br>
  * Description: Names of previously ordered items to drive reorder conversation<br>
  * Special Behavior: Pulled from trigger event data<br>

***

**Outputs:**

* **successful**
  * Type: Boolean<br>
  * Meaning: Whether the call was successfully initiated<br>
* **call\_id**
  * Type: Text<br>
  * Meaning: Unique identifier for the call<br>
* **call\_status**
  * Type: Text<br>
  * Meaning: Status of the call (e.g., completed, failed, no answer)<br>
* **user\_intent**
  * Type: Text<br>
  * Meaning: Detected intent of the user during the call (e.g., reorder, not interested)<br>
* **feedback\_sentiment**
  * Type: Text<br>
  * Meaning: Sentiment derived from the user’s responses (e.g., positive, negative)<br>
* **feedback\_notes**
  * Type: Text<br>
  * Meaning: Key feedback or remarks captured during the call<br>
* **call\_summary**
  * Type: Text<br>
  * Meaning: Summary of the conversation<br>
* **reorder\_call (structured data)**
  * Type: Object<br>
  * Meaning: Detailed structured data related to the reorder interaction<br>

***

**Requirements:**

* **Supported Events:**
  * All events (*all*)<br>
* **Required Integrations:**
  * None explicitly required<br>

***

**Notes:**

* This node is highly context-driven and works best when accurate past order data is available<br>
* The quality of the call depends heavily on the configured voice agent<br>
* Outputs like user intent and sentiment can be used to branch further flows (e.g., send payment link, escalate, or stop outreach)<br>
* Ideal for retention automation and lifecycle marketing flows rather than first-time engagement