Create WhatsApp chatbot
Production AI that grounds answers in your data
- Senior engineers · IST + EST overlap
- NDA on day 1
- 24-hour reply
Tell us what you need fixed
Reply in 24 hours · NDA on day 1 · No spam.
Create WhatsApp chatbot — done properly, by senior engineers
We create WhatsApp chatbot flows on the WhatsApp Business Platform’s Cloud API for customer support, lead capture and ordering, and take care of the Meta setup that stalls most teams. Going live involves more than code: a Meta Business portfolio, business verification to raise messaging limits, a phone number registered to the API, an approved display name, a payment method, and message templates that pass Meta’s review. The platform also has rules a web chatbot never meets. Free-form replies are allowed only inside the 24-hour customer service window that opens when a customer messages you; outside it, you need an approved template in the marketing, utility or authentication category, and proactive messages require the customer’s opt-in. Krapton’s engineers build the webhook service that receives messages and delivery statuses, verifies Meta’s request signatures, acknowledges quickly and processes work asynchronously, with deduplication by message ID. Conversations use reply buttons, list messages and WhatsApp Flows for multi-step forms, plus catalog messages where ordering applies. Agents take over in your shared inbox or helpdesk, and leads sync to your CRM. Your team inherits the running service, the approved template library and a runbook for watching the number’s quality rating and messaging limits.
What you're seeing
You want a WhatsApp chatbot for customer support, lead capture, or ordering — but the Cloud API is a maze.
Our approach
We onboard you to the WhatsApp Cloud API, build the flow with template messages, and integrate with your CRM and support stack.
Symptoms teams come to us with
- Customers already message a staff phone, so every reply depends on one person and one device.
- Template messages get rejected in Meta’s review, and nobody knows which rule they broke.
- Order updates fail to send because the customer’s last message falls outside the service window.
- Production still runs on the temporary access token from Meta’s test screen, and it keeps expiring.
- Leads captured on WhatsApp never reach the CRM, so sales follow up from screenshots.
What we get right
- Free-form messages sent outside the 24-hour customer service window, where only approved templates are allowed.
- Templates submitted under the wrong category, or with promotional wording inside a utility message.
- Webhook handlers doing slow work before responding, causing redelivered events and duplicate replies.
- One number used for both promotions and support, so complaints about marketing lower its quality rating.
- Temporary access tokens used in production instead of a system user token with the needed permissions.
Concrete deliverables, no fluff
Every engagement ends with measurable, documented outcomes — no black-box agency reports.
- Use-case discovery + dataset prep
- RAG-grounded prototype on your knowledge base
- Production rollout with guardrails + analytics
- Cost-control + escalation runbook
What changes after we ship
Meta onboarding handled end to end
Business portfolio, verification, phone number registration, display name approval and a system user token with the right permissions, documented so your team can manage the account later.
WhatsApp templates written for approval
Marketing, utility and authentication templates written to Meta’s guidelines, with variables, buttons and opt-out wording where needed, then submitted and tracked through review.
A webhook service built for retries
Signature checks on every request, fast acknowledgment, queued processing and deduplication by message ID keep replies single and conversations consistent, even when Meta redelivers events.
Handoff to agents and CRM
Conversations move to agents in Chatwoot, Zendesk, Freshdesk or Intercom when the bot reaches its limits, and leads arrive in HubSpot or Salesforce with the full chat attached.
From brief to shipped fix
A transparent, low-risk process — a senior engineer reads your brief personally, and nothing starts until you approve a written plan and price.
01
Diagnose
A senior engineer reviews your brief, reproduces the issue, and pinpoints the real root cause — not the symptom — before any code is touched.
02
Scoped plan & quote
You get a written plan to create WhatsApp Chatbot, a firm timeline, and a fixed quote. Nothing starts until you approve it — no surprise invoices.
03
Ship the fix
We implement on a branch and open a pull request you review, working to your code-review standards on your repo — never a black box.
04
Verify & hand off
We verify on staging and production, share before/after evidence where it applies, and leave you a short hand-off note so the fix sticks.
Situations we handle
Order updates for D2C brands
Shipping confirmations and delivery updates go out as utility templates, and replies about returns or exchanges are answered by the bot or routed to the support inbox.
Lead capture from click-to-WhatsApp ads
Ads that open a WhatsApp chat start a qualifying conversation. A WhatsApp Flows form collects budget, timeline and requirements, and the lead lands in your CRM with the ad source attached.
Appointment booking and reminders
Clinics, salons and service businesses let customers pick a slot inside WhatsApp, receive confirmation instantly and get reminder templates before the visit, with rescheduling handled in the same chat.
Why teams hand this task to Krapton
Senior engineers only
Your brief is read and handled by a senior engineer — no junior hand-off, no sales-rep filter in between.
Root cause, not a patch
We reproduce and fix the underlying cause, then add a guard so the same class of issue does not quietly return.
Your repo, your standards
Every change lands as a pull request you review, on your repository, following your existing review process.
NDA on day one
Confidentiality and IP are covered before we look at a single line of code. All work stays in your accounts.
Fixed quote up front
You approve a written plan and price before work starts. If scope changes, we re-quote in writing — no surprise invoices.
Proof, where it applies
Performance, SEO and reliability work ships with before/after evidence so the result is measurable, not anecdotal.
Three ways to engage
No retainer required. Pick the model that matches the work — pricing for this task starts from $500, with a fixed quote before anything starts.
Per task
Most popular
One clearly-scoped fix at a fixed price. Best when you know exactly what is broken and want it handled end to end.
- Fixed quote up front
- One PR, reviewed by you
- No retainer required
Hourly
Pay only for the hours worked. Best for diagnostics, audits, or exploratory work where the scope is still emerging.
- Weekly timesheets
- Pay for what you use
- No minimum commitment
Per sprint
A focused 1–2 week sprint when the work is bigger than one fix but smaller than a full project.
- 1–2 week blocks
- Clear sprint goal
- Scale up or stop anytime
Industry-standard stack, no proprietary lock-in
Create WhatsApp chatbot — your questions, answered
How much does it cost to create WhatsApp Chatbot?
Pricing starts from $500 and depends on the scope we find during the diagnostic. You get a fixed, written quote before any work begins — most engagements like this run 2–6 weeks.
How long does it take to create WhatsApp Chatbot?
Typically 2–6 weeks for a focused engagement. After a short diagnostic we commit to a firm timeline so you know exactly what to expect.
What do we need to create WhatsApp chatbot flows on the Cloud API?
A Meta Business portfolio, a phone number that can receive a verification code by SMS or voice call, a display name that follows Meta’s guidelines, and a payment method on the WhatsApp Business Account. Business verification raises messaging limits. We set up a system user token, webhooks and templates, and build against Meta’s test number before your real number goes live.
Can the bot message customers first, for example with order updates?
Yes, with an approved template and the customer’s opt-in. Business-initiated messages outside the 24-hour customer service window must use templates in the marketing, utility or authentication category, and Meta prices template messaging by category and the recipient’s country. Inside the window, after a customer writes to you, the bot can reply freely.
Do we need a provider like Twilio, or can you connect directly to Meta?
Either works. Connecting directly to the Cloud API avoids an extra party and its fees, and Meta hosts the infrastructure. A business solution provider such as Twilio, Infobip or 360dialog adds tools like shared inboxes, analytics and support contracts, which helps if you lack in-house engineers. We keep the integration portable so you can switch later.
Keep exploring
Related tasks and resources to plan your next step with Krapton.
Let's get this off your plate
Send a 60-second brief on Create WhatsApp Chatbot and a senior engineer replies within 24 hours with a plan and a fixed quote. NDA on day one, no retainer required.