> 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/cod-order-verification-call.md). # COD Order Verification Call Action Node · AI Voice COD Verification ### What It Does This node initiates an automated AI-powered phone call to verify a Cash on Delivery (COD) order. During the call, the AI voice agent interacts conversationally with the customer to confirm or cancel the order based on the workflow configuration. This helps businesses validate COD orders before fulfillment and significantly reduce RTO (Return to Origin) rates caused by fake or accidental orders. *** ### Example A customer places a COD order for shoes worth ₹2,499. The workflow triggers this node immediately after order placement. The AI voice agent calls the customer and says: > “Hi Rahul, this is a confirmation call for your recent order containing Running Shoes worth ₹2,499. Would you like to confirm this order?” Based on the customer response: * The order can be confirmed * The order can be canceled * The conversation can be escalated to a human agent *** ## When to Use This Node Use this node when: 1. You want to verify COD orders before fulfillment 2. You need to reduce fake orders and RTO losses 3. You prefer voice-based verification over WhatsApp-only confirmation 4. You want to capture customer intent automatically through AI calls 5. You need automated order confirmation or cancellation workflows *** ## Requirements Before configuring this node: * LimeChat Voice AI must already be configured * Valid customer phone number data should be available * Order details should exist in the workflow event * Voice agents must be created and active *** ## Supported Events This node supports: 1. All Events *** ## Setting It Up ### Inputs | Input | Type | Required | Description | | ------------------ | ------------------------- | ------------------- | -------------------------------------------------------------------------- | | Order ID | Event Field (Dynamic) | No | Unique identifier of the order being verified | | CRM Inbox | Dropdown (Server-Fetched) | No | Inbox where call logs and conversation tracking will be maintained | | Item Names | Event Field (Text) | Yes | Names of items included in the order | | Order Value | Event Field (Text/Number) | No | Total order value referenced during the call | | Voice Agent | Dropdown (Server-Fetched) | Yes | AI voice agent responsible for conducting the verification call | | Custom Prompt | Text | No | Custom instructions or script for the AI voice agent | | Customer Name | Event Field (Text) | No | Customer name used for personalization | | Discount Percent | Number | No | Discount offered on the order, if applicable | | Cancellation Tags | List (Text Array) | No | Tags applied if the customer cancels the order | | Confirmation Tags | List (Text Array) | No | Tags applied if the customer confirms the order | | Allow Cancellation | Boolean (True/False) | No (Default: False) | Controls whether customers are allowed to cancel the order during the call | *** ## Input Field Details ### Order ID Dynamic order identifier passed from the workflow trigger. #### Example * ORD12345 * \#54892 *** ### CRM Inbox Optional inbox used for tracking call activity and conversation logs. The list is dynamically fetched and may include a refresh option. *** ### Item Names Names of products included in the order. These are referenced by the AI agent during the conversation. #### Example * Running Shoes * Bluetooth Speaker *** ### Order Value Total order amount used for contextual communication during the call. #### Example * ₹2,499 * ₹999 *** ### Voice Agent Select the AI voice agent responsible for handling the verification call. The available agents are fetched dynamically from configured voice agents. *** ### Custom Prompt Additional instructions that guide the AI agent’s tone, flow, and conversational behavior. Supports dynamic variables. #### Example You are a polite order verification assistant. Confirm whether the customer wants to proceed with their COD order. Mention the ordered items naturally and avoid sounding robotic. *** ### Customer Name Used for personalization during the call. #### Example * Rahul * Priya *** ### Discount Percent Optional discount communicated during the verification process. #### Example * 10 * 15 *** ### Cancellation Tags Tags automatically applied if the customer cancels the order. #### Example * cod\_cancelled * high\_risk\_customer *** ### Confirmation Tags Tags automatically applied if the customer confirms the order. #### Example * cod\_verified * ready\_for\_shipping *** ### Allow Cancellation Controls whether the AI agent can process order cancellation requests during the call. | Value | Behavior | | ----- | ---------------------------------------- | | True | Customer can confirm or cancel the order | | False | Agent only attempts order confirmation | *** ## Outputs | Output | Type | Description | | ------------------------ | ------- | -------------------------------------------------------------- | | successful | Boolean | Indicates whether the call was successfully initiated | | call\_id | Text | Unique identifier of the verification call | | call\_status | Text | Status of the call (completed, failed, busy, unanswered, etc.) | | user\_confirmed | Boolean | Indicates whether the customer confirmed the order | | user\_requested\_handoff | Boolean | Indicates whether the customer requested human support | | call\_summary | Text | Summary of the conversation between customer and AI agent | | cod\_verification\_call | Object | Structured call interaction data for advanced workflows | *** ## Output Behavior | Output | Meaning | Recommended Next Step | | ------------------------------- | -------------------------------- | ------------------------------------ | | user\_confirmed = true | Customer confirmed the order | Proceed with fulfillment | | user\_confirmed = false | Order not confirmed | Retry or flag for review | | user\_requested\_handoff = true | Customer requested agent support | Route to human agent | | call\_status = failed | Call could not be completed | Retry call or send WhatsApp fallback | *** ## What Happens After It Runs Once executed: * The AI voice agent initiates a verification call * Customer responses are captured conversationally * Confirmation or cancellation outcomes are recorded * Tags and workflow actions can be triggered automatically * The workflow can proceed toward fulfillment, cancellation, or escalation *** ## Best Practices Pass accurate item names and order values for natural conversations. Keep voice prompts short, conversational, and human-like. Use confirmation and cancellation tags for downstream automation. Combine with: * Order fulfillment workflows * Fraud prevention logic * Agent escalation flows * CRM tagging Retry failed or unanswered calls using fallback WhatsApp reminders. *** ## Key Reminders 1. LimeChat Voice AI setup is mandatory 2. Works across all workflow events 3. Accurate order data improves call quality and verification success 4. `user_confirmed` output can drive fulfillment automation 5. `user_requested_handoff` can trigger agent escalation workflows 6. If Allow Cancellation is disabled, the AI agent will only seek confirmation 7. Tags can automatically categorize confirmed or canceled orders 8. This node enables voice-based automation within WhatsApp journeys