Submit by 11 PM IST
Week 1 · Day 1 of 14
Week 1
Day 1 ✓
Day 2 ✓
Day 3
Day 4
Day 5
Day 6
Week 2
Day 7
Day 8
Day 9
Day 10
Day 11
Day 12
Week 3
Day 13
Day 14
Day 15
Day 16
Day 17
Day 18
Week 4
Day 19
Day 20
Day 21
Day 22
Day 23
Day 24
Week 5
Day 25
Day 26
Day 27
Day 28
Day 29
Day 30
Week 6
Day 31
Day 32
Day 33
Day 34
Day 35
Day 36
Week 7
Day 37
Day 38
Day 39
Day 40
Day 41
Day 42
Week 8
Day 43
Day 44
Day 45
Day 46
Day 47
Day 48
⚡ Do This Right Now
1
Read the explainer
2
Pass the quiz (3/5)
3
Submit before 11 PM
🕚 Deadline: 11 PM IST
1
Read
2
Quiz 3/5
3
Submit
🕚 11 PM IST
🔒

This task is currently closed.

Day 1 is assigned to a specific date by the WSP team based on your batch start date.

📅 Check your confirmation email for your full task schedule.

Haven't received it? Email hello@wa.expert and we'll sort it out quickly.
📅 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
🔒 Wednesday only
Week
Week 1 of 8
Day
1 of 14
Program
2-Week Program
📖 Read This First — About 8 Minutes

A Team Inbox configured correctly is a customer service operation. Configured poorly, it's organised chaos.

The Team Inbox is not plug-and-play. Deliberate configuration determines whether it helps or hinders. The decisions you make on Day 1 of setup cascade through every conversation thereafter — so they need to be made correctly, not adjusted in week 3 after problems emerge.

🏢
Configuring a Team Inbox is like designing an office layout. You don't hand people desks and say start working. You define who sits where, who handles what, who is the manager, how urgent tasks get flagged, and what happens when someone is away. Same decisions, same importance.
👤
Agent roles + permissions
Agents (reply only), Supervisors (reply + reassign + view all), Admins (full access + configuration). Never give everyone admin. Role boundaries create accountability.
🔀
Routing rules
Auto-assign by: keyword in first message, contact tag, time of day, round-robin. Multi-location: route by city keyword. Multi-product: route by product mentioned.
SLA configuration
First response targets (e.g. 15 mins), resolution targets (e.g. 4 hours). Flag overdue conversations. Makes inbox a managed system, not just a shared screen.
🏷
Tag taxonomy design
Design all contact tags before go-live. Consistent tags from Day 1 make CRM data searchable and actionable. Without pre-design, 6 months of data becomes unusable.

🔑 Configuration principle: Every setting decided before go-live, documented, and trained. An inbox where agents invent their own tagging and routing habits within the first week will be unusable within a month.

💡
Read the reference page below before taking the quiz.
💬
Explore: Team Inboxwa.expert/pages/inbox.html · Configuration options · ~5 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
Real estate agency: 2 Mumbai agents, 2 Pune agents, 2 commercial agents. How should routing be configured?
A
All conversations to all 6 agents round-robin
B
Keyword-based routing: 'Mumbai' routes to Mumbai pair, 'Pune' to Pune pair, 'office/commercial' to commercial pair. Unmatched → supervisor queue.
C
Only the admin receives new conversations
D
All agents see all messages and self-assign
✅ Keyword-based routing by location and type. Each agent sees only relevant conversations — faster response, better expertise match, cleaner inbox.
❌ Keyword-based routing is the answer. Each agent sees relevant conversations only — reduces noise, increases speed and quality.
Question 2 of 5
Why define SLA targets in Team Inbox configuration?
A
SLAs are only for enterprise clients
B
SLA targets make response time a managed metric — overdue conversations are flagged, supervisors see bottlenecks, and the team has a clear measurable standard
C
SLAs automatically close old conversations
D
SLAs are set by Meta, not the business
✅ SLAs turn response time from a vague expectation into a measurable standard. Flagged overdue conversations create accountability without micromanagement.
❌ SLAs make response time measurable. Without them, 'reply quickly' means different things to different agents. With them, overdue conversations surface automatically.
Question 3 of 5
A new agent joins a business with 6 months of data but no tag conventions. What problem exists?
A
No problem — tags are optional and cosmetic
B
CRM data is likely inconsistent — 'lead', 'Lead', 'new lead', some untagged. Segmentation and reporting are unreliable. Defining tags before go-live prevents this entirely.
C
The agent cannot access the inbox
D
Meta blocks new agents from joining mid-stream
✅ Inconsistent tagging makes the CRM unreliable. Case variations, synonym tags, and missing tags create data that cannot be accurately segmented or reported on.
❌ Inconsistent tagging is the problem. Without a defined taxonomy, variations make segmentation and reporting unreliable. Design tags before go-live — always.
Question 4 of 5
Correct permission level for a team leader who needs to view all conversations and reassign them but NOT change platform settings?
A
Admin
B
Supervisor — view all and reassign, but no configuration access
C
Agent
D
Read-only viewer
✅ Supervisor role. View all + reassign = supervisor. Configuration = admin only. Role boundaries protect system integrity.
❌ Supervisor is the answer. View all + reassign without configuration access. Admin should be reserved for the platform owner only.
Question 5 of 5
A healthcare clinic's Team Inbox handles appointment booking, prescription queries, and billing. Why route these separately?
A
It isn't important — any agent handles any type
B
Different query types need different expertise and different SLAs — billing to a receptionist or clinical queries to a billing agent creates wrong answers and trust failures
C
Routing separately increases cost
D
Meta requires separate routing for healthcare
✅ Expertise + SLA matching. Each query type needs the right person. Misrouting creates wrong answers, patient frustration, and potential clinical risk.
❌ Expertise matching is the answer. Each type needs different knowledge and different response times. Misrouting is a quality and safety issue in healthcare.
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 Wednesday counts as Day 3 complete.
Week 1 · Coming Tomorrow
Day 2 — WhatsApp App vs Business API Opens Tuesday on your assigned date.
Day 2 →
WSP · WA.Expert Student Programs · wa.expert Help: hello@wa.expert
📋 Register a friend 🎁 Share your WSP ID