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
🔒 Thursday only
Week
Week 8 of 8
Day
1 of 14
Program
2-Week Program
📖 Read This First — About 8 Minutes

Event routing design determines whether an integration is maintainable or a house of cards.

Day 46 — Month 2, Week 8. You are in the advanced phase of the 2-Month Expert Program. Today: Advanced Webhooks — Event Routing.

You now have the full technical and implementation foundation from Days 1–28. The remaining days build the advanced expert capabilities — the skills that differentiate a junior implementer from a senior consultant.

🔬
Expert-level work is about depth within a domain, not breadth across domains. Anyone can configure a Team Inbox. An expert configures it correctly the first time, anticipates the edge cases, and knows how to fix it when something breaks six months later. That depth is what today builds.

Read the reference page below, then apply your expert-level knowledge to the quiz and the day's task. The tasks at this stage are real deliverables — not practice exercises.

🔑 Expert standard: Every task submission from Day 29 onwards should be something you could show to a client or employer as evidence of your capability. Not a draft — a deliverable.

💡
Read the reference page below before taking the quiz.
🔬
Reference: Advanced Webhooks — Event Routingwa.expert/pages/whatsapp-webhook-guide.html · ~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
What is 'event-driven architecture' and how does it apply to a WA.Expert integration?
A
A software design philosophy unrelated to WhatsApp
B
A system where components communicate by emitting and reacting to events rather than direct calls — in WA.Expert: a form submission emits an event, Make.com reacts by routing data to Salesforce, which emits a lead-created event, which triggers a WA.Expert welcome message. Decoupled, scalable, and maintainable.
C
An architecture for event ticketing businesses
D
A type of WhatsApp Flow
✅ Event-driven architecture: decoupled components communicating via events. In WA.Expert: form submit → event → Make.com routes → Salesforce creates lead → event → WA.Expert sends welcome. Each step is independent and swappable.
❌ Event-driven = components communicate via events, not direct calls. Each step is decoupled and independently swappable. This is how robust WA.Expert integrations are designed.
Question 2 of 5
A webhook integration must route different event types to different systems: leads to Salesforce, orders to the ERP, support tickets to Zendesk. Best architecture?
A
Three separate webhook endpoints, one per destination
B
One WA.Expert webhook endpoint → Make.com receives all events → event type field routes to the correct downstream system. Single integration point, conditional routing logic, easier to maintain than three separate endpoints.
C
Send everything to all three systems and let each decide
D
Manual routing by the operations team
✅ Single endpoint + conditional routing in Make.com. Cleaner, easier to maintain, single point of visibility for all webhook traffic. Add new destinations by adding routing rules, not new endpoints.
❌ Single endpoint + Make.com conditional routing = cleaner and more maintainable than three separate endpoints. Add new destinations by adding routing rules.
Question 3 of 5
What is 'idempotency' in webhook processing and why does it matter?
A
A type of webhook security
B
The property of a webhook handler that produces the same result even if the same event is processed multiple times — important because webhooks can be delivered more than once (retries). Processing a 'new lead' webhook twice should not create two duplicate leads in Salesforce.
C
The speed at which webhooks are processed
D
A metric for webhook delivery success rate
✅ Idempotency prevents duplicate processing on retry. Use the unique submission_id in the payload as a deduplication key — check if it was already processed before acting on it.
❌ Idempotency = same result regardless of how many times the same event is processed. Use submission_id as deduplication key to prevent duplicate records on retry.
Question 4 of 5
A WA.Expert webhook fires when a student submits a task. The receiving Google Sheet already has that submission. What should the processing logic do?
A
Add a duplicate row anyway
B
Check if the submission_id already exists in the sheet before inserting — if it does, skip the insert (idempotency). Log the duplicate receipt for monitoring but do not create a duplicate record.
C
Delete the original and replace it
D
Send an error back to WA.Expert
✅ Check submission_id before insert. If exists → skip + log. This prevents duplicates when webhooks are retried after temporary failures.
❌ Check submission_id → if exists, skip + log. Prevents duplicate records from retried webhook deliveries.
Question 5 of 5
How should sensitive data (phone numbers, names, financial details) be handled in webhook payloads?
A
Include everything — webhooks are secure by default
B
Use HTTPS for all webhook endpoints, include only the minimum data needed for the receiving system to act, avoid logging sensitive fields in error logs, and rotate webhook secrets regularly. For BFSI clients, consult the specific regulatory requirements for data transmission.
C
Encrypt every individual field in the payload
D
Avoid using webhooks for sensitive data entirely
✅ HTTPS + minimum required data + careful logging + secret rotation + regulatory awareness for BFSI. Security is a design consideration, not an afterthought.
❌ HTTPS + minimum data + careful logging + secret rotation + regulatory compliance for BFSI. Security is built in, not added later.
–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 Thursday counts as Day 46 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