AS
Implementation Proposal

Scalable WhatsApp Automation on Zoho One × AiSensy

A production-grade communication system for AdmissionLabs — every lead acknowledged in 30 seconds, every counselling call reminded, every webinar followed up. Built on your existing stack, documented to your own governance standard.

Prepared byAman Shukla — Zoho Developer (Creator Certified)
InvestmentUSD 1,200 fixed · ~65 hours
Timeline4–5 weeks
Date15 August 2026

01I've read your plan — and it's good

Your WhatsApp Automation Plan workbook already does what most clients pay a consultant to produce: 21 mapped CRM touchpoints, a tool-responsibility matrix, a WA-xxx flow naming convention, a Master Automation register, per-flow design docs, a template register with Meta approval status, and an integration register. My job is not to reinvent it — it's to implement it faithfully, harden it, and hand it back live and documented in exactly the structure you designed.

21 touchpoints mapped

From instant welcome through no-show recovery, close-lost reactivation, webinars and marketing campaigns — I build to your Requirement Mapping sheet, line by line.

Your governance, kept

Flows delivered under your WA-xxx convention in your three folders (Lead / Webinar / Counselling), each with a completed Flow Design doc and registers updated.

Gaps I'll close

Reply-based escalation, lead scoring, missed-call recovery and failure handling (retry → notify admin) need webhook engineering beyond point-and-click — that's where the real work is, and it's in scope.

02System architecture

One clean pattern, repeated: Zoho CRM is the single source of truth, Zoho Flow is the only place automation logic lives, and AiSensy is the delivery layer. Nothing talks to WhatsApp except through Flow, so every message is traceable to a flow ID and a CRM record.

