Skip to content

AI chatbot development

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

Kitchen staff preparing orders at a commercial kitchen pass
Starting price
$299
One-time setup, in US dollars. Usage at provider cost.
Typical timeline
3 days
For a defined flow. Extra channels or integrations add time, which we scope on the discovery call.
You own
Code and data
Plus the prompts and the accounts set up for you.

What is AI chatbot implementation?

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.

  1. Customer

    Writes on web chat or WhatsApp, the channel they already use.

  2. Chat agent

    Answers in the thread and collects the fields the record needs.

  3. Approved sources and CRM

    Quotes only approved pages and policies. Writes the result to your record.

  4. Handover

    A person gets the whole thread when the agent is unsure.

How one message moves through a chat agent, and where a person takes over.

Where it helps.

Scenarios the setup is built around. Each one ends in a record or a person, not a dead end.

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.

Order and booking changes

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.

First-line support

Repeated questions get answered from the pages and policies you approved. Anything else reaches a person with the whole thread attached.

What we build.

The bot sits on the channels your customers already use and writes into the systems your team already works in.

Channels

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.

Your sources, your history

The prompts, the approved sources and the thread history stay with you. The models underneath are chosen per flow and can be swapped later.

Your system of record

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.

Approved answers only

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.

Your businessWhatsApp thread
  1. Customer:

    Hello, is the Saturday slot still open? I would like to change my order.

  2. Chat agent:

    Yes, I can update that. Please send the order number and the day you prefer.

  3. Customer:

    Order 4821. Sunday instead.

  4. Chat agent:

    I cannot confirm Sunday delivery myself. I am passing this to a colleague now, with your order attached.

  5. Handed to a person:

    Thread and order 4821 attached.

Illustrative example. Not a real conversation.

From one real case to a live path.

Live in about 3 days. For a defined flow. Extra channels or integrations add time, which we scope on the discovery call.

  1. Day 1First working session

    Bring one real thread

    A lead, an order change or a support case that someone retyped by hand. That thread becomes the first flow.

  2. Day 1Design, before build

    Mark the approved sources

    We list the pages, prices and policies the agent may quote. Anything off the list becomes a handover.

  3. Day 2Build

    Connect the channel

    WhatsApp, the web widget or both, plus the system that receives the structured request.

  4. Days 2–3Test, before launch

    Test the unsure cases

    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.

  5. Day 3Launch

    Go live on the channel customers already use

    A defined flow is usually live in about three days. Customers keep writing where they already write.

Setup, priced once.

Prices are in US dollars and exclude taxes. They are one-time setup, not a subscription.

Starter

From$299One-time setup
  • One channel, web chat or WhatsApp
  • One conversation flow tied to a booking, order or support record
  • Answers limited to an approved source you provide
  • Handover to a person, with the thread attached, when the agent is unsure
Book a call

Growth

From$799One-time setup
  • Web chat and WhatsApp
  • Up to three flows
  • One integration, such as a CRM, calendar or shared inbox
  • Handover with the conversation attached
  • A review queue for replies the agent was not allowed to send
Book a call

Scale

From$1,599One-time setup
  • Web, WhatsApp and one further channel you already use
  • Several flows on one customer record
  • Up to three integrations
  • Handover, a record of what the agent said, and a review queue
  • The same limit to approved sources as the smaller tiers
Book a call

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 call

What you own at the end.

You own

  • The chat flows and their logic
  • The prompts and the list of approved sources
  • The thread history we set up, subject to the channel and model providers’ own terms
  • The messaging and model accounts, which can sit in your name
  • The build itself, with no vendor lock-in

Controls that stay in place

  • The agent answers from approved sources. It never invents a price or a promise.
  • When it is unsure, a person gets the thread with the history attached.
  • Consent and retention follow the rules where your customer is. Each city page sets out the local rule we design against.
  • Model and messaging usage is billed by the provider at cost. The setup tiers are one-time.

Integrations

Every channel in. Every system out.

Customers write where they already write. The bot answers there, then books, quotes or opens the record in the system your team works in.

Messaging channels

  • WhatsApp
  • Instagram
  • Messenger
  • Telegram

Your website or store

  • WordPress
  • Shopify
  • WooCommerce
  • Magento
ChatbotApproved answers, then the right record

CRM and helpdesk

  • HubSpot
  • Salesforce
  • Zoho
  • Zendesk
  • Intercom

Orders and payments

  • Shopify
  • Stripe
  • Razorpay
  • PayPal

Bookings

  • Google Calendar
  • Calendly

Hand-off to your team

  • Slack
  • Microsoft Teams
  • Gmail
Examples, not the full list. Logos do not imply a partnership with their makers.

Not on the list? We still connect it.

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.

  1. API or webhook

    The clean route. Most modern tools have one, and many older ones do too.

  2. Database or export

    No API? We read the database, or a scheduled CSV or SFTP export.

  3. Email and shared folders

    We pick up the reports, invoices and attachments your system already sends.

  4. Screen automation

    For a portal with no other way in, a bot works the screen the way your team does, with every step logged.

How we approach integrations →

In your market.

Local pages cover the rules, languages and prices where you operate.

Straight answers.

What is the difference between a chatbot and an AI agent?

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.

Can the chatbot run on WhatsApp?

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.

How does it avoid making up prices or promises?

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.

How is it trained on our documents?

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.

How long does a chatbot take, and what does it cost?

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.

Which languages does it support?

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.

Where is chat data stored?

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.

What happens when the chatbot is unsure?

A person gets the thread, the customer history the channel holds and the reason the bot stopped. The customer does not repeat the story.

Who owns the chatbot?

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.

Bring one workflow.

Tell us the call, the thread or the record. Every setup on this page starts with a call.

Book a call