DEV Community: botsense seo

5 Ways Rajkot Manufacturers and Retailers Can Use WhatsApp API in 2026

botsense seo — Thu, 22 Oct 2026 12:45:53 +0000

Rajkot is home to one of India's largest auto parts manufacturing clusters at Aji GIDC, a globally recognized jewelry industry, and a thriving engineering and retail sector. In 2026, WhatsApp API has become the communication backbone for B2B and B2C businesses in the city. Here are five ways Rajkot businesses are using it.

1. Automate dealer price list distribution

Rajkot auto parts manufacturers at Aji GIDC use WhatsApp API for dealer management — sending updated price lists instantly to their entire dealer network. Read receipts confirm delivery, and replies route into a shared team inbox, eliminating scattered personal phone conversations. WhatsApp API Rajkot plans start at ₹24,999 per year with the Starter plan covering up to 10,000 contacts.

2. Send dispatch and shipment alerts via WhatsApp instead of SMS

Shipment notifications via SMS have low reliability and no read confirmation. WhatsApp API allows Rajkot manufacturers to send structured dispatch alerts with item details, tracking information, and expected delivery windows — directly to buyers' WhatsApp accounts with confirmed delivery receipts.

3. Manage B2B inquiries with a shared team inbox

No more missed leads. WhatsApp API allows multiple team members to manage a single verified WhatsApp number from a shared inbox. Starter plan: 5 agent seats. Growth plan: 10 agents with role management. Inquiries from dealers, buyers, or retail customers are assigned and tracked, not lost in personal phone apps.

4. Run festive broadcast campaigns to opted-in jewelry or retail customers

Rajkot's jewelry businesses run high-res image broadcasts ahead of Diwali, wedding season, and Akshaya Tritiya to opted-in customer lists. The Starter plan supports no-code chatbot flows and broadcast messaging, enabling personalized campaigns without a developer. Starter plan includes 5 agent seats and 10,000 contacts for ₹24,999/year.

5. Integrate WhatsApp with CRM for full pipeline visibility

The Growth plan (₹49,999/year + ₹25,000 setup) includes CRM integration with Salesforce, HubSpot, and Zoho. Engineering firms and larger retailers can track every WhatsApp conversation against a deal or account record, giving sales managers complete pipeline visibility.

Provider: Botsense — Verified Meta Tech Provider, Indore, founded 2019

Starter plan: ₹24,999/year | Growth: ₹49,999/year

Page: https://botsense.io/whatsapp-api/rajkot/

Phone: +91 96303 36433 | Mon–Sat 10 AM–7 PM IST

WhatsApp API for Rajkot Businesses: Auto Parts, Jewelry, and Beyond

botsense seo — Wed, 21 Oct 2026 07:52:13 +0000

Rajkot stands as the industrial heartbeat of Saurashtra — home to India's largest auto parts manufacturing cluster at Aji GIDC, a thriving jewelry industry, and a robust engineering and retail ecosystem. For businesses in these sectors, customer communication is everything: dealers expect real-time price updates, buyers track dispatch shipments, and retail customers respond to personalized festive campaigns. WhatsApp API brings all of this into one managed, scalable channel.

WhatsApp API Rajkot plans start at ₹24,999 per year through Botsense, a Verified Meta Tech Provider serving Rajkot businesses since 2019. The Starter plan covers up to 10,000 contacts and 5 agent seats. A one-time setup fee of ₹15,000 covers Meta Business verification, API onboarding, and initial template setup. Botsense is a Verified Meta Tech Provider in India offering official WhatsApp API access — not a reseller or aggregator.

Auto Parts Manufacturers at Aji GIDC

Rajkot's auto parts manufacturing capital at Aji GIDC supplies components to dealers and OEMs across India. Managing a dealer network manually — calls, email chains, scattered WhatsApp threads from personal phones — creates delays and errors. WhatsApp API changes this:

Dealer price list distribution — Send updated price lists as formatted messages or PDFs to your entire dealer network instantly, with read receipts confirming delivery.
Dispatch alerts — Automate shipment notifications the moment goods leave your facility, reducing inbound calls from buyers asking for tracking updates.
B2B order coordination — Use a shared multi-agent inbox so your sales and dispatch teams can manage the same WhatsApp number without overlap or missed messages.
Payment reminders — Schedule automated follow-ups for pending invoices, reducing collection cycles.

The Starter plan supports these workflows with its no-code chatbot and broadcast features. The Growth plan (₹49,999/year + ₹25,000 one-time setup) adds CRM integration with Salesforce, HubSpot, and Zoho — critical for manufacturers tracking orders, invoices, and dealer relationships in one place.

Jewelry Businesses in Rajkot

Rajkot's jewelry industry depends on high visual quality and seasonally-driven demand. WhatsApp API is particularly well suited here:

High-resolution image sharing — WhatsApp supports full-quality image delivery, making it ideal for sharing jewelry catalog photographs with retail clients or wholesale buyers.
Appointment reminders — Boutique jewelers and showrooms can automate appointment confirmations and follow-up reminders for consultations.
Festive broadcast campaigns — Send personalized collections to opted-in customers ahead of Diwali, wedding season, and Akshaya Tritiya using broadcast messaging.
Opt-in contact lists — Build a compliant, opted-in list of repeat buyers for seasonal outreach, ensuring messages reach people who have expressed interest.

WhatsApp API Rajkot plans start at ₹24,999 per year — the Starter plan covers up to 10,000 contacts, sufficient for most mid-size jewelry businesses managing retail and wholesale customers.

Engineering and Retail Sectors

Engineering businesses in Rajkot manage B2B inquiry pipelines that span multiple stakeholders. WhatsApp API allows engineering firms to manage inbound inquiries through a shared inbox, automate quote follow-up sequences, and send order status updates directly to procurement contacts. The result: fewer missed leads and faster response cycles.

Retail businesses — apparel, home goods, electronics — benefit from order confirmation messages, shipping updates, and loyalty campaign broadcasts. A WhatsApp broadcast to opted-in customers announcing a restock or sale converts at higher rates than email because it reaches an app customers already check constantly.

