Tours that need data do not require the tenant to have any. One rich demo lead is seeded per user, per org, straight onto the real board, and deleted again when the tour ends. It is fenced so it cannot leak into anything that matters: no CRM push, no analytics, no leaderboard, no follow-up automations, and an email address on a reserved non-deliverable domain.
Also called: sandbox lead · practice mode · test lead · safe to experiment
- 1The tour calls ensure; the route idempotently creates one lead with a deterministic id prefixed 'demo-'
- 2The card is assigned to the caller so it is visible under 'Mine' and stays off the manager backlog hold
- 3The client paints an optimistic card instantly and then merges the authoritative fields from the response — no server re-read
- 4Cleanup deletes only rows where is_demo is true AND the demo owner is the caller, inside their org
- 5Every demo-route call resolves within a hard 15s timeout; a failure degrades the tour to an explainer card instead of wedging it
Nobody learns a sales pipeline by reading about it, and no owner wants a new hire practising on a live $80,000 opportunity. So a lesson that needs a lead gets its own, clearly badged, dropped onto the real board and assigned to the person taking it, then removed when they finish. It is fenced so practice cannot contaminate the business: the address cannot receive mail, nothing is pushed to the CRM, and it never appears in analytics, the leaderboard or anyone's rep score. A trainee moving a practice card through five stages does not quietly become the top rep that week.
- Training on live records risks emailing or texting a real customer
- Practice records contaminate analytics, leaderboards and rep scores
- New tenants have no data, so data-dependent tutorials cannot run at all
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →