To schedule WhatsApp messages in India, use the WhatsApp Business API through a Business Solution Provider such as RichAutomate, where you pick a date and time in IST when you create a campaign and the platform sends it for you. The WhatsApp Business app has no native scheduler for broadcasts, and any scheduled message going to contacts who have not messaged you in the last 24 hours must be a Meta-approved template.
Picking 7 pm on a Friday is easy. Getting the message type, messaging limit, quiet hours and Meta's marketing-template pacing right is where most Indian businesses lose money or quality rating. This guide covers each piece in order.
Can you schedule WhatsApp messages at all? App vs API
Two very different products carry the WhatsApp Business name. The WhatsApp Business app is the free phone app that small shops run from a single handset. The WhatsApp Business Platform, usually called the API, is accessed through a provider and is built for sending at volume from software. Scheduling is one of the clearest dividing lines between them.
In the app, broadcast lists are capped at 256 contacts and only reach people who have saved your number in their phonebook. There is no dependable way to tell the app "send this list at 10 am tomorrow". Greeting and away messages can run automatically outside business hours, and Meta has been rolling out some newer marketing features inside the app gradually, but for recurring campaigns most owners still end up setting a phone alarm and pressing send by hand. Third-party "auto-sender" tools that automate the app break WhatsApp's terms and risk restriction.
The API works differently. Your campaign lives in a dashboard, you choose the template, the audience and the send time, and the platform queues the messages and dispatches them at that moment through Meta's Cloud API. Recipients do not need to have saved your number, although they must have opted in to hear from you.
| Capability | WhatsApp Business app | WhatsApp Business API (via RichAutomate) |
|---|---|---|
| Broadcast scheduling | No dependable native scheduler; manual send | Yes, pick date and time in IST per campaign |
| Audience per send | Broadcast list of up to 256 contacts | Governed by your messaging-limit tier |
| Who receives | Only contacts who saved your number | Any contact who has opted in |
| Reminders and drip sequences | Not supported | Supported through automation triggers and delays |
| Format for cold or late sends | Plain message | Meta-approved template required |
| Delivery reporting | Ticks in each chat | Sent, delivered, read and failed per recipient, with error codes |
How scheduling works on the WhatsApp Business API
Meta's Cloud API does not have a "send later" parameter. Scheduling is a feature of your provider: the platform stores your campaign, and a job queue releases the messages at the chosen time. Meta's checks (template status, messaging limit, per-user marketing limits, the 24-hour window) run at the moment of sending, not when you clicked schedule. A template that was approved on Monday but paused on Wednesday for low quality will fail when your Thursday campaign fires.
On a platform like RichAutomate the flow is short:
- Pick an approved template and fill its variables, such as the customer's first name or an order number.
- Choose the audience, ideally a tagged segment rather than your entire contact list.
- Set the date and time in IST, and confirm the timezone shown on screen before saving.
- Review the recipient count and estimated cost against your current messaging limit.
- Schedule, then read the delivery report after the send to see failures by error code.
Two habits save a lot of pain. First, use template variables for names, dates and order details instead of sending an identical block of text to everyone; generic copy tends to draw more blocks and reports. Second, invest time in segmenting your broadcast audience by city, purchase history or last activity, so a scheduled festival offer reaches people likely to care about it.
The 24-hour window: why scheduled free-form messages fail
This is the single most common scheduling mistake. When a customer messages you, a 24-hour customer service window opens. Inside that window you can reply with any free-form text, image or document. Outside it, the only thing Meta lets a business send is an approved template message.
Scheduling makes this easy to forget. Suppose a customer asks about a product at 8 pm and your team schedules a free-form follow-up for 10 am two days later. By then the window has closed and the message is rejected. The same happens when someone schedules a plain "Happy Diwali" text to the whole contact list: every recipient who has not written in during the past day fails. The fix is simple. Anything scheduled for later than the window, or aimed at contacts who have not recently messaged you, should be built as a template. Keep free-form sends for live replies and for automations that fire within minutes of an inbound message.
The window also shapes cost. Our guide to making the most of the 24-hour customer service window explains how to structure follow-ups so more of the conversation happens while the window is open.
Best times to send WhatsApp broadcasts in India (IST)
There is no universal best time. Indian audiences span working professionals, students, homemakers, shop owners and shift workers, and the right slot depends on who you are messaging and what you want them to do. What works reliably is to start with a sensible window for your vertical, send to a small segment, and compare read and reply rates before scaling up.
The table below lists practical starting points to test. They are drawn from common daily routines, not from a study, and they are not guaranteed to perform for your audience.
| Vertical | Starting windows to test (IST) | Why it can work |
|---|---|---|
| D2C, fashion, e-commerce | 12:30 to 2 pm; 7:30 to 9 pm | Lunch-break scrolling; relaxed evening browsing |
| Grocery and quick commerce | 7 to 9 am; 5 to 7 pm | Meal planning before the day starts and before dinner |
| Education and coaching | 6 to 8 pm; Sunday 10 am to 12 pm | After school or college; parents free on weekends |
| Clinics and diagnostics | Day-before reminder 6 to 7 pm; same-day 9 to 11 am | Time to plan travel and rearrange the day |
| Real estate | Saturday and Sunday 10 am to 1 pm; weekdays 7 to 8:30 pm | Site visits are usually planned for weekends |
| Financial services and insurance | Weekdays 10 am to 12 pm; around salary days | Office hours for queries; renewals and EMIs near payday |
| Restaurants and cloud kitchens | 11:30 am to 12:30 pm; 6 to 7:30 pm | Just before lunch and dinner decisions |
| B2B and SaaS | Tuesday to Thursday, 10:30 am to 12:30 pm | Inside working hours, away from Monday backlogs |
Calendar effects matter as much as the clock. The first week of the month, roughly the 1st to the 7th, is when many salaried customers have just been paid, which often suits EMI reminders, subscription renewals and higher-ticket offers. Festival seasons change behaviour sharply. During Navratri, Durga Puja and the run-up to Diwali, inboxes fill with offers from every brand, so a morning send the day before a sale can stand out more than a message at peak evening hours on the day itself. Regional festivals such as Onam, Pongal or Bihu suit regional audiences, ideally with a greeting in their language. Where payment is part of the message, a UPI payment link timed close to salary days removes a step between interest and purchase.
Scheduling reminders and drip sequences
Scheduled broadcasts are one-to-many sends at a fixed clock time. Reminders and drips are different: they are timed relative to an event for each contact, such as a booking, a sign-up or an abandoned cart. On the API these are built as automations with delays rather than as a single campaign.
Get a 1-minute BSP audit on WhatsApp
Drop your WhatsApp number — we line-item your current invoice against Meta India rates in under 60 seconds. India-hosted, DPDP-compliant.
Reminders
Appointment and payment reminders count as utility messages when they are genuinely transactional, which makes them cheaper than marketing messages and less exposed to marketing limits. A common pattern for clinics, salons and coaching centres is a confirmation at booking, a reminder the evening before, and a short nudge two to three hours ahead. Our playbook on appointment reminders that cut no-shows covers wording and timing in more detail. Keep the reminder strictly about the appointment; adding a promotional offer can lead Meta to categorise the template as marketing.
Drip sequences
A drip is a series such as a day-0 welcome, a day-2 how-to and a day-5 offer. Each step that lands outside the 24-hour window must be a template, and each marketing step counts toward per-user marketing limits. Build in an exit: when a contact replies, buys or asks to stop, remove them from the rest of the sequence. Few things damage quality rating faster than a customer who said "not interested" receiving three more scheduled offers.
Replies to scheduled campaigns often arrive in the evening or overnight. Rather than leaving them unanswered until morning, set up after-hours and holiday auto-replies that acknowledge the message and say when a person will respond. Because the customer wrote first, that reply sits inside the service window.
Quiet hours, time zones and festival etiquette
TRAI's rules on commercial communication and the DND registry were written mainly for SMS and voice calls, and WhatsApp runs on Meta's own opt-in and policy framework. Even so, Indian customers carry the same expectations across channels. As good practice, avoid scheduling promotional messages between roughly 9 pm and 9 am. A late-night offer is one of the fastest ways to earn a block or a spam report, and those signals feed straight into your quality rating.
Time zones matter even in a single-timezone country. If you have customers in the Gulf, Singapore, the UK or the US, a 10 am IST send reaches Dubai at 8:30 am but reaches New York in the middle of the night. Segment international contacts by country code and schedule them separately. Also confirm that the scheduling screen is set to IST rather than a server default; a campaign meant for 7 pm that goes out at 1:30 am because of a UTC setting is an avoidable error.
During festivals, lighter is usually better. One well-timed greeting with a useful offer beats a burst of daily messages across all nine nights of Navratri. On days of mourning or major national events, pause scheduled promotions and review them before they fire.
How scheduling interacts with Meta pacing, 131049 and messaging limits
Scheduling decides when your platform hands messages to Meta. Meta then decides what happens next, and three mechanisms are worth understanding before you plan a large send.
Marketing template pacing
When a new or recently edited marketing template goes out to a large audience, Meta may release it in stages, sending to an initial slice and holding the rest while it watches early feedback. If people block or report, the remaining messages may not go out. For scheduled sends, this means a campaign can finish well after the start time you chose. Read our explainer on Meta marketing template pacing before scheduling a big festival blast with a template nobody has seen yet; testing it on a smaller warm segment a few days earlier is sensible.
Error 131049 and per-user marketing limits
Meta also limits how many marketing messages an individual WhatsApp user receives from businesses over a period, to protect the overall experience. When a message is held back for this reason, the delivery report shows error 131049. It is not a fault in your campaign, and retrying the same message immediately rarely helps. The practical response is to send fewer, better-targeted marketing messages, prioritise contacts who have engaged recently, and avoid piling into the busiest peak slots. Scheduling to engaged segments can reduce how often you see it, but no setting removes it.
Messaging-limit tiers
Your business also has a messaging limit: the number of unique customers you can start conversations with in a rolling 24-hour period. New accounts begin at a low tier and move up as they send consistently with good quality. Our guide to WhatsApp messaging limit tiers explains how accounts move between tiers. For scheduling, the rule is to keep any single day's scheduled volume below your current limit, including reminders and drips that fire on the same day. Schedule a 5,000-contact campaign on an account limited to 2,000 unique users a day and the excess will fail, and a high failure rate is not a signal you want to send.
Quality rating ties all of this together. It reflects how recipients respond, including blocks and reports, and a low rating can pause templates or hold back tier upgrades. No provider can promise that an account will never be restricted or that every message will be delivered; what you control is relevance, frequency and timing.
What a scheduled broadcast costs
Scheduling itself carries no extra charge on RichAutomate; you pay for the messages sent. There is ₹0 setup and ₹0 monthly fee on pay-as-you-go, with two billing modes. With Client Pay, RichAutomate charges a ₹0.10 platform fee per message and Meta's own charges are billed to your Meta payment method. With SaaS Pay, you pay RichAutomate an all-inclusive ₹1.20 per marketing message or ₹0.30 per utility message.
| Message type | When it can be sent | Typical scheduled use | SaaS Pay | Client Pay |
|---|---|---|---|---|
| Marketing template | Any time, to opted-in contacts | Offers, festival greetings, launches, win-back | ₹1.20 per message, all-inclusive | ₹0.10 platform fee plus Meta charges |
| Utility template | Any time, tied to a transaction or account event | Appointment, payment and renewal reminders, order updates | ₹0.30 per message, all-inclusive | ₹0.10 platform fee plus Meta charges |
| Free-form message | Only inside the 24-hour customer service window | Live replies and follow-ups minutes after an inbound message | Not usable for cold scheduled sends; see pricing page | Not usable for cold scheduled sends; see pricing page |
Some illustrative arithmetic: a scheduled festival campaign to 10,000 opted-in contacts on SaaS Pay costs 10,000 x ₹1.20 = ₹12,000 for marketing templates. The same volume of utility reminders comes to 10,000 x ₹0.30 = ₹3,000. On Client Pay, the RichAutomate platform fee for 10,000 messages is ₹1,000, with Meta's per-message charges billed separately to your own Meta account. Meta rates can change, so check the current figures on the RichAutomate pricing page before budgeting a large campaign.
A pre-send checklist for scheduled campaigns
Before any scheduled campaign fires, run a short check. It takes a few minutes and catches most of the problems described above.
- The template is approved and still active, in the right category, with variables filled for every recipient.
- The audience is opted in, segmented, and excludes anyone who asked to stop.
- The send time is set in IST, outside roughly 9 pm to 9 am for promotions, and not exactly on the hour.
- The day's total scheduled volume, including drips and reminders, sits below your messaging limit.
- Any new marketing template has been tested on a small warm segment first.
- A person or an auto-reply is ready to handle responses as they arrive.
After the send, open the delivery report the same day. A spike in one error code tells you more than overall read rates: 131049 points to marketing frequency, template errors point to approval or variable issues, and limit errors point to scheduling too much in one day.
Ready to stop setting phone alarms for broadcasts? Start free with RichAutomate with ₹0 setup and ₹0 monthly on pay-as-you-go, and schedule your first template campaign in IST in a few minutes.