Demo mode

Demo mode is a working tour of the platform that never touches a real account. It looks and navigates like the live product, filled with the data of a fictional business, so you can walk a prospect through the platform without setting anything up and without any risk of sending, publishing, or charging anything by accident.

This page is for partners who present the platform to their own clients.

New to the demo? Start with Running the demo — a partner's guide: a step-by-step walkthrough with the full list of example prompts, the scenarios they support, and an inventory of everything the fictional workspace contains.

What exists today

You can open any page, move between sections, and look at everything the fictional business has built: its campaigns, contacts, segments, journeys, analytics, reports, and settings, plus the content the assistant created for it.

You can also build something new in front of the prospect. Click one of the suggested prompts above the message box and the assistant answers the way it does in the live product — thinking, using its tools, and streaming the work as it goes — and what it produces lands in the library, on the calendar, and anywhere else it belongs, exactly as the real thing would.

Two things are worth knowing before you lean on this:

• Use the suggested prompts. They are the ones the demo has an answer for. Click the + beside the message box and choose Examples: a searchable list opens, grouped by what you are making (events, web pages, journeys, email, images, social). You can type anything you like, but a question outside that set gets a short note saying it is outside the guided demo rather than a live answer, which is a flat moment in front of a prospect. Worth opening that list once before your first call so you know what is in it.
• It is a recording, not a live model. Each prompt replays a real assistant turn that was captured ahead of time, so it is the genuine output rather than a mock-up — but it is the same answer every time, and it cannot follow up on a prospect's variation.

Getting in

1. Open the demo link your partner contact gave you. Access is per partner: your organisation has its own link, and the plain demo address will not let you in. There is no shared access code.
2. Enter your name and your work email.
3. You land inside the demo, on the page you opened. If you followed a deep link to a specific page, you are taken to that page once you're in.

Your name and email are recorded against your organisation when you sign in. That is how we know which partners are actively using the demo. The name you enter is also what the account menu shows during your session, so a prospect watching your screen sees your name rather than a placeholder.

If you are told the demo needs an invitation link, you have opened it without yours — go back to the original email. If you are told the link has been turned off, contact your partner contact for a new one.

What's safe to do: everything

Demo mode has no backend at all. The whole tour runs in your browser, answering from a snapshot of data that was recorded ahead of time and shipped with the page. There is no database behind it and no account behind it, so:

• Nothing sends email or SMS.
• Nothing publishes to a website or a social channel.
• Nothing charges a card or changes a plan.
• Nothing you do is saved.

Click anything. Open any setting, any report, any record. You can't break anything and you can't reach anyone.

The one exception is the sign-in form itself. When you enter your name and email, that single submission is sent so we can check your organisation's link and record who signed in. After that, the tour makes no calls of its own.

Signing out resets the demo

Everything you do in the demo lives only in the open browser tab, and nothing reaches a server. It does survive a page refresh: reloading mid-presentation keeps you signed in and keeps what you have built, so an accidental refresh — or a deep link you paste into the address bar — no longer costs you the thread in front of a prospect.

To start fresh, sign out from the account menu in the top-right. That clears your details and everything the tour created, and brings back the sign-in form. Do that before each client call and you are guaranteed a clean starting point rather than whatever the last session left behind.

Closing the tab has the same effect, since nothing is kept once the tab is gone. Opening the demo in a second tab gives you a second, independent session — the two do not share what you build in them.

A suggested run of show

The demo is built around one story, because a single connected story lands better with a prospect than a tour of features: running a webinar, end to end. A good order to walk it:

1. The event. Show the webinar, its date, its speakers, and its details.
2. The registration page. Show the page a visitor would sign up on, connected to the event.
3. Publishing it. Explain that publishing puts that page live for visitors.
4. A contact registering. Explain that when someone registers, they are added as a contact and attached to the event.
5. The journey picking them up. Show the journey that sends the confirmation and follow-ups from the moment someone registers. Edit journey opens the builder on it, so you can walk the steps on the canvas — trigger, confirmation, wait, reminder, the attendance branch — instead of describing them. Changes you make there stay in your tab like everything else, and the journey goes back to how it was when you sign out.
6. The analytics and the report. Finish on the results: who registered, who attended, and the report that summarizes the campaign.

Most of it you can do live: have the assistant create the event and build the registration page while the prospect watches, open the page it produced, and publish it. Nothing is sent and nothing is published anywhere real — the page you "publish" exists only in your browser tab.

Steps 4 and 5 — a visitor actually filling in the registration form, and the journey picking them up — are still ones you describe while showing the finished result. The fictional business already has registrants and a journey that ran, so you have real screens to point at; what you cannot yet do is submit the form yourself and watch a new contact appear.

The strongest version of the demo is a mix: build one or two things live so the prospect sees the assistant work, then move to the finished campaign and its analytics, which took a fictional quarter to accumulate and cannot be produced in a meeting.

You don't have to follow this order. Settings, the contact database, and the reports all stand on their own for shorter conversations.

Where the data comes from

The demo shows a fictional business, with fictional contacts, content, and results. It does not contain any real customer's data.

The data is refreshed nightly from the current version of the product, so the demo always matches what the platform looks like today rather than an old build. New features and changed screens appear in the demo after the next nightly refresh.

The assistant's answers are recorded separately and less often, because each one is a real assistant turn. If a suggested prompt produces something that looks out of date next to the rest of the tour, that is why — tell your partner contact and it can be re-recorded.

If something looks off

• A page looks empty or is missing something. The demo only contains what was captured in the nightly recording. If a page you expected to be populated is blank, tell your partner contact which page it was; a gap in the recording is something we can close.
• The assistant says your question is outside the guided demo. You typed something the demo has no recording for. Open + → Examples beside the message box and pick from there; those are the ones it can answer live.
• You're asked to sign in again. You signed out, or you are in a new tab. A refresh on its own no longer signs you out.
• You want to start over. Sign out from the account menu — that clears your details and everything the tour created. (A refresh no longer resets it.)