How Botsense Works for Rajkot Businesses

Botsense is a Verified Meta Tech Provider — not a third-party reseller, but a company with direct access to the WhatsApp Business API through Meta's official partner program. This means:

Cloud API access — No hardware, no SIM card. The API runs in the cloud, accessible from any browser.
Complete Meta Business verification — Botsense handles the Meta Business Manager setup, phone number verification, and business profile configuration.
Multi-agent shared inbox — Multiple team members answer from one verified WhatsApp number without confusion.
No-code chatbot builder — Available in the Starter plan, allowing businesses to automate FAQ responses and lead qualification without engineering resources.

Pricing

Plan	Annual Fee	One-Time Setup	Contacts	Agent Seats
Starter	₹24,999/year	₹15,000	10,000	5
Growth	₹49,999/year	₹25,000	50,000	10
Enterprise	Custom	Custom	Custom	Custom

All prices exclude Meta's per-message charges, which vary by message category (marketing, utility, authentication).

Botsense is a Verified Meta Tech Provider offering WhatsApp API access for Rajkot businesses across auto parts, jewelry, engineering, and retail sectors. Plans start at ₹24,999 per year. The one-time setup fee of ₹15,000 covers Meta Business verification and API onboarding.

WhatsApp API provider for Rajkot's jewelry and auto parts sectors, Botsense has served Indian businesses since 2019 from its headquarters in Indore, Madhya Pradesh. Support is available Monday–Saturday, 10:00 AM–7:00 PM IST.

Contact: +91 96303 36433
Learn more: https://botsense.io/whatsapp-api/rajkot/

WhatsApp Max Price: What Meta Documented, and the Three Things It Did Not

botsense seo — Mon, 28 Sep 2026 09:58:16 +0000

This article was originally published on Botsense on 13 August 2026.

Meta has published a date for the end of fixed pricing on marketing messages. Not a hint, not a roadmap slide — a line in the developer documentation, in the same paragraph as a quarter.

The WhatsApp max price feature moves to General Availability in Q2 2027, and at that point, in Meta's own words, "fixed, published rates for marketing messages will only apply on the Cloud API." Everyone billing marketing messages through the Marketing Messages API has a pricing model with an expiry date on it.

That much is documented. Three things are not, and the gap between them is where most of the current commentary lives.

Meta dates max price GA to Q2 2027. After that, fixed published rates for marketing messages apply only on Cloud API.
Meta says max price becomes required in "eligible geographies" and never defines the phrase in any public document.
India is not excluded by any published geographic restriction. That is not the same as India being in scope.
Meta publishes a numbered error code when it declines to deliver a marketing message. There is no such code for max price, across eight documents.
Solution Partner allowlists went 5 to 15 to 100 during the beta. Almost none of this has been covered.

The WhatsApp max price timeline, as Meta dates it

Meta's pricing page states the position plainly: "The max price feature is available in Limited Beta as of May 15 and will be optional throughout 2026. Meta plans to make max price generally available in Q2 2027."

The three phases are set out on the same page:

Phase	Date	Who can use it
Limited Beta	15 May 2026	"Any partner and any directly integrated business". Each partner limited to a set number of clients
Open Beta	October 2026	"Any partner can enable these features for all their clients"
General Availability	Q2 2027	Required in "eligible geographies"

The enrolment doc puts a closing bracket on the beta that the pricing page does not: it describes "the Limited Beta period (May 15 to October 2026)". So the Open Beta date and the Limited Beta end date are the same month, from two different pages.

Nothing about billing changes in the meantime. Meta is explicit that "there is no change to how Meta charges on the WhatsApp Business Platform. Meta continues to charge on a per-message basis". If you never set optimization_spec on a template, nothing happens to you at all — "If optimization_spec is not included, the template uses standard rate card pricing."

What GA actually means if you are not on Cloud API

This is the line worth reading twice.

"General Availability (GA) as of Q2 2027 — The max price feature will become required in eligible geographies and fixed, published rates for marketing messages will only apply on the Cloud API." — Set a max price for marketing messages, Meta for Developers, retrieved 11 August 2026

Two commitments in one sentence. The WhatsApp max price stops being optional somewhere, and the familiar per-category rate card survives somewhere else — on Cloud API. For anyone whose marketing volume runs through the Marketing Messages API, the fixed rate is a 2026 arrangement. Which API your traffic actually sits on is an account-architecture question, and if you are not certain, the account model change is the place to start.

The word doing the most work is "eligible". Meta does not define it.

I checked five documents: Set a max price for marketing messages; Enroll in the max price feature; Control max price visibility in WhatsApp Manager; Marketing Messages API changelog; Marketing Messages get-started, which carries the geographic availability table.

The phrase "eligible geographies" occurs exactly once across all five — in the GA sentence above. No list, no link, no table.

One source could contradict this and could not be read: the "Max price explainer PDF" linked from the pricing page. It sits on Meta's Highspot instance behind both a browser gate and a sign-in wall. If a list of eligible geographies exists anywhere, that is the likeliest place for it, and it is not public.

India is not named in any published restriction group. That means India is eligible to use the Marketing Messages API. It does not mean India is in scope for the GA requirement. Those are two different statements about two different lists, and only one of those lists has been published.

What Meta says the WhatsApp max price does

Meta describes the feature by objective, not by mechanism. A max price can be set "the same as, lower than, or higher than the published rate", and the page attaches an outcome to each: setting at published rates to lower costs "while maintaining delivery rates similar to current WhatsApp campaigns"; setting below to "Reach more customer cohorts on WhatsApp at lower cost"; setting above to "Increase delivery rates during periods such as holidays and peak sales periods".

The charging rule itself is one clause: "when a max price is set, Meta will charge that max price or lower for delivery."

The Reach Estimation API is the only place Meta puts numbers on the trade-off. Its own example response, at a targeted audience fixed at 1,000 users:

bid_amount	Targeted users	Estimated deliveries
400	1,000	500–570
520	1,000	600–650

