# AI chatbot development services for support and ordering

AI chatbot development is building a conversational assistant that answers customers, takes orders or resolves support requests in your own channels. Goldenroz builds customer support chatbots and ordering bots for WhatsApp, web and mobile apps, connected to your order, CRM and help content. Projects start at $25,000, fixed price per phase. A working prototype typically takes one to two weeks, and production roughly four to eight weeks depending on integrations.

**From $25,000, fixed price per phase**

Updated: 2026-11-13. By Shai Goldenberg.

## Who this is for

- Support leaders whose team answers the same questions every day and who want those resolved without a person.
- Businesses that take orders or bookings by message and lose the ones that arrive after hours.
- Companies whose customers already write to them on WhatsApp.
- Product teams that tried an off-the-shelf bot and hit its limit on integrations or control.

## What is included

- **Conversation design:** The intents the bot handles, the ones it refuses, its tone and the exact point where it hands over to a person.
- **Channels:** WhatsApp through the WhatsApp Business Platform, a web chat widget, or chat inside your mobile app.
- **Knowledge base answers:** Replies drawn from your approved help content and policies. When the content does not cover a question, the bot says so and routes it.
- **Actions in your systems:** Order lookup, order creation, booking, status updates and ticket creation through your APIs. See [AI integration](https://goldenroz.com/ai-integration/).
- **Fallbacks:** A model fallback chain, timeouts and retries, plus fixed replies that go out when no model responds.
- **Handoff to humans:** Transfer to your team with the full transcript and a summary, triggered by rules, by customer request or by low confidence.
- **Logs and cost tracking:** Every conversation, tool call and model cost recorded, so you can review failures and see cost per conversation.
- **Test set:** A set of real conversations the bot must pass before every release.

## How the work runs

1. **Scoping call (Before the project):** We review real transcripts, pick the intents worth automating and agree what the bot must never do. You get a fixed price.
2. **Prototype (About 1 to 2 weeks):** A working bot on the top few intents, tested against your past conversations in a private channel.
3. **Production build (Roughly 4 to 8 weeks):** System integrations, fallbacks, handoff, logging and channel setup. The range depends on integrations and on WhatsApp account approval.
4. **Limited launch (At launch):** The bot handles a share of conversations or selected hours first. Your team reviews transcripts daily.
5. **Widen (After launch):** New intents are added in order of volume, each tested against the conversation set.

## WhatsApp chatbot development: what is different from web chat

A WhatsApp bot runs on the WhatsApp Business Platform from Meta. That brings rules a web widget does not have. Your business needs a verified account and number, messages you start outside the customer service window must use templates Meta has approved, and Meta bills messaging to your account.

The conversation is also different. Customers send voice notes, photos, locations and three short messages in a row. A WhatsApp AI chatbot has to wait, combine those messages and reply once. It has to cope with a customer who returns two days later to the same thread.

WhatsApp automation works best for ordering, booking, order status and reminders. The bot confirms the details back to the customer in plain text before it creates anything, and the order lands in the same system your staff already use.

## Fallbacks: what the bot does when the model fails

Model APIs time out, return errors and sometimes return nonsense. A customer waiting on WhatsApp sees none of that. They see a business that did not answer.

Every bot we build has three layers. The first model gets a strict time limit. If it fails, a second model takes the request. If that fails, the customer gets a fixed, pre-written reply and the conversation is flagged for a person. Retries are safe to repeat, so a retried request never creates a second order.

Rules sit outside the model where they can. Opening hours, prices, delivery zones and refund limits come from your systems. The model phrases the answer and does not decide the policy.

## AI customer service agent with handoff to humans

An AI customer service agent should resolve the routine requests and get out of the way on the rest. Handoff triggers are written down at the start: the customer asks for a person, the topic is on a restricted list, the bot has failed twice, or the request involves money above a set amount.

When a handoff happens, your agent receives the transcript, a short summary and the data the bot already collected. The customer does not repeat themselves. Outside staffed hours the bot says when a person will reply.

We do not promise a resolution rate before reading your transcripts. The share a bot can resolve depends on how many requests are routine and how much your systems expose through APIs. Bots that take wider actions across systems are covered under [AI agent development](https://goldenroz.com/ai-development/).

## What backs this up

- **A production WhatsApp ordering bot:** Shai built an ordering bot on Claude that runs in production on WhatsApp with a model fallback chain, timeouts, retries and deterministic fallback replies.
- **A support assistant with a knowledge base:** He also built a support assistant that answers from a maintained knowledge base inside a live marketplace platform.
- **Bots tied to real payments:** The platform behind those bots handles real money, with an escrow model and a double-entry ledger that uses idempotency keys.
- **A named engineer:** [Shai](https://goldenroz.com/about/shai/), our CTO, designs and builds the bot. You own the code, prompts, transcripts and accounts.

## What it costs

Each phase has a fixed price agreed before work starts. Model usage and WhatsApp messaging are billed by the providers to your own accounts.

- Support or ordering bot: From $25,000 (Fixed price per phase)
- Multi-channel or multi-brand platforms: $100,000 and up (Scoped per project)
- Scoping call: $0 (Ends with a written scope and a price)
- Model and WhatsApp usage: Paid to the providers (Billed to your own accounts)

## Who it is not for

- Budgets under $25,000. A packaged chatbot tool is the better fit.
- Voice bots and phone call centers. We build text channels.
- Bots meant to hide the way to a person. Every bot we ship has a handoff.
- Medical, legal or financial advice given with no human review.

## Questions buyers ask

### How much does AI chatbot development cost?

At Goldenroz, chatbot projects start at $25,000 and are fixed price per phase after a scoping call. Larger multi-channel platforms run $100,000 and up. Model usage and WhatsApp messaging fees are separate and paid to the providers from your accounts.

### How long does it take to build a chatbot?

A working prototype on the top few intents typically takes one to two weeks. Production takes roughly four to eight weeks, depending on how many systems the bot connects to. These are typical ranges, and each project is scoped on its own.

### Can you build a WhatsApp chatbot?

Yes. We build on the WhatsApp Business Platform, with your verified business account and number. Shai has a WhatsApp ordering bot running in production on Claude.

### What happens when the bot cannot answer?

It says so and hands the conversation to a person, with the transcript and a summary. Handoff also triggers when the customer asks for a human, when the topic is restricted or after repeated failures. Outside staffed hours the bot tells the customer when to expect a reply.

### How do you stop the bot from making things up?

Answers come from your approved content and live data from your systems. Prices, hours and policies are read from the source, and the bot declines questions the content does not cover. A test set of real conversations runs before every release.

### Which model powers the chatbot?

Claude is our default, with a second model as fallback. We also work with OpenAI models and others where they fit. The bot is built so the model can be changed without rewriting the integrations.

### Is customer data safe?

The bot can reach only the records of the customer it is talking to, enforced in the database and the APIs. Conversations are logged in your own accounts. For an existing app, a [security audit](https://goldenroz.com/security-audit/) checks what is exposed today.

### Should we buy a chatbot tool or build a custom one?

Buy when your needs are standard help-center answers on a web widget. Build when the bot must take orders, act in your own systems, run on WhatsApp with your rules, or when per-resolution pricing gets expensive at your volume. [AI consulting](https://goldenroz.com/ai-consulting/) covers that decision in detail.

---
Page: https://goldenroz.com/ai-chatbot-development/
Book a free one-hour call: https://calendly.com/daniarozin/daniel-rozin-consultation-1-hour-clone
