Pick the exact pilot owner and operator before any customer handoff is prepared.
Pilot customer workspace
Source-only pilot readiness for owner selection, manual route proof, draft records, prepared-not-sent copy, triage evidence and an owner handoff report packet before any live pilot action is approved.
Confirm the app, public and review URLs by hand for the selected pilot customer.
Keep contact rows and campaign rows as draft evidence until explicit data approval is fresh.
Prepare WhatsApp, email and owner text for review without queueing or sending anything.
Check private feedback, recovery and report evidence before owner or support handoff.
Package a manual handoff note while billing, provider sync and sending stay blocked.
Pilot intake desk
Turn one real business into a controlled first loop
This is the operator table for the first customer: collect facts, prove the route, choose the channel order, and keep the contact sample tiny until every live gate is approved.
Business name, location, operator name, and the exact Google review link are captured as manual facts before any import or send path is considered.
Open the public site, app workspace, and Google review route by hand, then record the pass/fail note for the selected pilot.
Choose WhatsApp-first, email-first, or manual-copy-first for the first loop, with no provider queue connected from this screen.
Use only 10-25 warm contacts for draft import testing after approval; no bulk list, cold outreach, or live send is allowed here.
Manual pilot proof run
Five checks before the first customer is treated as live
- Owner confirms the business and Google review link.
- Operator proves the review route manually on desktop and mobile.
- Tiny contact sample is checked for consent, duplicates, and formatting.
- Request copy is reviewed as human text before any automation decision.
- First owner report is prepared only after the manual loop has evidence.
Hard gates
Pilot movement beyond source-ready is blocked
Pilot movement beyond source-ready needs deploy verification, route approval, approved contact data, sender credentials, payment activation, support handoff, provider sync and customer outreach approval to be freshly verified for the current runtime.
Deploy verificationRoutesContact dataSender credentialsPayment activationSupport handoffProvider syncCustomer outreach
Readiness only, not a live-system action
This workspace is protected as source readiness. It does not deploy, import, sync, send, bill, mutate customer data, change routes or contact customers.
- No runtime deploy from /app/pilot.
- No route, DNS, Traefik or Cloudflare change from /app/pilot.
- No Appwrite schema/import or customer-data mutation from /app/pilot.
- No WhatsApp, email, SMS, provider queue or live sending from /app/pilot.
- No payment, checkout, subscription or billing activation from /app/pilot.
- No owner handoff, customer handoff, report delivery or outreach is triggered from /app/pilot.