Raising the bid from 400 to 520 — thirty per cent more — moves the estimated delivery range from just over half the targeted audience to just under two thirds. Meta caveats it directly: "Meta generates estimates from historical data, and they are for informational and planning purposes only."

Read those two rows carefully and you will notice what they concede. At a bid_amount of 400, between 430 and 500 of the 1,000 targeted users do not receive the message.

What Meta never says

Meta does not say what happens to those messages.

I searched nineteen terms across eight public documents: auction, clearing price, clearing, market rate, market price, demand, competing, competition, bid against, outbid, win the, lose the, second price, not sent, undelivered, not be delivered, fails to deliver, dropped, skipped. Zero occurrences, all nineteen, in all eight.

That absence carries more weight than a word count, because Meta plainly has a way of saying this when it wants to. Error 131049 reads "This message was not delivered to maintain healthy ecosystem engagement." Error 130472 reads "Message was not sent as part of an experiment." Both describe a marketing message Meta decided not to deliver; both get a number, a published description and a row in the error code reference, where 69 codes are documented and not one mentions price, bid or budget.

Meta issues a numbered, published error code when it declines to deliver a marketing message. It has not issued one for max price.

One distinction worth stating: this shows Meta has not documented the outcome, not that no mechanism exists. Something is clearly deciding — the estimated delivery range moves with the bid, so a decision is being made per message. What is missing is any published account of what that decision is, or what becomes of the messages it goes against.

The Solution Partner controls nobody is reading

Meta shipped a partner-facing control surface for the WhatsApp max price through the beta, and it has gone almost entirely uncovered.

The allowlist cap moved twice. The changelog records the 17 June increase from 5 to 15, and then on 31 July: "Solution Partners can now allowlist up to 100 end-businesses for the max price feature during the Limited Beta period, increased from 15."

On 5 August, Meta added a visibility switch. The whatsapp_manager_marketing_messages_max_price_enroll_status field on the WhatsApp Business Account takes OPT_IN or OPT_OUT.

"This setting controls only the visibility of the max price experience in WhatsApp Manager. It doesn't change a WABA's eligibility for max price, and it doesn't affect max price settings configured through the API." — Control max price visibility in WhatsApp Manager, Meta for Developers, retrieved 11 August 2026

So it hides a UI. It does not gate the capability, and an end-business with API access is unaffected by it.

One more route worth knowing: since 17 July, an approved template can be cloned at a different max price by passing source_template_id, and "The duplicate is created in APPROVED status without re-review."

What to do with an undefined scope

The honest summary is short. Meta has committed to a date and a consequence, and has not published the list of places the consequence applies to. If you sell or buy WhatsApp marketing in India, you are entitled to know whether Q2 2027 changes your rate card, and as of today Meta's public documentation does not tell you.

Four things you can act on:

Decide whether your marketing volume runs through Marketing Messages API or Cloud API, because Q2 2027 treats them differently.
If you are a Solution Partner, check your allowlist headroom against the 100 cap before Open Beta in October.
Read whatsapp_manager_marketing_messages_max_price_enroll_status as a UI switch, not an access control.
Do not commit to a max price strategy on savings percentages that carry no link to Meta.

Read the full analysis with sources at botsense.io

Meta Business Agent needs two webhook fields WhatsApp does not list

botsense seo — Sat, 05 Sep 2026 07:39:52 +0000

Meta Business Agent will not deliver you a usable record of its conversations unless your app subscribes to the standby webhook and to messaging_handovers.

Neither field appears in WhatsApp's own webhook field reference, which lists nineteen fields and was last updated on 29 April 2026.

Both are documented, but under Messenger Platform, in Messenger vocabulary: page objects, Page IDs, PSIDs and postbacks. None of those exist on WhatsApp.

Meta's WhatsApp changelog records Standby Webhooks documentation being added on 4 August 2026. The field list was not updated to match.

The failure is silent. The agent still answers your customer. You simply stop receiving the conversation.

Meta Business Agent lets a business run an AI agent that answers WhatsApp conversations autonomously. Meta names thread control among its capabilities, describing it as managing handoffs between the AI agent and human agents.

What the standby webhook does, and why you need it

The standby webhook field receives traffic for conversations the Meta Business Agent is handling. When the agent becomes the primary responder for a conversation, that conversation's messages stop arriving on the messages field your existing integration subscribes to. They arrive on standby instead. Without that subscription, the conversation happens and no record of it reaches your application.

If you have not subscribed to that field, nothing errors. Your endpoint stays healthy, your existing messages subscription keeps working for everything else, and the agent keeps answering your customers correctly. What you lose is the record. The conversation happens and you receive none of it.

That is the shape worth naming: not a crash, not a rejected request, just an absence that looks exactly like a quiet day.

Where the standby webhook is actually documented

Meta's WhatsApp webhook reference has a Fields table listing nineteen fields, from account_alerts through user_preferences. standby is not one of them. Neither is messaging_handovers.

WhatsApp's webhook field reference lists nineteen fields: account_alerts, account_review_update, account_update, business_capability_update, flows, message_template_quality_update, message_template_status_update, messages, phone_number_name_update, phone_number_quality_update, security, template_category_update, user_preferences, and others through to the full nineteen. standby and messaging_handovers are not among them. The list was last updated 29 April 2026.

Both fields do have reference documentation. It sits under Messenger Platform.

Field	Where documented	Last updated
`standby`	Messenger Platform webhook events	25 September 2024
`messaging_handovers`	Messenger Platform webhook events	14 September 2021
WhatsApp webhook Fields table	WhatsApp Business Platform	29 April 2026

The dates are the interesting part. WhatsApp's field list is the most recently maintained of the three, and it is the one that omits them.

The documentation you are sent to is about something else

The standby webhook reference sits under Messenger Platform, not WhatsApp Business Platform. It describes a callback that fires when a message is sent to a page while your application is not the current thread owner. The example payload opens with "object":"page" and carries a PAGE_ID. Postbacks, PSIDs, and page objects appear throughout. None of those exist on WhatsApp, which uses "object":"whatsapp_business_account" and routes on a phone number ID. You are expected to read a Messenger reference and translate it into WhatsApp terms.

