Client setup
Every customer gets a workspace, account code, widget, and proof path.
Every client app should launch with the same real operating path: public app, lead capture, FS27 records, Relay13 workspace thread, ConnectLog event trail, SkyePay continuation, and optional paid AI lanes with backup buckets.
Setup rooms
The handoff is repeatable.
METRAIYUX-0S-SKM
Owner public-site workspace. Relay13 slug: connectlog-main.
BOBS-SMOKE-SHOP-SKM
Bob's Smoke Shop client/test workspace. Relay13 slug: bobs-smoke-shop.
EMPIRE-PALLETS-SKM
Empire Pallets client/test workspace. Relay13 slug: empire-pallets.
New Client
Create workspace, allow domain, publish widget config, then run the proof room.
Launch checklist
Do this for every client before calling the app done.
Public App
Logo intro, full app, obvious download button, QR-ready URL, and working mobile scroll.
Lead Capture
Forms post into FS27 and write lead, contact, activity, campaign, source URL, and workspace slug.
Workspace Thread
Relay13 receives the request in the client's own workspace so the owner has a dedicated inbox lane.
ConnectLog Record
ConnectLog mirrors the request as a relationship event for follow-up, proof, and later reporting.
What to tell the owner
Their customers can use the app. The owner can answer or route.
Direct Route
Customer asks for owner attention. Thread is held for human/operator handling.
Local Brain Route
The default brain classifies the request, keeps cost at zero, and leaves the reply under owner control.
Paid AI Draft Route
Starter drafts 125 replies plus 31 backup messages. Response Plus drafts 425 plus 76. Both remain owner-reviewed after SkyePay activation.
Managed AI Inbox
Managed starts at 1,000 messages plus 222 backup and actually runs the inbox: triage, labels, allowlisted routine replies, timers, summaries, and escalation.
ConnectLog Route
Sales, follow-up, vendor, or client relationship threads become cards and request records.
Gate Route
SkyeGate/SkyeMerit tracks account code, billing posture, and proof lane.