📅 Week 1 · Monday
day-01
What is WA.Expert?.
Today you'll learn: what WA.Expert is and why businesses pay for it — explained so clearly you could teach it to your parents by tonight.
⏱ ~20 mins
📖 Read + Quiz + Submit
✅ Need 3/5 to unlock
🔒 Tuesday only
Week
Week 1 of 8
Day
1 of 14
Program
2-Week Program
📖 Read This First — About 8 Minutes
A chatbot without a properly designed decision tree is a liability, not an asset.
Day 2. Architecture understood. Now the component that requires the most design work: the chatbot. Most people think building a chatbot means writing a few replies. A production-ready chatbot requires deliberate decision tree design, fallback handling, escalation logic, and ongoing optimisation. This is the difference between a chatbot that frustrates customers and one that genuinely serves them.
A chatbot decision tree is a map. Plan every road, every turn, and every dead end before you build. A map with missing roads leaves users stranded. A chatbot with missing branches leaves customers frustrated and bouncing to competitors. Design the full map first. Build second.
5 components every production chatbot must have:
Entry triggers
What starts the flow? Keyword triggers ("Hi", "Help", "Price"), button taps, specific phrases. Define every entry point explicitly — never assume users will message exactly what you expect.
Decision branches
Each branch handles one user intent. Maximum 3–4 options per menu — more creates decision paralysis. Each option leads to either a resolution or the next branch.
Fallback handling
When the user says something the bot doesn't recognise — never go silent. A fallback must always respond and offer a clear next step or human escalation.
Escalation triggers
Define exactly when the bot hands to a human: sentiment keywords ("complaint", "urgent", "angry"), specific topics, repeated fallbacks (3+ in one session).
⚠️ Most common chatbot failure: No fallback handling. When a user says something unexpected and the bot goes silent, trust collapses instantly. "I didn't quite get that — here's what I can help with: [options]" recovers the conversation every time.
Read the reference page below before taking the quiz.
Explore: Chatbot Builderwa.expert/pages/chatbot.html · Builder features + flow examples · ~6 mins
→
🧠 Quiz — 5 Questions
Day 1 Quiz
Score 3 or more to unlock your submission. Retry as many times as you want — every wrong answer tells you why.
5 questions
Need 3/5
Unlimited tries
Instant feedback
Question 1 of 5
Maximum recommended options per chatbot menu and why?
✅ 3–4 is the UX sweet spot. More than 4 options = users freeze or abandon. Keep menus tight and specific.
❌ 3–4 is the answer. More than 4 creates decision paralysis. Users abandon rather than choose.
Question 2 of 5
A user messages a clinic chatbot: 'I need to cancel my appointment.' No cancellation flow exists. What should happen?
✅ Fallback + immediate escalation with context. Bot can't handle this but can gracefully hand to human with intent already captured. Zero frustration.
❌ Graceful fallback + escalation with context. Never go silent. Acknowledge, escalate, pass context so the human doesn't make the user repeat themselves.
Question 3 of 5
What are escalation triggers and why must they be explicitly defined?
✅ Escalation triggers are defined conditions for human handover. Without them, the bot either handles everything (frustrating on complex issues) or never escalates.
❌ Escalation triggers are explicit conditions for human handover. Without definition, the bot either over-escalates or under-escalates — both damage the user experience.
Question 4 of 5
A real estate chatbot collects budget, location, property type, and timeline. What should happen to this data after collection?
✅ CRM storage + webhook push = immediately actionable data. Stored in WA.Expert for history AND pushed to sales system for immediate action. Both are necessary.
❌ CRM + webhook push is the production answer. Data only stored in WA.Expert is a dead end. It must reach wherever the team acts on it.
Question 5 of 5
What is the difference between a keyword trigger and a button trigger?
✅ Reliability is the key difference. Buttons are tapped — no typing variation. Keywords depend on exact text match, which users often get wrong. Production chatbots use buttons for navigation.
❌ Keywords require exact text match (fragile). Buttons are tapped (reliable). Use buttons for navigation, keywords for initial entry triggers.
–of 5
Answer all 5 questions, then check your score.
✏️ Your Task
Score 3/5 to unlock this
Complete the quiz above first. The moment you score 3 or more, this section unlocks.
🎉 Day 1 — done!
Day 2 opens on your assigned Tuesday.
📝 Today's Task
Someone in your family runs a small business. In 3–4 sentences, explain WA.Expert to them like you're actually WhatsApp-ing them right now. Your own words — not copied from the page.
Start like this: "So there's this platform I was reading about — it's basically for businesses that get too many WhatsApp messages to handle manually. It lets them..."
0 / 800
From your registration confirmation email. Can't find it?
Submitting before 11 PM IST on your assigned Tuesday counts as Day 2 complete.