The messaging_handovers reference is older still, dating to 2021, and documents pass_thread_control and take_thread_control events carrying previous_owner_app_id and new_owner_app_id.

This is not a claim that standby is undocumented or that Meta Business Agent is broken. The feature works, Meta added Standby Webhooks documentation for WhatsApp on 4 August 2026, and providers who have implemented it handle these fields on your behalf. The gap is narrower: the canonical WhatsApp field list does not name either field, and the reference documentation they are pointed to was written for a different product.

Why the documentation lives where it does

The handover protocol Meta Business Agent uses is not specific to WhatsApp. It is the thread control mechanism Messenger has used since 2021 for two applications sharing a conversation: one holds the thread, the other watches on standby, and pass_thread_control and take_thread_control transfer ownership between them. Meta reused that protocol rather than building a new one. The documentation predates the WhatsApp feature.

The consequence for a reader: if you are implementing against WhatsApp, the authoritative description of two fields you need is written in terms of a product you are not using, and the field list for the product you are using does not mention them.

What messaging_handovers carries, and why you need it separately

messaging_handovers is the webhook field that fires when thread control changes — when the Meta Business Agent takes over a conversation or when your application takes it back. It carries the application that previously owned the thread and the one that owns it now. Without it, you can reconstruct a transcript but not the custody chain — which application was responsible at which moment.

Treat the two as a pair. One is the content, the other is the timeline.

What to check before you enable the agent

Confirm your app is subscribed to standby and messaging_handovers, not only messages. The App Dashboard configuration panel is where subscriptions are managed, and the absence of a field from the published list does not mean it cannot be selected.

Test the failure rather than assuming it. Enable the agent, have a colleague message the number, and confirm the exchange actually arrives at your endpoint.

The pattern, not just this instance

We have documented several gaps of this kind in Meta's platform documentation, and they share a shape. A mechanism is specified completely somewhere, and the one page a reader would consult does not point at it.

When a feature depends on something you cannot find in the obvious place, assume the obvious place is incomplete rather than assuming the thing does not exist.

Sources

Webhooks, WhatsApp Business Platform — Fields table, 19 fields, updated 29 April 2026
standby Webhook Event Reference, Messenger Platform — updated 25 September 2024
messaging_handovers Webhook Event Reference, Messenger Platform — updated 14 September 2021
About the WhatsApp Business Platform — Meta Business Agent capabilities

Originally published at botsense.io

Meta's Embedded Signup notice names v2. The table retires v3 too.

botsense seo — Fri, 04 Sep 2026 08:13:21 +0000

Meta's deprecation banner on every embedded signup page names one version: v2, ending 15 October 2026.
The versions table on the same site retires four: v2, v3, v2-public-preview and v3-public-preview, all in October 2026.
A partner who reads the banner and confirms they are on v3 will conclude they are safe. They are not.
Moving to v4 is not a version string change. The extras object becomes empty and product configuration moves into a new Facebook Login for Business configuration.
Only v4 supports Click to WhatsApp Ads, Marketing Messages API and Conversions API through login config. On v3 and v2 those read "Not supported".

If you onboard WhatsApp customers through a partner platform, someone in that chain runs Embedded Signup. It is the flow where a business logs in with Facebook, picks or creates a WhatsApp Business Account, and grants your app access to it.

Meta has put a deprecation notice at the top of every page in that section. It reads the same everywhere: v2 will be deprecated on 15 October 2026, migrate to v4.

The notice is accurate. It is also narrower than what the versions table says, and the gap between the two is the kind that gets discovered in October.

What the embedded signup versions table actually says

The versions page lists each release with the date it arrived and the date it stops being available. Four rows carry the same end date.

VERSION	INTRODUCED	AVAILABLE UNTIL
v4-public-preview	12 May 2026	TBD
v4	8 October 2025	TBD
v3-public-preview	14 August 2025	October 2026
v2-public-preview	14 August 2025	October 2026
v3	29 May 2025	October 2026
v2	January 2023	October 2026

v3 was introduced in May 2025 and ends in October 2026, seventeen months later. It is not named in the banner.

That matters because of how a partner would check. You read the warning, you look up which version your integration sets, you see v3, and you close the tab. The banner told you the affected version and yours was not it.

Migrating embedded signup is not a version string change

This is the part that decides how much time you need.

On v2 and v3, the version lives in your code. The implementation passes an extras object that names the version alongside feature flags:

// v3 example
extras: {
  version: "v3",
  sessionInfoVersion: 2,
  featureType: "marketing_messages_lite"
}

On v4, Meta's own documentation says the extras object is purposely empty. There is no version to set. Instead you create a new Facebook Login for Business configuration and select the products you want, and selecting them sets you to v4 automatically.

So configuration moves from your front-end code into a dashboard object. That is a different task from editing a string. It needs a new login configuration created, tested against a real onboarding, and rolled out, and if anything downstream reads the session payload the shape of what comes back changes with it.

The one piece of good news is in the same document: versions are not exclusive, and Meta says partners can roll out a new version gradually to reduce risk. You do not have to switch everyone at once.

How to tell which version you are actually running

The version is not stored anywhere you can query. It is whatever your onboarding page passes at the moment the flow launches, so the only reliable answer comes from reading the code that launches it.

Find the page that opens the signup window and look for the extras object handed to the Facebook login call. What you see there tells you where you stand.

If it contains version: "v2" or version: "v3", you are on a version that ends in October 2026.

If it contains a sessionInfoVersion key, that is a v2 signature specifically. Only v2 requires it, and its presence usually means the integration has not been touched since before May 2025.

If it contains featureType or a features array naming app_only_install or marketing_messages_lite, those are v2 and v3 configuration shapes. On v4 the same capabilities are selected in the login configuration instead.

If the extras object is empty, you are already on v4 and this deadline does not apply to you.

