What Vesma connects to, and what each connection may do
Every integration below lists the permissions it asks for and the things it deliberately cannot do. If a page like this is vague, assume the worst about it.
Messaging channels
Website chat widget
Every plan, including freeA script tag on your site. Visitors get the same AI that runs on WhatsApp, and the conversation lands in the same inbox.
No approval needed — this is the fastest way to see the product against real enquiries.
WhatsApp Business Platform
Every plan, including freeConnect a number through Meta's official onboarding. Vesma replies inside the 24-hour service window and uses approved templates outside it.
A number already registered to the consumer WhatsApp app must be migrated, and can no longer be used in that app on a phone. Site-visit slots are offered through a native WhatsApp Flow, so a lead taps a date and time instead of typing one.
Comments on posts and reels are classified and answered publicly, and the commenter becomes a lead with their history attached. Direct messages run through the same AI, and posts and Reels publish from Vesma.
A comment is answered in public. The one automatic direct message Meta allows per comment is offered where it is permitted; nothing is sent unsolicited beyond that.
Facebook Pages
Every plan, including freeThe same comment handling and messaging as Instagram, on your Page posts, and Vesma can publish, edit and take a post down.
Messenger conversations land in the same inbox as WhatsApp, so one person answers everything in one place.
Google Calendar
Connecting your calendar is optional. It is what lets the AI avoid offering a slot you are already busy in, and keeps bookings in the calendar your team actually looks at.
- When the AI books an appointment, Vesma creates that event on your calendar.
- If the appointment is rescheduled in Vesma, the event is moved to the new time.
- If it is cancelled, the event is removed from your calendar.
- Before offering a slot, Vesma checks whether you are already busy, so the AI does not double-book you.
- It does not read the contents of your other events.
- It never shares your calendar data with anyone else.
- It is never used for advertising or to train models.
The permissions we ask for
- Permission to manage calendar events — so it can create, move and remove the appointments it books.
- Permission to view your free/busy availability — so it knows which slots it may offer.
Vesma’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can disconnect at any time from Settings, and see data deletion for removing what we hold.
Google Ads
Connecting Google Ads is optional. It lets Vesma set up the Search or Performance Max campaign you planned inside your own Google Ads account, so you are not copying keywords and ad text across by hand — and report back which clicks became qualified enquiries.
- Lists the Google Ads accounts you can advertise from, so you choose which one Vesma works in.
- Creates the Search campaign (ad group, keywords, responsive search ads) or Performance Max campaign (one asset group, cropped images, search themes) you planned in Vesma — paused, in that account.
- Reads how those campaigns are doing, so results show up next to the leads they produced.
- Tells your Google Ads account which clicks became qualified enquiries, so Google learns to find buyers rather than browsers.
- It never switches a campaign on or spends money — everything it creates starts paused, and you activate it.
- It does not touch campaigns you created yourself, or your billing.
- It never shares your Google Ads data with anyone else, and never uses it to train models.
The permissions we ask for
- Permission to manage your Google Ads campaigns — Google offers this as a single permission, and it is what lets Vesma list your accounts, create paused campaigns, and read their results.
- Permission to send conversion events (Google Data Manager) — so Vesma can tell your own Google Ads account which ad clicks turned into qualified enquiries. Only the click id Google issued, the time and the stated budget are sent; never a name, phone number or message.
You can disconnect at any time from Marketing › Connections, which deletes the stored authorisation. The same Google API Services User Data Policy and Limited Use commitments above apply.
Meta Ads
Connecting your Meta ad account lets Vesma publish click-to-WhatsApp campaigns into it and, for the leads those ads produce, tell Meta which ones stated a budget and qualified.
- Lists the ad accounts and Pages you can advertise from, so you choose which one Vesma works in.
- Creates the campaign, ad set and creative for a click-to-WhatsApp ad, paused, in that account.
- Reads review and delivery status, so results show up next to the leads each ad produced.
- When a lead from one of those ads states a budget and qualifies, sends a value-weighted QualifiedLead event to Meta against that click, through the Conversions API for Business Messaging.
- It never switches a campaign on or spends money — everything it creates starts paused, and you activate it in Vesma or in Ads Manager.
- It does not touch campaigns you created yourself, your billing, or your Page's posts and comments.
- The outcome event carries the click id Meta issued, the time and the stated budget. Never a name, phone number or message text.
The permissions we ask for
- ads_management and ads_read — to create paused campaigns in the ad account you choose, and read their status and results.
- business_management and pages_show_list — to list the ad accounts and Pages you hold, so you can pick one.
- whatsapp_business_manage_events — to send the qualified-lead outcome against the WhatsApp click that produced it.
You can disconnect at any time from Marketing › Connections, which deletes the stored authorisation.
Leads from listing portals and your own website
Anything that already collects leads for you can push them into Vesma as they arrive, and the AI answers them in seconds like any other enquiry. No approval from anyone is needed — you create a key in Settings › Leads from portals and hand it to whoever sends the leads.
- MagicBricks, 99acres, Housing.com, NoBroker
- IndiaMART and JustDial
- A broker or channel partner sending you enquiries
- Your own website form or backend
- Referrals logged by your team
Each key is tied to one of these. Leads arriving on it are recorded as coming from that source, so your reports say where business actually came from.
One HTTP request. A name and a phone number is the minimum.
POST /api/v1/ingest/lead
X-Api-Key: vsk_…
{ "name": "Priya Sharma",
"phone": "+919800000001",
"requirement": "3BHK in Whitefield" }Common field spellings are read automatically — SENDER_NAME, SENDER_MOBILE, mobile, fullName and so on — so a feed that already exists usually works without being rewritten.
- Creates the lead and starts the AI conversation immediately
- Reads the enquiry text into budget, configuration and location where it can
- Stamps the lead with the source bound to the key
- Records when each key was last used, so a dead feed is visible
- It does not log in to a portal or scrape one on your behalf — the portal, or your developer, sends the lead to us
- It does not trust a source named in the payload; only the key decides the source
- It cannot read anything back out of your workspace — an ingest key only writes leads in
- The key is shown once, at creation, and never again
Available on every plan, including the free one. Only a workspace admin can create or turn off a key, and turning one off stops that feed without affecting any other.
Facebook Page and Instagram posting
A different connection from the comment handling above, with its own permissions and its own consent screen. Vesma drafts posts on a rhythm you set and publishes them to your Facebook Page and Instagram account, including Reels when the post carries a video, and can edit or take down a post it published. It reads nothing back except whether the post went out.