Bullet · Support

Not live. There is no ticket system behind this — the tickets are synthetic and replies go nowhere. The customer details are the real records from the Onboarding Ops board, so what you see about someone's progress is honest. What the backend would have to expose to make this real: docs/BACKEND-QUESTIONS.md.

The loop tickets → dev → shipped → fewer tickets

What people are asking —

Mock — no AI is running and nothing is being learned. Tickets are matched against the customer app's Ask box, which already routes questions data vs how-to and hands how-tos to a named guide. Coverage is checked against the app's live how-to registry (fetched at runtime by js/registries.js — no hand-copied mirror). So this reads as: what could people already have self-served, and what should be added to the Ask box next. Real auto-answering needs the conversation history stored server-side — see BACKEND-QUESTIONS.md.

— · newest activity first

Select a ticket to read it.

—

Onboarding status —

Open their account Opens the customer's own app view. Mock — a real build needs staff impersonation with an audit trail.

Onboarding status is derived only from what the customer record holds: signup, activation and setup-review state. The Billing and Revenue tabs are placeholder data — no subscription field or ROS agent exists yet; both are mocks until the real wiring lands.