QR onboarding
Link a WhatsApp Business number by scanning a code — about five minutes, no developer needed.
What it shows
Six capabilities, each demonstrated on the product itself.
Keyword auto-replies
Rules that fire on customer keywords, with reply counts so you can see what actually gets used.
Visual flow builder
Multi-step conversations assembled by dragging nodes onto a canvas. No code, no deploy pipeline.
Bulk broadcasts
Segmented campaigns with recipient, sent and delivery counts reported honestly.
AI replies with handoff
Answers routine questions day or night, then hands anything unusual to a person.
Shared team inbox
Role-based access, assignment and presence, so nothing falls between shifts.
How this was built
Worth knowing if you are judging the person behind the demo.
Everything here is my own work
The product interface, the demo data, and the video pipeline are all mine — the rendering, the burned captions and the audio mix. The voiceover is synthetic, generated per caption chunk so the on-screen words line up exactly with what is spoken. The product is deployed and reachable; the demo is a recording of that deployment, not a staging mockup.
Start with a paid pilot
Pick one flow. I build it in two weeks on your real traffic, you keep the configuration either way. If it does not save you time, you have lost nothing but the fee.
Pilot · two weeks
₹6,000 one flow, fixed price
- One flow configured end to end
- Human-handoff rules included
- Tested on your live traffic first
- Written summary of what it saved
Ongoing · optional
₹2,000–4,000 per month
- Monitoring and tuning
- Priority support
- No lock-in — stop any time
- You keep the configuration
What happens next
No proposal theatre. Three steps, and you can stop at any of them.
-
1
Reply with a time
A 20-minute call. I will ask about your order flow and tell you honestly whether this is worth doing. If it is not, I will say so.
-
2
You pick the flow
Usually order confirmations or delivery-delay alerts. We agree the scope and the fixed price in writing before anything starts.
-
3
Two weeks, then a decision
Built, tested on live traffic, then a written summary of what it actually saved. Continue, or stop — you keep the configuration.
No paid clients yet. I’d rather say that up front than dress it up — ask me on the call exactly what I can and cannot evidence.