For agencies running real-estate ads: prove what happened after the click
An agency is paid for leads and judged on sales. You deliver two hundred click-to-WhatsApp enquiries in a month, the builder's team calls forty of them, closes one, and the review meeting opens with “your leads are junk.” You have no answer, because everything after the handoff happened on someone else's phone.
Vesma sits in that gap. It answers every lead you deliver, the moment it arrives, and keeps a record of what each one said. That gives you two things you have never had: proof of what happened to all two hundred, and a way to send the good ones back to Meta and Google so the next campaign finds more of them.
The conversation you keep losing
The problem is not that your leads are bad. Some are, some are not, and nobody knows which, because the evidence lives in forty phone calls nobody recorded and a hundred and sixty messages nobody answered. The builder remembers the ones that wasted their time. You remember the cost per lead. Neither of you has the data to settle it.
Every tool in this category stops at the same place: it delivers the lead into an inbox and the conversation becomes the client’s problem. That is exactly where the argument about quality starts.
What you can finally show
When Vesma answers every enquiry, the monthly report changes shape. Instead of “200 leads delivered, ₹412 each” you can put a funnel in front of the client. The numbers below illustrate the shape of that report; they are not a result we are claiming:
The last row is the one that ends the “junk leads” conversation. It separates the leads that were wrong for the project from a sales team that did not follow up, and it does so with what buyers actually typed.
What goes back to the platform
Meta and Google optimise on what they can see: a click, a form fill, a “conversation started.” They have never been told that one of those conversations contained “my budget is around 1.4 crore, possession by next Diwali,” because that sentence sat in a WhatsApp thread nobody else reads.
Vesma reads it. When a lead from your ad states a budget and qualifies, a value-weighted QualifiedLead event goes back to the platform against the click that produced it: to Meta through the Conversions API for Business Messaging, to Google through the Data Manager. The click id, the time and the stated budget as a value. Never a name, number or message.
The platform can then do what it is built to do and find more people like the ones who qualified, instead of more people like the ones who clicked. That is the product. The report is what it produces on the way.
Under your name
Agencies do not want to introduce a vendor to their clients. The white-label product exists for that: your logo, colours and domain; a separate, isolated workspace per client; an agency console that shows every client and its status in one place; and partner billing with an optional setup fee, a per-client onboarding fee and a monthly fee, collected through payment links you send.
Clients see your product. Their leads, documents, WhatsApp number and campaigns never touch another client’s. You see all of it.
What day one looks like
Everything the client’s sales team needs is in one inbox: the conversation, the captured brief, the booked visit. Any rep can take a conversation over with one tap and hand it back.
Vesma reports what buyers said, not what they did afterwards. If the client’s team closes a deal on a phone call and never marks it, that outcome stays outside the loop. Site-visit attendance is the same: somebody has to record it, and in practice nobody does, so we do not pretend to optimise on it. The signal we send is the one that exists for every lead and that nobody can fake: what the buyer typed.
Ad-account connection is in beta while Meta and Google complete their reviews. Until then we switch the loop on per workspace, on request, after a conversation. What is live and what is beta is listed plainly.
Common questions
Does the client see Vesma, or my agency?
Your agency. The white-label product puts your logo, colours and domain on it. Clients sign in at your address, and every email and page they see carries your name. Vesma appears nowhere they look.
Whose ad accounts do the campaigns run in?
The client's, or yours if you run their ads from your own accounts today. Vesma connects to whichever account you choose and publishes there, paused. It never creates or bills an ad account of its own.
What if the client already has a CRM?
Vesma is the WhatsApp qualification layer in front of it. Qualified leads, with the captured budget and timeline, are what you hand over. Most clients stop opening the old CRM for ad leads within a month, but nothing forces that.
How do I charge for it?
However you charge today. Partner billing supports an optional setup fee, a per-client onboarding fee and a monthly fee, collected through payment links. Many agencies fold it into the retainer and charge nothing separately; the product does not care.
Is the outcome loop live?
It is built, tested against Meta's validator and running on our own campaigns. Connecting a customer's ad account waits on Meta's App Review and Google's OAuth verification, which is why it is marked beta. We switch it on per workspace as those clear.
Bring one client's campaign
The fastest way to see it is on a live campaign you already run. We set up the workspace under your brand, switch on the beta, and you watch the first hundred enquiries get answered.