One nuance worth knowing if you inherited the integration: app_only_install lets a partner reach WABAs through a granular business integration system user token rather than creating a system user access token. If your platform relies on that behaviour, confirm it is selected in the new login configuration rather than assuming it carries across, because it moves from a code flag to a dashboard product.

Meta also notes that the versioning cadence follows Graph API. If you already have a process for tracking Graph API version changes, this belongs in it rather than in a separate reminder somebody has to remember.

What you gain, and what you cannot have on v3

The feature table draws a line that has nothing to do with deprecation dates.

CAPABILITY	V4	V3	V2
Products via login config	Marketing Messages API, Click to WhatsApp Ads, Conversions API	Not supported	Not supported
Session info logging	Sent back for all flows	Sent back for all flows	Requires an explicit sessionInfoVersion
Completion state	Verified, unverified, or no phone number	Verified, unverified, or no phone number	Must finish with a verified number

Read the first row again if you run Click to WhatsApp ads. Onboarding customers with CTWA and the Conversions API attached through login config is a v4 capability. On v3 it is not available at all.

That reframes the migration. It is not only a deadline to survive, it is the version where three onboarding products become reachable.

The session info row is the one most likely to bite quietly. On v2 the callback that returns the customer's WABA ID and phone number ID only arrives if you explicitly set sessionInfoVersion. On v3 and v4 it is sent for every flow. If your integration was built against v2 and someone assumed the callback was automatic, it was not.

Dates in this post were read from Meta's documentation on 3 September 2026. Meta moves deprecation dates, and the versions page carries an "Updated" stamp from December 2025 while describing a release from May 2026, so its own metadata is behind its content. Check the live page before you plan around any date here.

There is a UI change landing separately

Buried under the version list is a note that the refreshed interface currently in public preview will roll out to all versions of Embedded Signup in early September.

That is now, and it is independent of which version you run. If your onboarding documentation contains screenshots, or your support team walks customers through the flow screen by screen, that material is about to be wrong regardless of whether you have migrated.

What to do in the next six weeks

Find out which version you are actually on. Not which version you think you specified. Grep your onboarding page for the extras object and read the value.

If it says v2 or v3, or if the object exists at all, you have work to do. An empty extras object is the v4 signature.

Create the new Facebook Login for Business configuration and select the products you want, including Click to WhatsApp Ads if you use it. This is where the migration effort actually sits.

Test a real onboarding end to end, and confirm the session callback still delivers the WABA ID and phone number ID your system stores. Do not assume the payload is unchanged.

Roll out gradually rather than switching everyone at once, which Meta explicitly supports.

Then update your onboarding screenshots, because the interface is changing this month whatever you decide about versions.

The pattern worth carrying forward

A deprecation banner is a summary, and summaries drop things. The banner named the oldest version, which is reasonable, because v2 dates from January 2023 and is presumably where most legacy integrations sit.

But the authoritative statement of what ends and when is the table, not the banner. Anyone who checked the prominent warning and stopped there has now confirmed the wrong thing.

We have written before about a Meta capability restricted to Select and Premier Solution Partner tiers that Meta's partner comparison never defines. This is the same category of problem read from the other end. There, the detail existed and the summary omitted it. Here, the summary is correct about one version and silent about three more.

Originally published at botsense.io

The 72-Hour Free Window on Click-to-WhatsApp Ads Has a Condition Nobody Mentions

botsense seo — Wed, 19 Aug 2026 07:22:22 +0000

The two windows, and why people confuse them

There are two separate timers in WhatsApp Business, and treating them as one is the root of most CTWA budgeting mistakes.

	Customer service window	Free entry point window
What opens it	Any customer message, by any route	A CTWA ad or Facebook Page CTA click, Android/iOS only
How long	24 hours from the customer's message	72 hours from your reply
What you can send	Any free-form message	Any message, including marketing templates
What it costs	Free-form replies are free	Everything is free while open
Opens automatically	Yes	No: only if you reply within 24 hours

According to Meta's documentation: "If you respond within 24 hours using any type of message, the message will be free, and a Free Entry Point window will be opened, starting from the time when you responded."

A free entry point conversation requires two conditions: (1) the customer messages from a CTWA ad or Facebook Page CTA button on Android or iOS — desktop and web are not supported; (2) you respond within 24 hours. The 72 hours starts from the moment you reply, not from when the customer messaged.

What this means for how you run the campaign

Match your ad delivery hours to when someone can actually reply
Set an automated first response to secure the window
Treat your reply capacity as a hard limit on ad spend
Plan the follow-up sequence across three days, not one

Why the ad gets rejected before it ever runs

WhatsApp-side rejections are the surprising ones. The ad account is fine, the creative is fine, and the campaign still cannot launch because something is wrong with the WhatsApp Business Account behind it.

The display name problem

Rejection ground	What Meta rejects
Identity mismatch	Name does not correspond to verified business identity
Promotional words	Official, Best, No.1, Cheap, Free
Meta product names	WhatsApp, Facebook, Messenger
Generic names	Customer Service, Support Team, Info Desk
Formatting	Emojis, excessive punctuation, slogans

Identity mismatch is the single most common cause. The fix is completing business verification first, linking the website, and making sure the Facebook Page name and the requested display name tell the same story.

What Click-to-WhatsApp Ads cannot do

It cannot push, only pull. CTWA starts conversations when someone chooses to click. You cannot use it to reach people who have not engaged.

A click is not a conversation. The ad opens WhatsApp with a pre-filled message the user can edit or delete. Plenty of people open it and never press send. You pay for the click either way, and no window opens.

Desktop and web do not count. The free entry point requires Android or iOS.

Attribution is harder than a landing page. Without a platform connecting ad click to conversation to outcome, you lose the thread between spend and revenue.

The short version

Click-to-WhatsApp Ads work well when three things are true: you have a genuine reason for someone to start a conversation, you can reply inside 24 hours, and you treat the following 72 hours as the actual campaign.

Most of the value people describe as "the 72-hour free window" is really the reward for answering quickly.

