Which category should I submit this under?+
Utility. It confirms an order the customer has already placed and is tied to a specific action, which is the definition of a transactional utility template. Adding any promotional or discount language would reclassify it as marketing and likely get it rejected.
Does a COD confirmation still need opt-in?+
Yes. Consent and opt-in still apply to utility and authentication templates, not just marketing. Utility simply means the message is tied to a real transaction — it does not remove the requirement to have a lawful basis and the customer's number on a valid basis for messaging.
Can I edit the wording?+
Yes, as long as you stay within the utility category rules — keep it informational and transactional, with no offers or upsell. Any edit creates effectively a new template, so re-submit it for approval before sending.
How soon after order placement should it go out?+
Within a few minutes, ideally triggered automatically on order creation. The faster you ask for confirmation, the fresher the buyer's intent and the lower your cancellation and return-to-origin rate.
How does adding a Pay now button help with COD?+
It gives the customer a one-tap way to prepay at the exact moment they're most engaged, converting a high-risk cash-on-delivery order into a paid one. That removes the RTO risk entirely for anyone who chooses to prepay.
What does it cost to send?+
Each delivered message is billed at the utility rate under Meta's per-delivered-message model (in effect since 1 July 2025). With InfiQ you pay transparent ₹ pricing built on Meta's live utility rate card, ex-GST. The 24-hour service window that opens on a customer reply is for follow-up support messages, charged from 1 October 2026.
How fast can I go live?+
Once you submit the template it usually clears Meta's review within a day. After approval you can send it instantly through InfiQ, triggered from your order system.
Can I send it in Hindi or another language?+
Yes. Create a separate language clone rather than mixing scripts in one template, keep it inside the utility rules, and submit each language version for its own approval.