Upinion · Round 3 · WhatsApp Flows Prototype
Inside WhatsApp, every conversation pattern Upinion needs — modelled as a real, clickable Flow.
Round 2 surfaced the choice. Round 3 commits: WhatsApp is the surface. This prototype demonstrates the four conversation patterns the team needs, each one as a separate clickable Flow you can walk through end-to-end.
Everything you see below is grounded in the actual Meta Flows API — no marketing, no aspirational features. Where WhatsApp can't do something, we say so.
1Four conversation flows — click through each
A migrant in transit sees something dangerous (new border control, smuggler, authority action) and reports it back to us anonymously.
A 5-question survey on safety, location, conditions — earn 100 DA topup. The structured-form half of Upinion's data work.
Instead of pushing info as chat messages that scroll away, we deliver verified info via a Flow — list of stories, tap to read, lives in a structured archive (until the Flow token expires).
User taps a Channel post CTA or types ‘help' — opens a fresh service window so they can talk to a human (or scoped bot) for the next 24h, free.
2What's decided · what's still open
✓ Decided
- WhatsApp is the surface. PWA dropped as primary.
- Form-stays-open is a myth — but a Flow CAN have 100 navigable screens.
- Architecture: WhatsApp Channel (broadcast) + WABA Bot (Flows) + ‘Message us' CTA bridges them.
- WhatsApp Communities are OFF the table — phone numbers visible to all members. Hard fail.
- Topup abuse: invitation tokens + 30-day Reloadly lockout. Accept 5–10% residual fraud.
○ Still open
- Stack pick: Turn.io ($120/mo NGO discount, Flows-ready, fastest) vs. Glific (OSS, self-hostable, no Flows yet).
- Trust at first contact (no blue tick for ‘Anwar' pseudonym) — warm referrals + zero-link first message.
- Push notifications without a chat handle — Channel follow vs. WABA opt-in.
- Voice-as-answer — Flows have NO voice input. Workaround: voice notes via chat layer.