AI & automation
An AI chatbot answers customer questions from your own material and collects details. An AI agent goes a step further: it can look up an order, check a calendar or create a lead by calling your systems. We build both for your website and for WhatsApp, with a clear scope of what the bot may answer, a handover to your staff that carries the whole conversation, and limits on what it may do. We work with the WhatsApp Cloud API already, because BrokLeads runs on it.
The risk with a chatbot is not that it stays silent. It is that it replies confidently to a question outside its knowledge: a price you never published, a refund policy it half remembers, a promise your team can't keep. The customer believes it, because it sounds sure.
So the design starts from what the bot must not do. It answers from approved sources and says so when it can't. It hands over to a person when a customer is upset, asks for something sensitive, or asks twice for a human. Every action it can take on your systems is listed, limited and logged.
A chat widget on your site that answers from your pages and documents, captures contact details and books or routes the next step.
A conversation on a WhatsApp Business number through the official WhatsApp Cloud API, within Meta's messaging rules and your approved templates.
Tool calls into your CRM, calendar, orders or ticketing, each with its own permission, so the bot can act, not only talk.
A clean transfer to your team's inbox, with the conversation, the details collected and the reason for the handover attached.
For businesses whose customers already write on WhatsApp. We connect the official WhatsApp Cloud API, handle webhooks, message templates and the conversation window, and route the chat to a person when needed. The same kind of plumbing sits under the BrokLeads team inbox, where every chat is linked to a lead and an owner.
BrokLeads and WhatsAppA bot trained on your help pages, product documents and policies. Answers show where they came from, questions it can't answer become a ticket or a callback request, and your team gets a log of what visitors asked, which is useful content research on its own.
Every AI agents and chatbots project runs through our delivery process. These are the steps that are specific to this work. Teal steps are thinking, graphite steps are building, and orange ones keep it running.
Define the scope
What the bot may answer, what it must refuse, which channels, and the exact moments it hands over to a person.
Collect the knowledge
Your pages, policies and documents, cleaned and organized so the bot has one source of truth instead of three conflicting ones.
Build the conversation
The assistant, its retrieval over your content, its tool calls, and the guardrails that keep it inside the scope.
Wire the channels and handover
The widget or WhatsApp number, the transfer to your inbox, and the logging behind it.
Test with real questions
A set of real and awkward customer questions, run before launch and again after every change, with failures written up.
Launch narrow, then widen
Live for a limited audience or topic first. We read the conversations with you each week and widen the scope only as it earns it.
| Scope | Range |
|---|---|
| Scope, knowledge audit and test set | 1–3 weeks |
| One channel, one knowledge area, with handover | 4–8 weeks |
| Website and WhatsApp with tool calls into your systems | 2–4 months |
Planning ranges, not quotes. Your scope sets the real timeline, which we confirm in writing after discovery. See how engagements are priced.
For the background work behind a conversation: routing, CRM updates and reporting.
Our own product, built on the WhatsApp Cloud API with lead routing and a shared team inbox.
If the assistant is part of a product with accounts, tenants and plans.
How we structure the service layer a bot calls into.
It takes the repeat questions, such as opening hours, order status and where to find a document, and leaves the unusual and sensitive ones to people. We design the handover so your team gets the conversation and the context, not a customer who has to start over. How you organize your team afterwards is your decision.
The bot sends the provider only what a reply needs: the customer's message and the retrieved passages, not your whole database. We review retention and training settings with you, avoid sending identifiers where possible, and design with data minimization. Your own legal review decides if a provider is acceptable, and we make no compliance-certification claims.
It depends on how good and consistent your source material is, so we don't quote a number. We run a test set of real questions before launch and after every change. Where the bot doesn't know, it says so and offers a person, a ticket or a callback, and risky actions like changing an order or giving a quote need approval or are left to your staff.
Yes, through the official WhatsApp Cloud API, which BrokLeads uses in production for a shared team inbox. Using it means a Meta business account, an approved number and message templates for conversations you start. We check what applies to your country and use case during scoping.
You provide your documents and policies, an owner who can approve answers, and a place for handovers to land. We measure before and after: the share of questions handled without a person, handover rate, response time and the topics it fails on. Running costs are model usage, WhatsApp conversation fees charged by Meta, hosting and review time.
A builder can be the right choice for a simple FAQ bot, and we'll say so. We're useful when the bot has to read from your systems, write to your CRM, hand over inside your own inbox, or live in your product. How we differ from a freelancer: we cover the hosting, the integrations and the monitoring, not only the prompt.
Automate one repetitive workflow end to end, with an AI step only where a fixed rule cannot decide.
Learn moreCRMs, internal tools, portals and multi-tenant SaaS with roles, permissions and integrations.
Learn moreMulti-tenant subscription products: tenancy, roles, plans, admin tools, and the running of them afterwards.
Learn moreA few lines is enough. We'll ask the right questions on the call.
We reply within one working day
By email or WhatsApp, whichever you prefer.
A short call
To understand the goal, the people who'll use it and any deadline.
A written scope and estimate
Before any work starts, so you know what you're agreeing to.
Prefer to talk first?