AI chatbot development Website, WhatsApp, in-app

AI chatbots that answer from your data, then hand over.

A chatbot that makes up an answer is worse than no chatbot. I build support and sales bots that answer from your real docs, products and order status, know when to stop, and pass the chat to your team with the full context.

Sample conversation, for illustration.
12 minfirst response, down from 4 hours
50+workflows and bots shipped
RAGgrounded in your own docs
30 daysof free fixes after launch
In short

AI chatbots with Hammad

Who it's for
Brands answering the same customer questions all day, on chat, email or WhatsApp.
What you get
A support or sales bot grounded in your content, wired to your store and CRM, with a human handover.
Timeline
Launches supervised: a person approves replies while we tune it on real chats.
Price
One fixed build price after a free 30-minute call. Model usage is sized to your traffic first.
Why bots fail

Most chatbot projects fail for the same two reasons

01

It makes things up

A bot wired straight to an AI model will answer confidently about a policy it has never seen. Customers believe it, and you inherit the promise. The fix is retrieval and a confidence threshold, not a longer prompt.

Can I return an opened item?
Typical bot

Yes! Any item, any time, no questions asked.

Made up
Built right

Unopened items within 30 days. For opened ones, I'll check with the team.

From returns-policy.pdf
02

It's a dead end

The bot can't answer and there's no route to a person, so the customer repeats themselves three times and leaves angry. Handover decides whether people trust the thing at all.

I was charged twice.
Typical bot

Sorry, I didn't get that. Can you rephrase?

Loop
Built right

I'm passing this to a person now. They'll see this chat and your payment.

Handed over
How it answers

Every reply has to clear a bar

  1. 1Customer asksOn your site, WhatsApp, Messenger or in your app.
  2. 2Looks it upHelp docsProduct cataloguePast ticketsOrder status
  3. 3Confidence checkIs there a real source for this answer?
YesAnswers, with the sourceReplies cite something real from your content.
NoHands over to a personTo Slack, your helpdesk or email, with the transcript and customer record attached.
Channels and stack

One brain, different front doors

Built once, not three times. And wired into the tools your team already uses, because a bot that can't read order status can't answer the question people actually ask.

Where customers talk to it
  • Website widget
  • WhatsApp Business
  • Messenger
  • Inside your product
What it reads and writes
  • Shopify orders
  • HubSpot or your CRM
  • #Slack for handovers
  • @Your helpdesk
What I build

Six bots that earn their keep

Order status

Reads live Shopify and 3PL data to answer "where is my order?" without a ticket ever being opened.

Support draft replies

Drafts each reply for a person to approve. One client's first response went from 4 hours to 12 minutes.

Product finder

Asks two or three questions, then recommends from your real catalogue, never an invented product.

Lead qualification

Scores the enquiry, books the call and writes the CRM record before anyone opens their laptop.

Internal docs assistant

Answers your team's questions from your own handbook and process docs, with the source linked.

Escalation with context

Your person gets the transcript and the customer record together, not a cold "user needs help".

Proof, not promises

I run my own AI support product

Tendabot is the AI support agent I built and run: one bot for your website, WhatsApp and email, with every chat in one inbox and a person able to take over any of them.

3channels, one inbox
Freeto start
See Tendabot
Tendabot homepage
How it works

Supervised first, then on its own

  1. 1

    Question audit

    What people actually ask, and whether the content exists to answer it.

  2. 2

    Scope and model

    Which model, where the handover line sits, one fixed price.

  3. 3

    Build and ground

    Retrieval over your content. Escalation paths built before the happy path.

  4. 4

    Supervised launch

    A person approves replies while we tune on real chats.

  5. 5

    Review loop

    30 days of free fixes and a weekly look at what it got wrong.

FAQ

Chatbot questions, answered

How do you stop the bot making things up?

Retrieval plus a threshold. The bot answers from your own documents, not from the model's memory, and every answer has to clear a confidence bar before it's shown. Below that bar it says it doesn't know and hands over.

What does an AI chatbot cost to build and run?

The build is one fixed price, quoted after a free 30-minute call. Running costs are model usage, usually $30 to $200 a month depending on volume, and I size that against your real traffic before you commit.

Which model do you use?

The cheapest one that clears your quality bar. Claude for a nuanced support tone, a smaller model for high-volume sorting, open-source and self-hosted if data can't leave your servers. I have no reason to prefer one vendor.

Will my customer data go to an AI provider?

For most builds, yes: that's how the APIs work. Anthropic and OpenAI both offer terms that keep your data out of training, and I set those up. For legal, medical or financial use, I can self-host an open model so nothing leaves your servers.

Can it hand over to my team?

Yes, and I wouldn't build one that couldn't. Handover goes to Slack, your helpdesk or email with the full transcript and customer record attached, so nobody starts from zero.

Taking new projects

Want a bot customers trust? Let's talk.

A free 30-minute call. I'll tell you whether your content is ready to ground a bot, and what it would take if not.

Book a chatbot call
Prefer email?hello@hammadshahzad.com