Lead questions on WhatsApp
A prospect writes in the evening. The agent answers from the approved source, collects the name and the need, writes the lead on the record, and flags it for a person.
In short. Aiwah Labs builds AI chatbots for WhatsApp and web chat. The bot answers from sources you approve, takes bookings or qualifies leads, writes the result into your CRM, and hands the thread to a person when it is unsure. Setup starts at $299, and a defined flow is live in about 3 days.
Available inBengaluruDubaiLondon, Ontario

AI chatbot implementation puts a chat agent on WhatsApp, your website or another channel your customers already use. It answers from sources you approve and takes only the actions you allow, such as logging a lead, moving a booking or opening a ticket.
A widget that only talks leaves your team retyping. We tie the chat to the booking, order or support record and design the handover, so a person gets the whole thread when the bot is unsure. For the wider operation, see customer lifecycle.
Writes on web chat or WhatsApp, the channel they already use.
Answers in the thread and collects the fields the record needs.
Quotes only approved pages and policies. Writes the result to your record.
A person gets the whole thread when the agent is unsure.
Scenarios the setup is built around. Each one ends in a record or a person, not a dead end.
A prospect writes in the evening. The agent answers from the approved source, collects the name and the need, writes the lead on the record, and flags it for a person.
Customers change or cancel in the thread they ordered in. The agent updates the record where it may, and hands over where it may not.
Repeated questions get answered from the pages and policies you approved. Anything else reaches a person with the whole thread attached.
The bot sits on the channels your customers already use and writes into the systems your team already works in.
WhatsApp and web chat are the usual pair. Instagram, Messenger, Telegram or SMS can be added where you hold the account. Hand-offs reach your team in Slack, Teams or email.
The prompts, the approved sources and the thread history stay with you. The models underneath are chosen per flow and can be swapped later.
A reply that books, qualifies or opens a ticket lands in your CRM, helpdesk, store or booking system. If you have no record yet, we build a private one you own.
Prices, discounts, delivery slots and legal or medical claims come from a source you approved, or from a person. The bot hands over instead of guessing.
Hello, is the Saturday slot still open? I would like to change my order.
Yes, I can update that. Please send the order number and the day you prefer.
Order 4821. Sunday instead.
I cannot confirm Sunday delivery myself. I am passing this to a colleague now, with your order attached.
Thread and order 4821 attached.
Live in about 3 days. For a defined flow. Extra channels or integrations add time, which we scope on the discovery call.
A lead, an order change or a support case that someone retyped by hand. That thread becomes the first flow.
We list the pages, prices and policies the agent may quote. Anything off the list becomes a handover.
WhatsApp, the web widget or both, plus the system that receives the structured request.
A missing price, an angry message and a question outside the source all get tested. Each one should reach a person with the thread attached.
A defined flow is usually live in about three days. Customers keep writing where they already write.
Prices are in US dollars and exclude taxes. They are one-time setup, not a subscription.
Usage is passed through at provider cost: LLM tokens and WhatsApp or other messaging fees. We add no markup.
Bring one call, thread or workflow. We scope from there.
Book a callIntegrations
Customers write where they already write. The bot answers there, then books, quotes or opens the record in the system your team works in.
If your system lets data in or out, we connect to it. If it does not, we find a workaround, and we tell you how dependable that route is before we build. We also connect WhatsApp accounts on Gupshup, Interakt or WATI, SMS, Freshdesk, LeadSquared and your ordering or booking system.
The clean route. Most modern tools have one, and many older ones do too.
No API? We read the database, or a scheduled CSV or SFTP export.
We pick up the reports, invoices and attachments your system already sends.
For a portal with no other way in, a bot works the screen the way your team does, with every step logged.
Local pages cover the rules, languages and prices where you operate.
These are published patterns. They are not a claim that the client is in a particular city.
Case study, FlavoBoxFlavoBox brought 1,000+ WhatsApp threads into one delivery operation without forcing customers into an appWhatsApp stayed the customer channel while each order became a record the kitchen could run.
EssayWhat a WhatsApp lead agent should actually doWhat a WhatsApp agent should capture before a person takes the lead.A chatbot answers in a channel. An agent, as we build it, can also take an allowed action in your system and stops when it is unsure. The practical difference is the record and the handover.
Yes, through the WhatsApp Business API. Customers stay in the thread they already use. WhatsApp bills each delivered message at Meta’s rate for that country and message type, and we pass that cost through unchanged.
It quotes only what an approved source says. A price, discount or delivery slot that is not in that source becomes a handover. We test that boundary before launch.
It retrieves from the documents and records you mark as approved. We do not paste your archive into a consumer chat account. The model provider processes each request under its own terms, which we list before build.
A defined flow is usually live in about three days. Extra channels or integrations add time, which we scope on the discovery call. Setup is one-time: Starter from $299, Growth from $799 and Scale from $1,599. Messaging and model usage are billed at provider cost.
The languages your customers write in, tested on your own chat history before launch. That is often Kannada, Hindi and English in India, Arabic and English in Dubai and the UAE, and English and French in Canada.
In your own cloud account, in a region you choose, with a retention rule you set. WhatsApp and the model provider process messages under their own terms.
A person gets the thread, the customer history the channel holds and the reason the bot stopped. The customer does not repeat the story.
You do: the flows, prompts, approved sources and thread history we set up. The messaging and model accounts can sit in your name. There is no vendor lock-in.
Tell us the call, the thread or the record. Every setup on this page starts with a call.
Book a call