Truvest Truvest Sign in
All posts Guide

How to Build a WhatsApp Chatbot Without Writing a Single Line of Code

T
Truvest Team
13 Apr 2026 · 4 min read

If you've been told building a WhatsApp chatbot needs a developer, an agency, or a 6-month project — that's outdated.

In 2026, you can have a working chatbot live in 60 minutes, with zero code. Here's exactly how.

What you need before you start

  1. A phone number that's NOT linked to a personal WhatsApp account (the most common gotcha)
  2. A Meta Business Account (free, takes 10 minutes)
  3. A no-code chatbot platform — we'll use Truvest as the example
  4. One piece of content to ground the bot: a brochure, FAQ doc, or product list

That's it.

Step 1: Get the WhatsApp Cloud API connected (15 mins)

The WhatsApp Cloud API is Meta's official API for business automation. Don't confuse with the WhatsApp Business app (which won't work for bots).

  1. Go to developers.facebook.com
  2. Create a new App → choose "Business" → enable WhatsApp product
  3. Add your phone number → verify via OTP
  4. Copy the Phone Number ID, WABA ID, and System User token
  5. Paste these into Truvest → Settings → WhatsApp → Save

Verified ✓. You can now send messages programmatically.

Step 2: Define your bot's purpose (5 mins)

Before adding features, write one sentence:

"When someone messages [my business] on WhatsApp, the bot should help them [do X] without involving me."

Examples:

  • "...help them book a site visit at one of my projects."
  • "...help them get a quote for plumbing service."
  • "...help them check class timings and enroll in a batch."

The more specific, the better the bot.

Step 3: Upload your knowledge base (10 mins)

This is where AI chatbots become powerful.

In Truvest → Settings → AI Data Sources:

  • Upload your brochure / price list / FAQ as PDF
  • Paste your website URL (the bot crawls it)
  • Optionally: paste a list of common Q&A

The AI will use this content to answer customer questions accurately, instead of making things up.

Step 4: Set the bot's persona (5 mins)

In Truvest → Settings → AI Bot:

  • Tone: friendly / professional / casual
  • Language: English / Hindi / multilingual
  • Off-limits topics: pricing of competitors, refunds, etc.
  • Handoff trigger: "if the customer asks about X, route to a human"

Save. The bot now sounds like your brand.

Step 5: Test in a real WhatsApp chat (10 mins)

Send your business number a few real questions a customer would ask:

  • "What are your prices?"
  • "Where is your office?"
  • "Can I get a sample?"
  • "What's your refund policy?"

Watch the responses. If any are wrong → go back to step 3 and add more content.

Step 6: Set up the lead capture flow (10 mins)

When the bot can't fully answer, it should collect contact info:

  • Name
  • Phone (already known from WhatsApp)
  • Best time to call back
  • Specific need

This becomes a lead in your CRM.

Step 7: Go live (5 mins)

  • Add the WhatsApp button to your website
  • Add it to your Instagram / Facebook profile
  • Update your Google Business Profile with the WhatsApp number
  • Send your team a heads-up: "leads will start coming in via WhatsApp"

Done. You have a 24/7 sales chatbot running.

Common mistakes to avoid

  1. Skipping the knowledge base upload → bot sounds generic
  2. Trying to handle every scenario on day 1 → ship simple, iterate
  3. Not setting up handoff to humans → bot frustrates power users
  4. Forgetting to log conversations → you can't improve what you can't measure
  5. Using a personal phone number → Meta will block you

What "good" looks like after 30 days

  • 60-80% of inbound conversations resolved without human
  • Customer satisfaction (CSAT) ≥ 4 / 5
  • Lead capture rate ≥ 30% on chatbot conversations
  • Owner's WhatsApp inbox volume drops by half

If you don't hit these, the bot needs more content, not more features.


Want to skip the setup? Truvest's WhatsApp Chatbot runs all of the above in one platform — official Cloud API, knowledge-base upload, AI replies, lead capture, CRM. Free 15-day trial.

Share this post