WhatsApp Chatbot for Business: One Part of a Lead System That Works
A chatbot is the front door, not the sales desk. Webbtex builds custom WhatsApp chatbots that collect the right details, qualify the lead and hand over with a summary, then keeps them working after launch.
Built around your workflow.
Where whatsapp chatbot breaks down
An enquiry reaches Whatsapp Chatbot from WhatsApp, a website form, advertising, email or social media, but it arrives without the information needed for the next action. Staff ask questions in different ways, forward screenshots without context and assume somebody else owns the reply. Documents or photos remain in separate channels, the responsible person receives an incomplete handover, and follow-up depends on memory. Management cannot see where the request stalled, what was promised or whether the opportunity reached a useful outcome.
- Enquiries for Whatsapp Chatbot arrive without enough context for the next action
- Staff collect different information for similar requests
- Ownership changes without a recorded handover
- Documents, photos and customer details are scattered across channels
- After-hours enquiries wait without a clear next step
- Follow-up depends on individual memory instead of a visible process
- Management cannot see where enquiries are getting stuck
Situations the workflow must handle
- A new Whatsapp Chatbot enquiry contains only a name and a short request
- A staff member forwards a message but leaves out the information needed to act
- A quote or booking request needs photos, documents or scope before review
- An urgent request sits beside routine questions in the same queue
- Two team members follow up because ownership was never recorded
Why an auto-reply is not enough
A greeting can acknowledge a message, but it cannot decide who owns the enquiry, collect the right context for Whatsapp Chatbot, apply the company rules, prepare a useful handover, connect the request to existing tools, manage multi-step follow-up or show management where work is getting stuck.
A system for whatsapp chatbot
A Webbtex chatbot is designed backwards from the handover. We sit with the people who actually close enquiries and ask what they need to know before they can quote, book or call. For a dealership that might be the vehicle, budget, trade-in and timing. For a dental practice it is the treatment, medical aid, preferred branch and urgency. Those become the chatbot's questions, in that order, and nothing else is asked.
The conversation is written to be short and tolerant. People answer in their own words, so the chatbot is built to understand a budget typed as a sentence, an address given as a suburb, or a photo sent instead of a description. When someone does not fit the expected path, such as a bulk order or a language the flow was not written in, the chatbot stops guessing and hands over immediately rather than looping. Every path ends with a person.
Qualification happens quietly. Based on the answers, the enquiry is scored and tagged, then routed to the right desk: the salesperson for that product, the branch for that suburb, the on-call number for an emergency. The handover message gives the staff member a three-line summary and the full transcript underneath, so the first human reply is a useful one. Outcomes flow into your CRM, Google Sheet or calendar without retyping.
Launch is the start of the work rather than the end. Webbtex watches where people drop off, rewrites questions that confuse, adds answers for things customers keep asking, and adjusts routing as staff change. We send you a short report on what the chatbot is capturing and where leads go. You never edit the chatbot yourself, and it does not quietly decay into the version that was live on day one.
- 01Whatsapp Chatbot trigger identified and recorded
- 02Approved questions selected for the situation
- 03Required information captured in a consistent format
- 04Completeness, urgency and exceptions checked
- 05Correct owner selected using company rules
- 06Task, quote brief or booking request prepared
- 07Human alerted with the full handover context
- 08Follow-up triggered at the approved time
- 09Outcome recorded and visible to the team
Human handover rule
A Webbtex chatbot hands over on three triggers. First, when the qualifying questions are complete, the lead goes to the assigned desk regardless of score, because a low-scoring enquiry is still a person who deserves a reply. Second, the moment a customer asks for a human in any wording, the chatbot stops and routes them. Third, when an answer falls outside what the chatbot was built for, such as a bulk request, a complaint or a language it does not cover, it hands over immediately rather than attempting a guess.
The staff member receives a three-line summary of who the person is, what they want and how urgent it is, followed by the full conversation. They reply in the same thread, so the customer is not moved to a new number or asked to start again. If the first person does not respond inside the window you set, the lead escalates to the next desk and the delay is logged for review.
What the system may connect
Depending on the workflow, Webbtex can connect the channels and tools required to move information to the right person. Connections are scoped after the current process and technical requirements are confirmed.
- Website forms
- Facebook or Instagram enquiries
- Google Ads landing pages
- CRM
- Google Calendar or Microsoft 365
- Spreadsheets
- Internal dashboards
- File storage
- Quoting or booking systems
- Staff notifications
Information and decisions
Information captured
- Customer name and preferred contact details
- Service or help required
- Area or relevant location
- Urgency and preferred timing
- Scope, budget or qualification information where appropriate
- Photos, documents or supporting details where required
- Source of the enquiry
Decisions made by the workflow
- Which department or staff member owns the enquiry
- Whether urgent human escalation is required
- Whether more information is needed before handover
- Whether the request is ready for a quote, booking or consultation
- When follow-up should occur and who is responsible
Done-for-you implementation
Webbtex completes the workflow design, configuration and implementation with the client team.
- Understand the current process
- Identify the leak or bottleneck
- Map the desired workflow
- Design the rules and handovers
- Connect the relevant channels and tools
- Test using real enquiry scenarios
- Launch with the client team
- Review and improve the system
Best fit
Webbtex is most useful where the operational cost of a missed, incomplete or badly handed-over enquiry is meaningful.
- Whatsapp Chatbot already paying to generate enquiries
- Teams receiving repeated questions or requests
- Businesses with several staff members, departments or branches
- Quotes or bookings that require several pieces of information
- Operations with manual handovers and weak follow-up visibility
- Businesses whose current tools do not connect cleanly
Questions about this workflow
What should a WhatsApp chatbot for business actually do?
Collect the details your sales desk needs, qualify the enquiry, and hand it to the right person with a summary. It should not try to replace the salesperson. Webbtex builds chatbots to do that narrow job well and connects them to the tools your team uses.
Why do DIY chatbot tools stall after launch?
Because the build is the easy part. Deciding the right questions, wording them for South African customers, connecting to a CRM and fixing drop-off points after launch all take time nobody on your staff has. Most DIY chatbots stay at version one until they are switched off.
Can the chatbot answer questions about our products and prices?
It can answer a defined set of common questions you approve, such as opening hours, areas served or what to bring. Anything specific to stock, availability or a custom price is handed to a person, because a wrong answer costs more than a short wait.
How does the chatbot know who to send a lead to?
By rules agreed with you: product line, suburb or branch, urgency, language, or who is on shift. Those rules are built into the handover, and Webbtex adjusts them as your team changes.
What does a custom WhatsApp chatbot cost?
Builds start from R15,000 once-off, with care and optimisation from R2,500 a month. Meta's conversation charges are billed separately. The price depends on how many desks, questions and integrations the chatbot needs, not on message volume.
Will the chatbot handle Afrikaans, isiZulu or other languages?
It can be written in the languages your customers use and can offer a choice at the start. Where a customer writes in a language the flow was not built for, it hands over to a person rather than guessing.
Does Webbtex build on the official WhatsApp API?
Yes. Every chatbot runs on the WhatsApp Business Platform from Meta, which is what allows multiple staff, routing, integrations and reliable delivery. Your existing business number can usually be moved onto it.
Can we try the chatbot before deciding?
Yes. Message Webbtex on WhatsApp and the conversation you have is built the same way we build for clients. If it collects your details and hands over cleanly, that is the demonstration.
Whatsapp Chatbot should become a controlled workflow, not another message staff must remember.
Show us where enquiries, admin or handovers are breaking down. Webbtex will map the workflow and recommend the system that should be built.