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 8 of 8
Day
1 of 14
Program
2-Week Program
📖 Read This First — About 8 Minutes
At scale, the dashboard becomes insufficient. API-level control is what keeps high-volume campaigns running reliably.
Day 45 — Month 2, Week 8. You are in the advanced phase of the 2-Month Expert Program. Today: Advanced API — Bulk Send Architecture.
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.
What is the difference between sending a bulk campaign via WA.Expert dashboard vs via the HTTP API?
A
No difference — both produce the same result
B
Dashboard: simple interface, template selection, audience upload, one-click send — suitable for most use cases. API: programmatic control, dynamic personalisation per recipient, trigger-based sending from external systems, batch management at very high volumes. API is for when the dashboard's capabilities are insufficient.
C
API is always faster
D
API campaigns are cheaper
✅ Dashboard for most use cases. API for programmatic control, dynamic personalisation, trigger-based sending, or very high volume management that needs external system control.
❌ Dashboard = simple, sufficient for most. API = programmatic control, dynamic personalisation, trigger-based, or extreme volume management.
Question 2 of 5
What is a 'message batch' in API bulk sending and why does it matter?
A
A group of templates awaiting approval
B
A defined set of messages sent in one API call — batching controls send rate to respect Meta's tier limits, enables tracking of a specific send group, and allows retry logic to be applied to a failed batch rather than individual messages
C
A Meta billing category
D
A WA.Expert campaign type
✅ Batching controls rate, enables group tracking, and allows batch-level retry. Essential for high-volume API sends that must respect daily tier limits.
❌ Batch = controlled rate + group tracking + batch-level retry. Essential for high-volume API sends respecting daily tier limits.
Question 3 of 5
Write the conceptual structure of an API call to send a personalised WhatsApp to 3 contacts with different variable values.
A
One API call for all 3 contacts simultaneously
B
Three separate POST /v1/messages calls — one per recipient — each with the same template_name but different variable values specific to that recipient. The API does not support multi-recipient personalised sends in one call.
C
One API call with all 3 phone numbers
D
Use the bulk endpoint instead of messages endpoint
✅ One call per recipient when personalisation variables differ. The messages endpoint sends to one recipient per call. Build a loop in your code or Make.com scenario for multiple personalised sends.
❌ One call per recipient for personalised sends. Build a loop for multiple recipients with different variables.
Question 4 of 5
What is rate limiting in the WhatsApp Business API and how does it affect bulk sending?
A
Meta charges more for faster sends
B
Meta limits how many messages can be sent per second per WABA (typically 80 messages/second). Exceeding this rate causes API 429 errors. Production bulk sends must implement rate limiting with delays between calls to stay within limits.
C
Rate limiting only affects utility templates
D
Rate limiting can be disabled by upgrading your plan
✅ ~80 messages/second per WABA. Exceed this = 429 rate limit errors. Implement delays between API calls (e.g. 13ms minimum between calls for 80/second). Essential for high-volume sends.
❌ ~80 messages/second limit. Exceed = 429 errors. Implement per-call delays to stay within rate limits.
Question 5 of 5
A client wants to send 1 million WhatsApp messages per month. What infrastructure considerations apply?
A
No special considerations — the API handles it
B
Tier 4 (unlimited) messaging tier with sustained Green quality rating required. Robust webhook retry infrastructure for acknowledgement tracking. Database to log all 1M sends and statuses. Make.com or similar will be insufficient — requires custom API integration or enterprise automation platform.
C
Only the billing needs attention
D
This volume is not supported by WhatsApp API
✅ Tier 4 + Green quality + robust retry infrastructure + logging database + custom API integration. At 1M/month, no-code platforms become insufficient — enterprise-grade implementation required.
❌ Tier 4 + Green quality + retry infrastructure + logging + custom API or enterprise platform. No-code tools are insufficient at this volume.
–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 45 complete.
Week 1 · Coming Tomorrow
Day 2 — WhatsApp App vs Business APIOpens Tuesday on your assigned date.