COD Verification and RTO: Why the Numbers in This Market Do Not Add Up

botsense seo — Wed, 19 Aug 2026 07:20:30 +0000

What COD verification claims to do

The mechanism is straightforward. A cash-on-delivery order carries no payment commitment, so nothing at checkout confirms buyer intent, address accuracy, or phone number validity. An automated call placed shortly after checkout tests all three before the parcel enters fulfillment.

That much is sound. The disagreement starts at the number attached to it.

Vendor claim	RTO reduction	Cost per RTO	Source given
Vendor A	30–45%	—	None
Vendor B	—	₹400–600	None
Vendor C	—	₹180–240	None
Vendor D	30–40%	₹200–500	None at the time of writing

Cost per RTO varies by more than three times between vendors describing the same operation in the same market. The reduction percentages sit in a band wide enough to be unfalsifiable.

The base rate is contested, not settled

To claim a reduction you need a starting point, and the starting point is not agreed.

According to GoKwik: "COD orders in Indian e-commerce see RTO rates of nearly 26%, compared to less than 2% for prepaid orders."

Unicommerce reports differently. Based on 410 million tracked shipments across more than 6,000 D2C brands, during the festive quarter "COD orders returned at 58%", against prepaid "under 15%."

Both are first-party platform data. Neither is citing a blog. And they disagree by more than double at the peak.

If your baseline could be 21% or 58% depending on the month, a vendor promising to cut it by "30 to 40%" has told you nothing you can hold them to.

The most repeated fact has no source

Almost every article on this subject opens with a version of the same line: roughly 60% of Indian e-commerce orders are cash on delivery.

That figure traces back to ET Prime Research in 2024 through secondary write-ups, yet the original remains unreachable. Bain & Company's How India Shops Online contains no absolute COD share figure. Unicommerce publishes return rates but explicitly not the COD share of orders.

That does not make the figure wrong. It makes it uncheckable — which is a different problem and in some ways a worse one.

What is actually sourced is the timing, not the reduction

One figure in this space comes with a named source: GoKwik states "Send confirmation within 5 minutes of order placement (response rates drop 40% after 30 minutes)."

This is still the most actionable thing published on the subject, because it describes a window rather than an outcome. The typical manual process misses it entirely — the calling team works through the queue the following morning, by which time the window has been closed for approximately fourteen hours.

What COD verification should be measured on

Since reduction figures are not checkable, measure the things that are:

Time from order placement to first call attempt (minutes, not hours)
Connect rate: what proportion of calls are answered
Confirmation rate: of those answered, how many confirm the order
RTO rate on confirmed orders versus unconfirmed orders in the same period and category
Your own fully loaded cost per RTO: forward shipping, reverse shipping, packaging, handling

The fourth metric settles it. Comparing confirmed against unconfirmed orders in your own data, in the same weeks and same categories, tells you what verification is worth to you. No industry average can do that.

Run it for one month before signing anything longer than a month.

Including our own numbers

Botsense sells AI calling, including COD verification. Our own pages carried RTO reduction percentages with no source attached, in the same shape as the table above.

We are correcting them. A post arguing that unsourced percentages are worthless would be worth nothing if it quietly exempted the company publishing it.

What we can tell you honestly: we do not know what COD verification will do to your RTO rate, because it depends on your categories, your pin codes, your season, and your current process. If a vendor gives you a percentage instead, ask where it came from. The answer is the useful part.

The WhatsApp Green Tick Is Now Blue: What Meta's API Actually Asks For

botsense seo — Wed, 19 Aug 2026 07:18:56 +0000

Is the WhatsApp green tick actually green?

The terminology everyone searches for is "green tick," but Meta's current documentation uses different language. An Official Business Account (OBA) is described as having "a blue checkmark beside their name in the contacts view."

The color changed between July 2024 and February 2025, when archived snapshots show the transition from "green checkmark badge" to "blue checkmark badge." However, Meta's approval notification system hasn't caught up — it still tells newly approved businesses they received a green badge, creating confusion when users see a blue checkmark instead.

The practical answer: The badge is currently blue, though Meta and the broader community frequently still refer to it as green.

What the Official Business Account page tells you

Meta's official OBA eligibility page lists five criteria, all procedural in nature:

Criterion	What it means
Policy compliance	Complies with WhatsApp Business Messaging Policy
Thirty days	Registered on WhatsApp Business Platform for at least 30 days
Business verification	Business portfolio verified through Business Verification
Two-step verification	Enabled on the phone number
Display name	Approved

Notably absent from this documentation is any mention of notability, fame, or press coverage. A business reviewing this page would reasonably assume that meeting these five procedural conditions is sufficient.

What Meta's API actually asks for

The requirement exists but lives in documentation most businesses never consult. Meta's OBA Status API reference includes a field called supporting_links — described as "Supporting links that demonstrate business notability (minimum 5, maximum 10)."

Meta's Business Help Center further clarifies notability as "a well-known business that has a substantial presence in news articles from publications with sizable audiences."

This represents a significant gap: the requirement for five to ten editorial links demonstrating business notability appears in the API schema and help documentation but not on the main eligibility criteria page. Most guides to obtaining the badge quote Facebook's verification standards instead, which ask for coverage in "multiple news sources" without specifying a minimum number.

Why the WhatsApp green tick usually goes through a provider

Meta documents a self-serve application path through WhatsApp Manager, but for most accounts, the Submit Request button doesn't appear. When this occurs, Meta directs businesses to "reach out to your Meta point-of-contact, Solution Provider support, or Meta Support."

This explains why most applications go through providers — not because Meta forbids self-serve submission, but because the option isn't exposed to most accounts.

What to have ready before applying

At least five links to editorial coverage in publications with genuine audiences (not paid placements)
Business portfolio verified through Business Verification
Two-step verification enabled on the number
Display name approved and directly associated with the business
Thirty days elapsed since registration on the platform

If rejected, businesses must wait 30 days before resubmitting. Meta states that denials currently cannot be appealed, though display name rejections follow a separate process with their own appeal route.

The key principle

The badge follows genuine editorial coverage. If a business lacks five pieces of authentic news coverage, waiting is preferable to submitting an application that will fail and trigger another 30-day waiting period before resubmission.

WhatsApp Multiple Providers: Meta Is Removing the Switching Barrier It Built

botsense seo — Wed, 19 Aug 2026 07:17:16 +0000

What Meta is actually changing

The WhatsApp Business account structure is evolving into two separate components: one managing phone numbers and business profiles, the other handling templates and billing. This enables businesses to operate multiple providers on a single phone number with isolated billing.

Component	WhatsApp Business Account	Messaging Account
Holds	Phone numbers, usernames, profile, catalogs	Templates, billing, webhook subscriptions
Owned by	Always the business	Business or provider (one per provider)
Identifier	New, unavailable until Phase 2	Keeps existing WABA ID

Critically, the account holding your phone number remains yours. Partner accounts handling templates and billing may belong to service providers.

Why WhatsApp multiple providers becomes possible

Currently, a number belongs to one WhatsApp Business Account containing all components. Switching providers requires migrating the number, creating substantial friction that discourages changes.

Meta's documentation directly addresses this shift: "The phone number migration process that previously acted as a natural switching barrier no longer applies." This friction was structural, not technical — a competitive moat that Meta has now dismantled.

What WhatsApp multiple providers share

Adding a second provider does not increase capacity:

Throughput remains at the phone number level
Messaging limits remain at the business portfolio level (unique users per 24-hour period)

When multiple providers operate a single number, they share throughput and daily user limits. Billing separates by which application sends the message, but messaging capacity does not multiply.

What does not change

Deregistration processes, pricing models, and customer-facing experience remain unchanged. WhatsApp users see one trusted contact regardless of provider count.

The timeline

Phase	Timeline	Details
Phase 1	H2 2026	Automatic migration, backward compatible, parallel providers enabled
Phase 2	H1 2027	New account identifiers become available
Phase 3	H1 2028	Mandatory transition to new identifiers

No action is required from businesses during migration. The change shifts market dynamics: the structural cost of switching providers drops to near zero, and provider relationships become genuinely competitive.

AI Collections Calls in India: RBI's Rules Are Not the Ones You Have Been Quoted

botsense seo — Wed, 19 Aug 2026 07:16:03 +0000

There are two calling windows, not one

The widely circulated recovery calling window of 8:00 a.m. to 7:00 p.m. applies to general lending. However, microfinance loans operate under a distinctly different timeframe. According to RBI's Responsible Business Conduct Directions, microfinance borrowers can only be contacted between 9:00 a.m. and 6:00 p.m.

Calling a microfinance borrower at 6:30 p.m. isn't merely outside operating hours — it's officially classified as a harsh practice.

Where the rules differ by lender type

Requirements presented as universal across the industry actually vary considerably:

Requirement	Banks	NBFCs
IIBF certification for recovery agents	Mandatory	Not in the Directions
Call recording	Required	No equivalent requirement
Calling window	8:00–19:00 (microfinance excluded)	8:00–19:00 (microfinance excluded)
Microfinance window	9:00–18:00	9:00–18:00

Banks must ensure recovery agents complete the Indian Institute of Banking and Finance certificate course, while NBFC Directions specify only due diligence and police verification. Banks require call recordings with borrower notification; NBFCs face no such mandate.

What RBI says about AI collections calls

RBI's Responsible Business Conduct Directions contain no reference to artificial intelligence, automated calling, voice bots, or synthetic voices. The regulatory framework addresses human agents exclusively and hasn't been updated for automation technology.

The absence of specific guidance means automated calls inherit all requirements written for people: calling windows, prohibitions against persistent contact, and other behavioral standards.

One potential distinction exists around the prohibition against "making threatening and/or anonymous calls." Whether a synthetic voice call qualifies as anonymous remains judicially unresolved.

AI collections calls do not move liability

Outsourcing recovery functions doesn't transfer regulatory responsibility. Banks and NBFCs remain liable for their service providers' actions regardless of whether contact is human or automated.

Under the Reserve Bank–Integrated Ombudsman Scheme 2026, RBI can award compensation up to ₹30 lakh for consequential losses, plus up to ₹3 lakh for "loss of the complainant's time, expenses incurred, harassment/mental anguish suffered."

What to establish before you buy

Which regulatory instrument governs your portfolio
Whether any portion qualifies as microfinance requiring the 9:00–18:00 window
Whether platforms can enforce different windows for different segments
How your organization defines "persistent calling"
Recording and borrower notification requirements
Internal authorization for meeting anonymity prohibitions

The segment-level calling window represents the most critical verification point. A platform unable to enforce 9:00–18:00 for microfinance while running 8:00–19:00 elsewhere cannot serve mixed portfolios.

Where we stand

RBI has not published guidance confirming automated recovery calling compliance. Vendors cannot represent automation as compliant on RBI's authority. Compliance obligations depend on individual licenses and portfolio composition.

WhatsApp Max Price: What Meta Documented, and the Three Things It Did Not

botsense seo — Wed, 19 Aug 2026 07:14:48 +0000

The WhatsApp max price timeline, as Meta dates it

Phase	Date	Who can use it
Limited Beta	15 May 2026	Any partner and any directly integrated business
Open Beta	October 2026	Any partner can enable for all clients
General Availability	Q2 2027	Required in "eligible geographies"

Nothing about billing changes in the meantime. Meta is explicit that "there is no change to how Meta charges on the WhatsApp Business Platform." If you never set optimization_spec on a template, nothing happens to you at all.

What GA actually means if you are not on Cloud API

This is the line worth reading twice:

"General Availability (GA) as of Q2 2027 — The max price feature will become required in eligible geographies and fixed, published rates for marketing messages will only apply on the Cloud API."

Two commitments in one sentence. The WhatsApp max price stops being optional somewhere, and the familiar per-category rate card survives somewhere else — on Cloud API.

