Planned: integration not built yet

COD Order Confirmation Calls for Zoho Commerce

The Zoho Commerce integration is planned, not built yet. The aim: a COD sales order is created, we call the customer, they press 1 to confirm or 2 to cancel, and the sales order is confirmed or cancelled in Zoho Commerce. Request early access to be in the first group.

How it will work on Zoho Commerce

Planned design, based on Zoho Commerce sales order events and Zoho's OAuth API

Connect your Zoho account
Sign in with Zoho to authorise access to your organisation's sales orders.
Send sales order events
Sales order created and cancelled events go to your webhook URL, with a secret header we give you.
Customers get called
Hindi or English. Press 1 to confirm, 2 to cancel.
Sales order updated
The aim is to use Zoho Commerce's own confirm and cancel for sales orders.

What we expect to change in Zoho Commerce

Planned behaviour. The exact API calls will be confirmed when the integration is built.

Confirmed: sales order confirmed

The plan is to mark the sales order confirmed using Zoho Commerce's own confirm.

Cancelled: sales order cancelled

The plan is to cancel the sales order using Zoho Commerce's own cancel.

Unreachable: flagged

After the last retry, the order is flagged in your Edesy dashboard for your team.

Cancelled first: no call

A sales order cancelled before we call is skipped.

What a Zoho Commerce store will need

  • Zoho sign-in (OAuth) for your organisation. Zoho runs separate data centres (for example India and US), so we connect to the one your account lives in and keep the access refreshed.
  • Sales order webhooks for created and cancelled orders. Zoho doesn't document a signature for these, so we give you a secret header value to add and reject any request without it.

Still being verified

The exact Zoho Commerce API calls for confirming and cancelling a sales order, how COD orders are identified, and what the webhook payload contains still need checking against a live account. We won't promise specific behaviour until that's tested.

What every connection includes

The same calling engine runs behind every platform

Calling window and retries

Calling hours in IST, a delay after the order, retry gaps and when to give up.

Fresh check before dialling

The order is checked again just before the call. If it was already cancelled or confirmed, we don't call.

DND check

Numbers on your do-not-call list are skipped.

Hindi and English scripts

Edit the script as plain words. No call-flow builder needed.

Order timeline

Event received, call attempts, key pressed and what was written back, for every order.

Webhook replay

Every incoming store event is logged and can be replayed.

Confirmation call vs the alternatives

How each way of confirming a COD order compares in practice

Keypad callWhatsApp messageSMSIn-house calling team
Reaches customers without WhatsApp-
What the customer doesPresses 1 or 2 on the callTaps a button or repliesReplies or opens a linkTalks to an agent
Answer saved to your store automaticallyDepends on the toolDepends on the tool-
Keeps up with order spikesNeeds more callers
Can handle questions or address changes---
What you pay forCalls made, from a prepaid walletMessages sentSMS sentSalaries, phones and time

COD Confirmation for Zoho Commerce: FAQ

Want COD confirmation calls on Zoho Commerce?

Request early access and tell us your order volume. We'll contact you when Zoho Commerce is ready for pilot stores.