COD Confirmation & NDR Calling AI India: ₹2/min

The current implementation has three event-driven outbound flows and one inbound lookup. They all require a configured connector for that business.

Shopify documents webhooks as event notifications and uses `orders/create` as its worked example. Its current webhook topic list includes `orders/create`, `orders/cancelled`, `checkouts/create` and `checkouts/update`. Shiprocket defines an NDR as a shipment the courier could not deliver and exposes reattempt, contact-buyer and RTO actions in its NDR panel. These official platform definitions explain the triggers; the Dvaarik behaviour in the table comes from the current backend and its connector tests.

A configured Shopify connector receives the order event, verifies the webhook signature and checks the merchant's configured COD gateway label. A prepaid order is ignored. An old replayed order is ignored rather than treated as a new customer request.

For a fresh COD order, Dvaarik extracts only the facts needed for the campaign: order number, item summary, amount payable, delivery city/address and the Shopify order identifier. The call enters the same outbound machinery used by a normal campaign, including the business calling window, credit guard, callee fence and durable scheduled-call sweep.

Two separate duplicate controls matter. Shopify can retry a delivery with the same webhook ID, and a store can accidentally deliver the same order through two subscriptions. Dvaarik fences both the webhook delivery and the underlying order identifier, so neither case should mint a second confirmation call.

The confirmation outcome remains on the campaign record for the merchant's team. The agent does not edit the Shopify order after the call unless a separate write-back integration has been explicitly scoped.

When Shiprocket pushes an undelivered shipment, Dvaarik reads the AWB, courier, status activity and channel order reference. Shiprocket's event does not supply the customer phone needed by this implementation, so Dvaarik looks up the exact order reference in that business's connected Shopify store. A fuzzy or missing match is skipped; it must not call a different customer whose order number merely looks similar.

The first qualifying event creates one call for that AWB. A second undelivered scan for the same AWB is ignored, because repeating the same conversation for every courier reattempt would waste credits and annoy the buyer.

The agent can ask whether the buyer wants a reattempt, needs an address correction or no longer wants the parcel. The result is captured on the campaign board. It is not automatically sent back to Shiprocket today. Shiprocket's own NDR processing guide requires the seller to submit the corrected contact/address, reattempt date, evidence or RTO choice in its panel; that human courier-side step remains visible here rather than being disguised as automation.

Shopify does not publish an `abandoned checkout` event. The configured flow starts from checkout create/update events after contact information exists, then waits for the merchant's chosen delay. Updates refresh the same checkout record instead of creating another lead.

Immediately before dialling, Dvaarik asks Shopify whether an order now carries that checkout token. If the purchase completed, the recovery call is blocked. If Shopify cannot answer, the lead is parked and retried a bounded number of times rather than risking a sales call to someone who already paid. A cancelled or completed order also closes the pending call.

There is no universal “call in 60 seconds” promise. The delay is configured per merchant, and the safe moment depends on checkout behaviour, calling hours and the business's own consent/compliance decision.

Dvaarik direct voice starts with Bharat Essential at ₹2 per whole billed minute. Essential supports 10 languages: English, Hindi, Tamil, Kannada, Malayalam, Marathi, Gujarati, Bengali, Punjabi and Urdu. Telugu and the full 23-language surface start on Bharat Standard at ₹3/min; do not combine “₹2” and “all Indian languages” as if they were one grade.

Use billed minutes, not order count, as the input:

The table is scenario arithmetic, not a measured customer result. Replace the assumed durations and event counts with your own call logs. A 40-second connected call still bills one whole minute. A phone channel/carrier arrangement, implementation work and any connected social channel are separate from this voice-usage table; the pricing page is the current public direct-rate reference.

Store-connector onboarding is assisted today. The business dashboard does not yet expose a self-serve Shopify or Shiprocket connector screen.

Before calls can run, the business needs:

1. a per-business Shopify connector with the store domain, Admin API access token and webhook secret;
2. Shopify webhook subscriptions for the events the merchant chooses;
3. a per-business Shiprocket webhook secret for NDR calls;
4. one outbound campaign per enabled event, with the questions and result fields the merchant wants;
5. outbound calling enabled, a funded voice balance and a working phone channel;
6. a customer phone that passes the Indian-mobile dialability check; and
7. an operating process for a human to review the campaign result and update Shopify or Shiprocket where required.

The current store connector is Shopify-specific. Other storefront, OMS, courier-panel or spreadsheet read/write integrations can be scoped only after the exact system and write actions are verified.

Do not use an order-support workflow as permission to call an unrelated list. These connectors act on the merchant's own order or delivery events; bought, rented or scraped lists do not belong in this flow.

TRAI's current UCC definition excludes transactional and service voice calls, while still placing commercial communications inside a registered-sender and access-provider framework. The exact classification depends on the call's purpose and content. A COD or delivery-problem call should stay limited to that order. An abandoned-checkout recovery pitch can cross into promotional content and needs the merchant's compliance review, customer preference handling and carrier-approved setup.

The primary regulatory reference is TRAI's 2025 amendment to the Telecom Commercial Communications Customer Preference Regulations. This page describes product controls, not legal advice.