The word doing the most work is "eligible". Meta does not define it. The phrase "eligible geographies" occurs exactly once across all five documents — in the GA sentence above. No list, no link, no table. India is not named in any published restriction group, but "India is eligible to use the Marketing Messages API" and "India is in scope for the GA requirement" are two different statements about two different lists — and only one of those lists has been published.

What Meta never says about undelivered messages

Meta does not say what happens to messages that fall below the max price threshold.

I searched nineteen terms across eight public documents: auction, clearing price, market rate, demand, competing, bid against, not sent, undelivered, dropped, skipped. Zero occurrences, all nineteen, in all eight.

That absence carries weight, because Meta plainly knows how to describe undelivered messages. Error 131049 reads "This message was not delivered to maintain healthy ecosystem engagement." Error 130472 reads "Message was not sent as part of an experiment." Both describe a marketing message Meta decided not to deliver — both get a number, a published description, and a row in the error code reference.

Meta issues a numbered, published error code when it declines to deliver a marketing message. It has not issued one for max price.

What the market claims instead

The top-ranking guide on this feature presents three specific savings percentages and attributes them to "Meta's examples" with no link to any Meta page. Those figures do not appear in any of the five documents above.

More consequential is the auction framing that runs through wider commentary — the idea that your bid competes against other advertisers. It is a reasonable inference. It is not something Meta has written down about this product.

The distinction matters when a client asks what happens to their undelivered messages. "Meta has not documented that" is a defensible answer. "They lost the auction" is a claim you cannot source.

The Solution Partner controls nobody is reading

Meta shipped a partner-facing control for the beta that has gone almost entirely uncovered. The allowlist cap moved twice — from 5 to 15 on 17 June, then to 100 on 31 July.

On 5 August, Meta added a visibility switch: whatsapp_manager_marketing_messages_max_price_enroll_status takes OPT_IN or OPT_OUT. But:

"This setting controls only the visibility of the max price experience in WhatsApp Manager. It doesn't change a WABA's eligibility for max price, and it doesn't affect max price settings configured through the API."

It hides a UI. It does not gate the capability.

Practical steps

Decide whether your marketing volume runs through Marketing Messages API or Cloud API, because Q2 2027 treats them differently.
If you are a Solution Partner, check your allowlist headroom against the 100 cap before Open Beta in October.
Read whatsapp_manager_marketing_messages_max_price_enroll_status as a UI switch, not an access control.
Do not commit to a max price strategy on savings percentages that carry no link to Meta.

The honest summary: Meta has committed to a date and a consequence, and has not published the list of places the consequence applies to. If you sell or buy WhatsApp marketing in India, you are entitled to know whether Q2 2027 changes your rate card. As of today, Meta's public documentation does not tell you.

Meta Business Agent: Meta Documented the Costs for One Path and Not the Other

botsense seo — Wed, 19 Aug 2026 07:12:39 +0000

What Meta Business Agent costs you on the WhatsApp Business app

Meta has published specific consequences for WhatsApp Business app users who enable the Meta Business Agent. According to their Help Center, customer conversations are collected to improve Meta's AI systems, and this collection continues even when businesses mute the agent:

"Messages sent or received in chats that have connected Meta Business Agent will still be collected by Meta to improve AI at Meta, even when you mute Meta Business Agent."

Deletion is the only documented control that stops data collection. Muting merely pauses agent responses without halting the data-gathering process.

Meta also documents operational feature losses for app-path users:

Broadcast lists, disappearing messages, greeting and away messages become unavailable
The inability to pause or delete the agent using WhatsApp Web

What the Cloud API documentation says instead

For businesses using Meta's Cloud API—the path most Indian companies take through Solution Partners—the documentation differs significantly. Cloud API developer documentation meticulously describes mechanics: standby webhooks, handoff procedures, thread control endpoints, and control-release mechanisms.

However, across nine developer documents reviewed, there are zero mentions of data collection practices, feature restrictions, or messaging capability changes equivalent to those published for app users.

The nine documents, and what is not in them

A systematic search across Meta's developer documentation for the agent yielded striking gaps:

Term Category	Search Terms	Results Found
Feature loss	disable, unavailable, cannot use, lose access (22 terms)	0
Data use	improve AI, train, retention, privacy, consent (17 terms)	0
Messaging capability	messaging limit, throughput, rate limit (11 terms)	0

What this does not prove

This documentation gap does not necessarily indicate Meta is concealing unfavorable terms. Cloud API deployments have fundamentally different architectures than phone-based WhatsApp Business apps. Broadcast lists and linked devices are app-specific concepts that don't exist in Cloud API environments, so feature losses wouldn't apply.

The core problem is simpler: Solution Partners cannot answer clients' basic questions about costs because Meta hasn't published the answers in either direction.

Where Meta Business Agent is available

The WhatsApp Help Center clearly states: "This feature is currently only available in limited countries to select businesses. It might not be available to you yet."

The developer documentation merely requires businesses be "based in a country authorized for Meta Business Agent" without naming any specific countries. No published country list exists, and India is neither explicitly included nor excluded in any official documentation.

One defect you can check yourself

The thread control endpoint appears at three different URLs across Meta's documentation:

Get Started guide: https://graph.facebook.com/v21.0/<PHONE_NUMBER_ID>/thread_control
Thread Control reference: https://api.facebook.com/business/whatsapp/phone_numbers/{phone_number_id}/thread_control
Changelog: POST /business/whatsapp/phone_numbers/{phone_number_id}/thread_control

The reference and changelog align; the walkthrough diverges. Developers following the Get Started guide would call a different endpoint than the official reference specifies.

Actionable recommendations

Verify deployment path first: Cloud API and WhatsApp Business app paths are documented entirely separately with different consequences
Read the mute clause carefully: For Business app users, muting doesn't stop Meta's data collection
Check eligibility individually: Use the eligibility endpoint rather than assuming global availability based on third-party claims
Test both endpoints: If implementing thread control, verify both documented URLs in your testing environment

The asymmetry remains: one deployment path has published costs; the other has published mechanics only.