| Patient | Age | Therapist(s) | Package | Goals | ID | Status | Last seen |
|---|
🌅
Morning briefing
Coming in Phase 2
⏰
2 deposits overdue — action required
Kevin Wong (6h — cancel now) · James Ho (5h — remind now)
Today's schedule — Mon 16 Mar
Deposit tracker — pending confirmations
WhatsApp message preview
Select a booking above then tap an action to preview the auto-generated message
📅
Appointments
Coming in Phase 2
✅
Tasks
Coming in Phase 4A — Urgent · Today · This week · Custom
💬
Team chat
Coming in Phase 4B — General · Clinical · Assistant · DMs
Clinic configuration
Clinic: Speech Therapy, HK · Days: Tue–Sun · Hours: 9am–6pm
Session: 45 min · Currency: HKD · USD · Deposit: 6hrs (reminder 5hrs)
Form reminder: 24hrs before initial assessment · Languages: EN · 廣 · 普
Session: 45 min · Currency: HKD · USD · Deposit: 6hrs (reminder 5hrs)
Form reminder: 24hrs before initial assessment · Languages: EN · 廣 · 普
API configuration
WhatsApp Cloud API credentials are intentionally not stored in this page. Meta access tokens must stay server-side only.
WhatsApp Cloud API migration
Destination WABA onboarding
Loading WhatsApp migration status...
Important migration rule
Do not assume the old WABA ID migrates. Meta Embedded Signup must return the destination WABA ID and business phone number ID, and LEDO should store those new values for the clinic.
Connection status
Loading...
Checking current backend state...
WABA ID
Loading...
Store the new destination WABA ID returned by Embedded Signup.
Phone number ID
Loading...
Use this destination phone number ID for Cloud API registration and message sends.
Display phone number
Loading...
Visible clinic number after migration is confirmed.
Webhook status
Loading...
Verification GET and inbound POST live on the backend.
Cloud API registration status
Loading...
Phone registration must complete after the destination number ID is known.
Embedded Signup launches Meta directly. Webhook subscription, Cloud API registration, and final phone cutover still depend on server-side completion steps.
No WhatsApp admin action has been run yet.
Status source: waiting for backend.
WhatsApp Test Panel
Developer testing tools
Test credentials (saved locally)
Test phone number ID from Meta developer console.
Send test message
Received messages & account status
Polling paused
No account data yet.
Admin checklist
Meta Business verified
Required
Complete business verification in the destination Meta Business account before final onboarding.
Source WABA approved
Required
Confirm the source WhatsApp Business Account and number are eligible for migration before starting Embedded Signup.
Payment method attached
Required
Attach a billing method in Meta so the destination WABA can send Cloud API traffic after migration.
Two-step verification disabled on the WhatsApp phone number
Required
Turn off two-step verification on the migrating phone number before final registration.
ManyChat automations paused before final registration
Final cutover
Pause source-side ManyChat automations immediately before the destination registration step to reduce message routing conflicts.
Backend integration points
These are the backend hooks LEDO expects for WhatsApp Cloud API migration. The UI calls placeholder routes until the production server wiring is finished.
Database proposal
Recommended Supabase table for one clinic WhatsApp account record per clinic.