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
🔒 Friday only
Week
Week 8 of 8
Day
1 of 14
Program
2-Week Program
📖 Read This First — About 8 Minutes
A well-designed integration architecture is as important as the WA.Expert configuration itself.
Day 47 — Month 2, Week 8. You are in the advanced phase of the 2-Month Expert Program. Today: Integration Architecture — Full Stack.
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 a 'point-to-point' integration and a 'hub and spoke' integration architecture?
A
They are the same thing
B
Point-to-point: each system connects directly to every other system — manageable for 2–3 systems, complex at scale (N*(N-1) connections for N systems). Hub and spoke: all systems connect to a central hub (e.g. Make.com) which routes between them — much simpler at scale, single point of management.
C
Hub and spoke is only for large enterprises
D
Point-to-point is always more reliable
✅ Hub and spoke is the scalable architecture for WA.Expert integrations. Make.com or similar acts as the hub — add new systems by connecting to the hub, not to every other system.
❌ Hub and spoke = central routing platform (Make.com). Add new systems by connecting to the hub. Far simpler than point-to-point at scale.
Question 2 of 5
A medium-sized e-commerce business has: Shopify, WA.Expert, Google Sheets, Salesforce, and a custom inventory system. What is the correct integration architecture?
A
Connect each system directly to every other system
B
Hub and spoke with Make.com as the hub: all systems connect to Make.com. Scenario: Shopify order created → Make.com routes to WA.Expert (confirmation message) + Sheets (analytics row) + Salesforce (customer record) + inventory (decrement). One event, multiple actions, one place to maintain.
C
Only connect Shopify and WA.Expert
D
Use a separate Make.com account for each connection
✅ Hub and spoke with Make.com. One Shopify event → Make.com routes to all downstream systems simultaneously. Single maintenance point, easy to add new systems.
❌ Make.com as hub. One event triggers multiple downstream actions through one central routing point. Simple to maintain, easy to extend.
Question 3 of 5
When should a client use a custom API integration instead of Make.com or Zapier?
A
Always use custom code for reliability
B
When: volume exceeds no-code platform limits (100,000+ operations/month), when latency requirements are under 100ms, when complex data transformation logic is needed, or when the client has an in-house development team and long-term ownership matters
C
Never — no-code is always sufficient
D
When the client prefers it aesthetically
✅ Custom code when: very high volume, low latency requirements, complex logic, or in-house team available. No-code is the right choice for most SMB implementations.
❌ Custom code for: very high volume, low latency, complex logic, in-house team. No-code for everything else.
Question 4 of 5
What documentation should be created and handed over after completing a WA.Expert integration?
A
No documentation needed — the client can figure it out
B
Integration map (which systems connect to what), webhook payload schemas for each event type, Make.com scenario documentation (what each scenario does and when it triggers), error handling procedures, and who to contact if something breaks
C
Just the Make.com login credentials
D
A video recording of the setup process
✅ Integration map + webhook schemas + Make.com documentation + error procedures + escalation contacts. This documentation enables the client to maintain and troubleshoot the integration after the implementer leaves.
A client's integration breaks 6 months after go-live. They have no documentation. What does this indicate about the original implementation?
A
The client should have maintained the integration themselves
B
The original implementation was incomplete — a professional implementation includes handover documentation that enables the client or a new developer to understand, troubleshoot, and maintain the integration without the original implementer. Documentation is not optional.
C
Integrations always break eventually
D
The Make.com platform is unreliable
✅ Incomplete handover is an implementation deficiency. Documentation that enables maintenance and troubleshooting without the original developer is a non-optional deliverable.
❌ No documentation = incomplete implementation. Documentation enabling independent maintenance is a required deliverable, not a nice-to-have.
–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 Friday counts as Day 47 complete.
Week 1 · Coming Tomorrow
Day 2 — WhatsApp App vs Business APIOpens Tuesday on your assigned date.