flowchart LR
  subgraph CAPTURE["Lead Capture"]
    META["Meta CTWA Ads"]
    FORMS["Zoho Forms"]
    WEB["Webinar Registrations"]
  end
  subgraph CORE["Source of Truth"]
    CRM["Zoho CRM
Leads · Students · Counsellors
Lead Score · Tags · Tasks"] end subgraph ENGINE["Automation Engine"] FLOW["Zoho Flow
WA-001 … WA-021
+ retry & admin alerts"] end subgraph DELIVERY["WhatsApp Layer"] AIS["AiSensy
Templates · Campaigns · WABA"] end BOOK["Zoho Bookings
Self-service slots"] AN["Zoho Analytics
Delivery · Booking · No-show KPIs"] META --> CRM FORMS --> CRM WEB --> CRM CRM -->|"triggers"| FLOW FLOW -->|"send API"| AIS AIS -->|"reply webhook"| FLOW FLOW -->|"score · tasks · notify"| CRM BOOK <--> CRM BOOK --> FLOW CRM --> AN AIS --> AN style CRM fill:#0b3a2a,color:#fff style FLOW fill:#128C43,color:#fff style AIS fill:#25D366,color:#04310f
Every automation follows CRM → Flow → AiSensy; every reply comes back AiSensy → Flow → CRM (escalation, scoring, tasks).

Tool responsibilities — exactly as your plan assigns them

Zoho CRM

Zoho CRM

Master database, lead stages, scoring fields, tasks, counsellor assignment.

Zoho Flow

Zoho Flow

All automation and API orchestration — the only home for logic, with retry + admin-notify failure handling.

Ai

AiSensy

WhatsApp delivery: utility & marketing templates, campaigns, WABA health, reply webhooks.

Zoho Bookings

Zoho Bookings

Self-service counselling slots, synced to counsellor calendars; confirmations and reminders driven from booking events.

Zoho Forms

Zoho Forms

Lead capture and the pre-call qualification form (course, intake, budget, IELTS/German level).

Zoho Analytics

Zoho Analytics

KPI dashboards: delivery rate, booking rate, no-show rate, webinar funnel, reactivation yield.

M

Meta Business

WABA management, template approvals, Click-to-WhatsApp ad attribution into CRM.

Zoho One

Zoho One

Single licence umbrella — no extra middleware (no Zapier/Make), so cost and complexity stay flat as you scale.

03The lead journey, automated end-to-end

Your Requirement Mapping sheet, as a living system:

flowchart TD
  A["New lead created"] -->|"≤ 30 sec"| B["WA-001 Welcome +
counsellor assigned"] B --> C{"Booked a call
within 24 h?"} C -->|No| D["WA-002 Booking nudge
(Bookings self-service link)"] D --> E{"Active by 48 h?"} E -->|No| F["WA-003 'Why AdmissionLabs'
trust message"] C -->|Yes| G["Booking confirmation +
qualification form"] G --> H["Reminders: 24 h & 15 min"] H --> I{"Attended?"} I -->|No| J["No-show rebooking flow"] I -->|Yes| K["Thank-you + next steps
+ document upload links"] K --> L{"Outcome"} L -->|"Follow-up set"| M["Personal follow-up reminder"] L -->|Undecided| N["Standby: Germany roadmap,
FAQs, career insights"] L -->|"Future intake"| O["Tagged — auto-reminder
when applications open"] F --> P["60–90 d inactive →
reactivation campaign"] N --> P style A fill:#0b3a2a,color:#fff style B fill:#25D366,color:#04310f style P fill:#b45309,color:#fff
Parallel webinar track: launch campaign → registration confirmation → 24 h / 1 h reminders → attended = strategy-call push · missed = replay invite.

04Scope of work & delivery plan

Three phases. Each ends in something you can test and accept — nothing is "80% done" at a milestone boundary.

PhaseWhat gets builtHours
Phase 1 — Foundation & Core Lead Flows
Week 1–2
WABA/AiSensy audit & Flow connections · full template pack drafted and submitted for Meta approval (~16 utility + marketing templates) · architecture document · WA-xxx folder & naming setup · WA-001–WA-003 live (welcome, 24 h booking nudge, 48 h trust message) · Bookings self-service pipeline wired to CRM 29 h
Phase 2 — Counselling Engine
Week 3
Booking confirmation + qualification form · 24 h / 15 min reminders · no-show rebooking · post-call thank-you & next steps · follow-up reminders · missed-call recovery · document collection links · reply-based escalation webhook + lead scoring + auto task assignment 20 h
Phase 3 — Webinars, Campaigns & Handover
Week 4–5
Webinar track (launch, registration confirmation, 24 h/1 h reminders, attended/missed branches) · reactivation & future-intake journeys · campaign templates (testimonials, deadlines, Germany updates, YouTube) · Analytics KPI dashboard · end-to-end UAT · registers & Flow Design docs completed · handover walkthrough 16 h
TotalAll 21 mapped touchpoints live + governance documentation65 h

Deliverables checklist

Working system

~18 production Zoho Flows (some touchpoints share a flow), AiSensy campaigns, approved Meta templates, Bookings pipeline, qualification form, scoring fields and dashboards — live in your accounts.

Documentation, your format

Master Automation register filled for every flow · one Flow Design doc per flow · Template register with Meta status · Integration register · admin runbook for failure alerts.

05Investment & milestones

Fixed price: USD 1,200 (~65 hours). Paid per milestone, each released only when its phase passes your acceptance test.

45%
USD 540 — Phase 1
  • Templates approved by Meta
  • WA-001–003 live & verified
  • Bookings pipeline working
  • Architecture doc delivered
30%
USD 360 — Phase 2
  • Full counselling engine live
  • Escalation + scoring verified
  • Reminder/no-show flows tested
25%
USD 300 — Phase 3
  • Webinar & campaign track live
  • KPI dashboard delivered
  • Docs complete, handover done
Why the split leans forward: Phase 1 carries the heaviest engineering — WABA plumbing, the entire Meta template approval cycle (the longest external dependency, started on day one), architecture, and the first live flows. The weighting simply follows where the build effort actually lands.
Assumptions: Zoho One and AiSensy subscriptions, WABA and Meta Business Manager access are provided by you (AiSensy conversation charges are pay-as-you-go to Meta, outside this quote). Two revision rounds per phase included. 30 days of post-handover bug-fix support included at no charge.

06Why me

5 years, Zoho only

Zoho Creator Certified developer with clients across 10+ countries. CRM, Flow, Bookings, Forms, Analytics and Deluge are my daily stack — including webhook-driven WhatsApp integrations.

Lean, honest estimates

I've delivered enough webhook-driven WhatsApp and CRM automation builds that most components start from proven patterns, not a blank page. That's why 65 hours is a real number, not a teaser — you pay for outcomes, not keystrokes.

Architecture first

You asked for clean, well-documented architecture. Every flow ships with its design doc, the registers stay current, and the naming convention means your team can maintain the system without me.

Next steps