Integrations · WhatsApp

WhatsApp follow-ups for AI voice calls

A missed call is not a lost lead if a WhatsApp lands a minute later. Vyora connects to the WhatsApp Business API account you already have, AiSensy, Interakt or Wati, and sends one of your approved templates right after an AI call, to everyone or only to the people who did not pick up. No Zapier, no code.
01

How it works

Vyora does not run a WhatsApp inbox or send messages from its own number. A Workflow places the AI call, reads the result, and a Send to another app step calls your provider's API with the contact's name, number and call details filled in. Your provider sends the template from your WhatsApp number and bills the conversation as usual. The API key stays in Vyora; it is not passed to the telephony platform that places the call.

1

AI call

2

If: they didn't answer

3

Send to another app

4

Template on WhatsApp

02

AiSensy vs Interakt vs Wati: what changes in the setup

All three send Meta-approved templates through the official WhatsApp Business API. For this integration they differ in four places, and each guide covers its own in detail.

AiSensy
Interakt
Wati
Phone number
With +91, as is
10 digits + separate "+91"
91 + 10 digits, no "+"
Authentication
API key inside the JSON body
Basic auth header
Bearer token header
Template variables
Ordered list (templateParams)
Ordered list (bodyValues)
Named pairs (custom_params)
Before you start
Needs a Live "API Campaign" per template
Public API on Growth / Advanced plans only
Token needs template-send permission

Already on one of them? Use that one. Choosing fresh, compare pricing and plan limits on each provider's own site; the call side in Vyora works the same with all three.

03

The setup in five steps

  1. 01

    Get a template approved in your provider

    Create the WhatsApp template in AiSensy, Interakt or Wati and wait for Meta approval.
  2. 02

    Build a Workflow with a Call step

    In Vyora, open Workflows, create a workflow and pick the agent that should call.
  3. 03

    Branch on the call result

    Add an If / else step with the condition "They didn't answer" if only missed calls should get WhatsApp.
  4. 04

    Add a "Send to another app" step

    Paste your provider's API address, auth and JSON body, using contact fields such as {{callee_name}}.
  5. 05

    Test, then publish

    Run a test to your own number, confirm the run log says "Sent to ... (200)", then publish.

Provider-specific details for step 4 (address, auth, JSON body, number format) are in the AiSensy, Interakt and Wati guides.

04

Contact and call fields you can send

The step replaces these with each contact's values when it sends. Call fields come from the nearest Call step above it. In the builder, click a field chip to insert it where your cursor is.

{{callee_name}}
Contact name from your list or lead form
{{callee_number}}
Number with country code: +919876543210
{{callee_number_local}}
Number without country code: 9876543210
{{call_status}}
"completed" when they answered
{{summary}}
Short summary of the call
{{call_duration}}
Call length in seconds
{{call_id}}
Vyora call id, handy as a reference in your provider
{{answer.<field>}}
A Post-Call Analysis answer, e.g. {{answer.visit_date}}
{{<column>}}
Any extra column in your contact list
05

Two ways to connect

Workflow (recommended)
Call webhook + Zapier / Pabbly
Vyora plan
Business
Any plan
Missed calls only
Yes, with "They didn't answer"
Filter on the status field in Zapier / Pabbly
Extra tool
None
Zapier, Pabbly or Make
API key lives in
Vyora
Your automation tool
Setup
This guide
Settings → Integrations → Webhook, payload in the API docs

With the webhook, Vyora posts each finished call to your Zapier "Catch Hook" or Pabbly webhook trigger with phone_number, contact_name, status and analysis.summary. Add a filter, then your provider's "send template" action.

06

Template tips for call follow-ups

  • — Say who you are and why you called in the first line: "Hi {{1}}, this is Sharma Realty. We just tried calling about your 2BHK enquiry."
  • — Give one easy action: "Reply YES for a callback" or a button. Replies land in your provider's inbox.
  • — Write it in the language of the call. A Hindi call followed by a Hindi template reads as one conversation.
  • — Meta sets the template category when it reviews it. Promotional wording (offers, discounts) makes it a marketing template, which costs more per conversation than a utility one.
07

Frequently asked questions

Does Vyora send WhatsApp messages itself?

No. Vyora places the AI voice call. The WhatsApp message goes out from your own WhatsApp Business API provider (AiSensy, Interakt, Wati or any other with an HTTPS API), from your number, using a template Meta has approved. Vyora calls that provider for you right after the call.

Which Vyora plan do I need?

The Workflow route uses the "Send to another app" step, which is on the Business plan. On any plan, you can use the call webhook (Settings → Integrations) with Zapier or Pabbly in between.

Can I message only the people who did not pick up?

Yes. Put an If / else step after the Call step with the condition "They didn't answer" and the WhatsApp step on its Yes branch. You can add "They hung up quickly" to the same rule so very short calls get the message too.

Can the WhatsApp message use what was said on the call?

Yes. A template variable can take the call summary or any Post-Call Analysis answer the agent collects, such as a preferred visit date or a budget. Meta does not allow line breaks inside template variables, so keep those values to one line.

Who pays for the WhatsApp messages?

Your WhatsApp provider bills you for the conversation, the same as for any template you send from their dashboard. Vyora charges only for the call.

My provider is not AiSensy, Interakt or Wati. Will it work?

If it has an HTTPS API that sends a template with a JSON request (Gupshup, Gallabox, Kaleyra, Meta's own Cloud API and most others do), the same step works. Put its address, auth header and JSON body in the step and use the contact fields listed on this page.

Related

We use cookies to improve your experience. By continuing to use this site, you agree to our Privacy Policy.