Internal Ops — New Customer Onboarding Process Automation
Current Process (Manual — Fragmented) CS manually creates Team Account in backend. CS manually creates Stripe Payment Link. Customer pays. CS manually adds…
Current Process (Manual — Fragmented)
-
CS manually creates Team Account in backend.
-
CS manually creates Stripe Payment Link.
-
Customer pays.
-
CS manually adds Credit or activates Plan.
Issues: many handoffs → error prone, slow, poor customer UX.
Ideal Automated Flow (zero CS touch)
Step 1: CS enters customer phone → system auto-searches for existing ChatDaddy Team Account.
Step 2: If exists → link. If not → auto-create.
Step 3: Auto-generate Stripe Payment Link with metadata (phone, team_id, plan tier).
Step 4: Customer pays → Stripe webhook fires payment_intent.succeeded.
Step 5: Backend reads metadata + calls ChatDaddy API to provision Credit / activate Plan.
Step 6: Auto-send confirmation + welcome pack. Total: 3-5 minutes elapsed, zero CS intervention.
Tech Implementation
- Use ChatDaddy existing API (Team query, Credit add, Plan management).
- Add Stripe Payment Link with metadata.phone + metadata.team_id + metadata.plan.
- Set up Stripe webhook endpoint receiving payment_intent.succeeded.
- Webhook handler dispatches to ChatDaddy API. Feasibility: HIGH — all primitives already exist.
Interim Manual SOP (until automation lands)
- Build a Notion onboarding tracker with: stage (Quotation Sent / Paid / Activated / Welcome Sent).
- Standardise Stripe Payment Link notes (Team name, contact).
- Use a strict SOP doc with screenshots so every CS follows the same steps.
- Pair-check every new account in first 24h.
- Status emoji in WhatsApp group when each stage flips.
Recommendation
Submit to Pro Team as Q3 priority tech automation. Estimated dev effort: 1-2 sprints. Customer-facing impact: faster activation, fewer errors, better margin.