Here are the questions we'd ask in your position, answered plainly.
What does a chatbot builder actually do all week?
- Collects a business's real questions and approved answers.
- Builds the bot in a tool (Botpress, Flowise, AI Engine on WordPress).
- Embeds it on the site or connects it to WhatsApp.
- Tests it with a written sheet of questions.
- Sets up hand-off to a human.
- Reviews chat logs and fixes wrong answers.
Writing and testing take more time than code.
What from web development carries over?
- Embedding: script tags, iframes, Content Security Policy issues, mobile layouts.
- Forms and flows: a bot conversation is a form with better manners.
- Webhooks: for hand-off to a CRM, email or a helpdesk.
- Hosting: if you self-host Flowise, it's a normal Node app to deploy.
- QA habits: edge cases, regressions, staging vs live.
Form-Field to Intent Sorter
Choose a contact form you might have built — clinic, coaching class, plugin shop. Its fields and the free-text messages people typed into it ("is parking available?", "can I reschedule?") appear as tiles. Sort them into bot intents: answer from FAQ, collect details, hand to a human. At the end you see your form turned into a chatbot plan — the exact document you'd show a first client.
Turn a contact form into a bot plan
Which tools are actually free? (checked 23 Oct 2026)
Tap a card to flip it.
AI model usage generally costs money once a bot is live. Budget for it with the client.
What should I ask a client before building anything?
- What are the ten questions your team answers most often?
- Which questions must a human always answer?
- Where do the approved answers live today (website, PDF, a person's head)?
- Which channel matters most — website, WhatsApp, or both?
- Who receives hand-offs, and during which hours?
- How will we know the bot is helping — fewer repeated questions, faster replies, something else?
- Who approves changes to the bot's content each month?
Write the answers into a one-page brief and get a "yes" on it. Most chatbot projects that go wrong skipped this page.
How is this different from building a contact form?
A form waits for the user to fill fields in your order. A bot has to cope with whatever the user types, in any order, in Hinglish or with typos. That's why testing matters more than build time — and why your QA habits are worth more here than your framework knowledge.
Do I need Python or ML?
No. For this route you need content sense, testing discipline and integration skills. Python helps later for custom retrieval or self-hosted setups.
What does a good first portfolio piece look like?
One embedded bot on a demo site, a public test sheet (30+ questions with pass/fail), a hand-off that actually sends an email or creates a CRM record, and a two-minute Loom walkthrough. Bonus: a short note on what the bot refuses to answer.
Where do the first clients come from?
Past web clients who already have a site and a busy inbox. Local businesses in India where WhatsApp is the main channel. Agencies that build sites but don't offer bots yet — you can partner with them.
Job titles to search?
"Conversational AI developer", "chatbot developer", "support automation", "AI implementation specialist". Naukri, LinkedIn, Instahyre, Cutshort.
How do I rewrite my headline?
Before: "Frontend/Web Developer · React, Node" After: "Web developer building tested AI assistants for websites and WhatsApp · Botpress, Flowise, webhooks"
Your realistic 90 days
You've added chat widgets, WhatsApp buttons and 'Contact us' pages to dozens of sites, then watched owners drown in the same questions. Now the job is to build what sits behind the widget. You'll start with the site where the owner complained most about repeat enquiries.
Assumes 2–3 hours a day alongside job applications, a laptop and a phone, and free plans only. Every step has a smaller version and a way to pause. Use them. It runs in three blocks of 30 days, each ending with a signal that you're on track. A signal is not a promise of a job or income.
The two worries we hear most about this move
Do businesses really want chatbots? Many small businesses want quicker answers to repeated questions, especially on WhatsApp. They don't want a bot that invents answers. Your job is to build one that stays within the facts and hands off to a human. Is it risky to build bots that give wrong answers? Yes, which is why testing and guardrails are part of the work. Show in your proof how you limited answers to approved content and what happens when the bot doesn't know.
Other worries, such as age, a career gap, no degree, English, family pressure and savings, are covered on the route page and the role page.
What AI changed in your old tasks
| You used to… | Now you… |
|---|---|
| Installed a chat widget plugin and left | Write the bot's knowledge from the owner's real answers |
| Wrote page copy for humans skimming | Write short answers a bot can quote exactly |
| Did a launch checklist for the site | Do a launch checklist for the bot: wrong answers, hand-off, office hours |
Your first 7 days
| Day | Task | Done when |
|---|---|---|
| 1 | Pick the client who complained most about repeat enquiries; list 15 questions they get | 15 questions |
| 2 | Ask them (or recall) the real answer to each; write in under 50 words | 15 answers |
| 3 | Build a Voiceflow or Botpress free-plan bot with those answers | The bot answers in preview |
| 4 | Test with 30 messages typed like customers: short, misspelt, mixed language | Each scored right/wrong/hand-off |
| 5 | Fix the source answers for the worst 5 | Rerun shows improvement |
| 6 | Add the hand-off: collect name and phone, email it to the owner | Test lead arrives |
| 7 | Save 10 bot-related postings and note what platform each uses | 10 rows |
Days 1–30: A bot for your most-asked client
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Ship the bot plus a 30-message test log with before/after scores | about 10 hours over 3 weeks | score sheet shared as a link | 15 messages. | Keep the log; pause the bot. |
| Show it to the client and two others with similar businesses | about 3 hours | 3 demos done | Just the one client. | Delay a week. |
Signal by day 30: That client has seen the bot and told you which answer is wrong.
Days 31–60: Real questions, real hand-off
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Rebuild the knowledge from 50 anonymised real questions the client shares | about 10 hours | new score sheet on real questions | 20 real questions. | Stop after scoring. |
| Learn the WhatsApp Business rules through an Indian BSP's free docs (AiSensy or Interakt) | about 2 hours | you can explain opt-in, templates and the 24-hour window | Opt-in only. | Bookmark where you stopped. It will still be there next week. |
| Apply to 8 roles: conversational AI developer, chatbot developer, CX automation | about 4 hours | 8 logged | Apply to 4 roles: conversational AI developer, chatbot developer, CX automation. | Stop sending for now. Keep a list of who you've contacted so you can follow up later without doubling up. |
Signal by day 60: A business shares anonymised real chats with you, or you get a screening call.
Days 61–90: Live with a review habit
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Put the bot live for 2 weeks and send the owner a weekly 'what it answered / what it handed off' note | about 8 hours | 2 notes sent | Live on your own site. | Turn it off; keep notes. |
| Offer the same setup to 10 similar businesses with that weekly note as the example | about 3 hours | 10 messages | Offer the same setup to 5 similar businesses with that weekly note as the example. | Put it on hold until your current interviews are done, then come back to it. |
Signal by day 90: A bot running on a client's site, or a second-round interview.
One search that fits your background
The full set of search strings for this move is on the route page. They work on LinkedIn, Naukri and foundit; Instahyre and Cutshort are worth a weekly look too. Add your old job title to any of them with AND, so recruiters who want both skills find you first.
Job-hunt moves that matter for this route
- Your old clients with busy WhatsApp numbers are your first prospects.
- Search 'Voiceflow', 'Botpress', 'chatbot developer' on LinkedIn; also check BSP partner pages for agency hiring.
- Lead with the score sheet. Owners fear wrong answers more than anything.
Your 30/60/90 quests
XP: learning 20 · proof 60 · outreach 40. Ranks: Wayfinder → Builder → Pathmaker. Progress stays in your browser only.
What are the downsides?
- Free tiers are small. Real projects need paid plans and model budgets.
- Bots can be confidently wrong; you own the guardrails.
- Clients may expect the bot to "know everything". Set scope in writing.
- Chat logs hold personal data. Disclose it's a bot, collect little, follow the client's policy (DPDP in India, GDPR for EU). Not legal advice.
Which offers are scams?
"Chatbot reseller licences" sold for an upfront fee, courses guaranteeing clients, job posts asking for a deposit, and anyone asking for an OTP or UPI PIN. Official domains only. Report: cybercrime.gov.in / 1930 (India), ReportFraud.ftc.gov (US).
Is this better than the other two routes?
Not better — different. It's the gentlest on code. If you miss building, look at AI MVP rescue. If you liked the webhook part most, see automation.
Where next?
Chatbot route overview · Web developer hub · same route from WordPress or PHP
Pay
We haven't verified pay data for this route. Check current listings on job boards in your city and ask people already in the role.
Quick quiz: does this path fit?
Answer each, then press Check. Every answer explains itself.
Make your Path Card
A shareable reminder of where you're heading. The day count starts the first time you open this page; quest XP comes from your log above.
Scam check before you apply anywhere
- Real job and gig platforms are free to join. Never pay a "joining" or "training" fee.
- Never share an OTP or UPI PIN — no genuine employer needs them.
- Use official domains only; type the address yourself.
- India: report at cybercrime.gov.in or call 1930.
- US: report at ReportFraud.ftc.gov.
Small steps, every day.
Each quest has a smaller version for hard weeks, and a pause button. Nothing is lost.
Keep exploring
Sources
Checked 23 Oct 2026. We opened every link below ourselves. Search volumes on this site come from OpenSEO keyword research (Oct 2026).
The other facts here are shared with the route page, where each is listed in full with its link.
| What we checked | Where |
|---|---|
| AiSensy free plan | aisensy.com |