You may be closer to this than it feels.
Before → after: what changes in your week
| Before | After |
|---|---|
| Install and configure plugins | Install and configure a bot (AI Engine in WP, or Botpress) |
| Write the FAQ page | Turn the FAQ into the bot's approved knowledge |
| Test on staging | Run a 30-question test sheet; fix wrong answers |
| Contact form for leads | Bot hands off to a human when unsure |
| Hand over and leave | Monthly "answer review" retainer |
Is this you?
Good fit: you write clear copy, you've handled client support, you're patient with testing. Less good fit: you want to write lots of code (look at AI MVP rescue) or you dislike talking to non-technical staff.
Flip cards: myths about chatbot work
- "You need to be an ML engineer." → Flip: most client bots are configuration + content + testing.
- "Bots replace support staff." → Flip: good bots handle repeats and hand the hard cases to people.
- "Any bot is fine." → Flip: a bot that invents refund rules is worse than none.
AI tried your job — where it slipped
Read a short scripted chat between a "plugin shop" bot and a customer. Three answers are wrong: it invents a refund window, quotes a plugin version that doesn't exist, and offers a coupon nobody approved. Tap each one you spot. Every catch unlocks the guardrail you'd add — "answer only from approved content", "version comes from the changelog", "never create offers". Score out of 3. It's scripted, not live AI. The point: spotting these is your job now.
AI tried your job — where it slipped
Tools we checked (23 Oct 2026)
- AI Engine (wordpress.org): free; 90,000+ active installs; chatbots and MCP server free; embeddings, function calling and AI Forms are Pro. You need your own AI provider key and pay that provider for usage.
- Botpress: free plan with 100 conversations/month, 3 seats, 3 agents. Plus is a paid tier.
- Flowise: open source and free to self-host; check flowiseai.com for current cloud plans.
- Voiceflow: offers a free trial; we found no free plan, so don't plan on it being free.
- WhatsApp (India): AiSensy says it has a free-forever plan (Meta charges per message separately). Interakt is widely used by Indian D2C brands; pricing not checked.
- Certification: not required. Your test sheet is your certificate.
Proof project: "Ask the Clinic" bot
- Take 30 real FAQs from a site you built (with permission) or a made-up clinic.
- Build the bot in AI Engine on staging. Instructions: answer only from these FAQs; if unsure, show the hand-off form.
- Write a test sheet: 30 questions, 10 of them tricky ("Can I get a refund after 3 months?").
- Record pass/fail. Fix. Re-test. Publish the sheet with the demo.
Your realistic 90 days
You've built sites for clinics, coaching centres, shops and local services — businesses that get the same ten questions on WhatsApp every day. A chatbot builder answers those questions safely and hands the rest to a human. You'll start with the FAQ content already sitting on a site you built.
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.
What AI changed in your old tasks
| You used to… | Now you… |
|---|---|
| Built FAQ pages with accordions | Turn the same FAQ into a bot's knowledge base and test every answer |
| Embedded WhatsApp click-to-chat buttons | Design what happens after the click: bot reply, hand-off, office hours |
| Did QA on contact forms before launch | Write a test sheet of 30 real customer questions and score the bot |
| Handed over the site and moved on | Offer a monthly 'answer review' to fix what the bot got wrong |
Your first 7 days
| Day | Task | Done when |
|---|---|---|
| 1 | Pick one past client site with a real FAQ (clinic, school, shop); copy the FAQ into a Google Doc | 10+ question-answer pairs in the doc |
| 2 | Install AI Engine (free) on a local copy of that site and load the FAQ | The bot replies on the local site |
| 3 | Write 30 test questions the way customers actually type them (Hinglish, typos, voice-note style) | 30 rows in a Sheet |
| 4 | Run all 30; mark right, wrong or 'should have handed off' | Every row scored |
| 5 | Fix the 5 worst answers by editing the source FAQ, not the prompt | Rerun shows those 5 improved |
| 6 | Open Botpress's free plan and read how it handles a human hand-off | One page of notes on hand-off options |
| 7 | Save 10 chatbot or 'conversational AI' postings and 5 local businesses with busy WhatsApp numbers | 15 rows in your sheet |
Days 1–30: A tested bot for one real business type
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Build the FAQ bot with a written test sheet: 30 questions, scores before and after fixes | about 12 hours over 3 weeks | score sheet shows the before/after | 15 questions. | Save the sheet; the bot can wait. |
| Show the bot to 3 past clients on a 10-minute call or a WhatsApp video | about 3 hours | 3 demos done; their top question noted | 1 demo. | Optional. If reaching out feels like too much this week, skip it and put the time into your proof. |
Signal by day 30: You can show a test sheet with right/wrong scores — that's rarer than a demo. One business owner has watched it.
Days 31–60: Hand-off and WhatsApp reality
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Add a hand-off: unanswered → form → email to staff, with office hours shown | about 8 hours | a test question the bot can't answer reaches your inbox | Show a phone number instead. | Stop once the form works. |
| Read the WhatsApp Business API basics through an Indian BSP like AiSensy or Interakt (free docs only) | about 3 hours | you can explain templates, opt-in and the 24-hour window in your own words | Read only the opt-in rules. | Bookmark and return later. |
| Apply to 8 chatbot or CX-automation roles with your test sheet linked | about 4 hours | 8 applications logged | 4 applications. | Pause in interview weeks. |
Signal by day 60: A business has shared real (anonymised) customer questions with you, or you've had an interview for a bot or support-automation role.
Days 61–90: One live bot with a review routine
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Put one bot live on a past client's site for 2 weeks and review its logs weekly | about 10 hours | two weekly review notes exist | Live on your own site. | Turn the bot off; keep the test sheet. |
| Write up what the bot handled and what it handed off; send to 10 similar local businesses | about 4 hours | write-up done, 10 messages sent | 5 messages. | Hold the messages for later. |
Signal by day 90: One bot live on a real site with the owner's OK, or a second-round interview.
The two worries we hear most about this move
Will a chatbot plugin do this for clients anyway? Plugins handle the widget. Clients still need someone to choose what the bot may say, connect it to their content, test it and fix wrong answers. That setup and care is the service. Do I need to learn AI programming? No. You'll configure tools, write the content the bot draws on, and test conversations. Light scripting helps for integrations but isn't required at the start.
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.
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
- Local businesses with busy WhatsApp numbers (clinics, coaching institutes, salons) are the realistic first buyers. Your past clients come first.
- Job titles to search: 'chatbot developer', 'conversational AI', 'Botpress', 'WhatsApp bot'.
- Lead with the test sheet. It shows you check answers, which is what owners worry about.
- Never promise a bot that 'replaces staff'. Promise fewer repeat questions and a clean hand-off.
Your 30/60/90 quests
XP: learning 20 · proof 60 · outreach 40. Ranks: Wayfinder → Builder → Pathmaker. Progress stays in your browser only.
First offers
| Offer | Scope |
|---|---|
| FAQ Bot Starter | Site bot + hand-off |
| WhatsApp Enquiry Bot | Menu + FAQ + lead capture |
| Monthly Answer Review | Logs → fixes → updates |
Titles to search: Chatbot Developer, Conversational AI Developer, AI Support Automation, Botpress Developer, WhatsApp Automation Executive.
Salaried role or client work?
Jobs exist in support-tech teams (search LinkedIn and Naukri for "conversational AI", "chatbot"). Search volume for "ai chatbot developer" is small (30/month India, 70 US), so most early work comes from people who already trust you, not from search.
Headline rewrite
Before: "WordPress Developer · Elementor · WooCommerce" After: "I build website and WhatsApp assistants that answer customers accurately — and hand off when they shouldn't"
On calls and interviews
Show the test sheet. Explain your hand-off rule. Ask, "Which questions must a human always answer?" That one question signals you're safe to hire.
Does experience level change the entry point?
Freshers: build two demo bots in different niches. Mid: sell to past clients. Senior/40+: lead with risk — "here's how we stop the bot embarrassing you."
Bot-reseller red flags
Be wary of "chatbot reseller" schemes with joining fees. Use official domains only; never share an OTP or UPI PIN. Report at cybercrime.gov.in / 1930 (India) or ReportFraud.ftc.gov (US).
Plugin-to-bot questions
Will clients pay monthly? Some will for reviews and updates; it isn't guaranteed. Who pays the AI usage bill? Usually the client's own provider account — set that up from day one. Is customer chat data sensitive? Yes. Collect little, tell users it's a bot, and follow the client's privacy policy. Not legal advice. AI Engine or Botpress? AI Engine if the client lives in WordPress; Botpress for multi-channel bots.
Next: AI chatbot builder route · AI automation bridge · quiz
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.
Your skill map
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.