Running the demo — a partner's guide
A step-by-step guide to presenting the platform using the demo version. It covers how to get in, the scenarios the demo supports, exactly how to run the example prompts, and an inventory of everything the fictional workspace contains so you know what you can point at.
For the shorter "what it is and what's safe" summary, see Demo mode. This page is the one to read before your first presentation.
1. Getting in
- Open the demo link your account team sent you. The link is specific to your organisation — keep it, because the plain demo address will not let you in.
- Enter your name and work email at the gate. There is no password; the name and email are only used to make the workspace look like yours during the session — the account menu and the greeting pick them up.
- Click Enter demo.
If you see "This demo needs an invitation link", you have opened the demo without your link — go back to the original email. If you see "This demo link has been turned off", contact your partner manager.
You land in Zava, a fictional AI-infrastructure company mid-way through launching a product called Atlas 2. The chip in the top right reads Demo Version throughout, so nobody in the room mistakes it for a live account.
One tab, one demo. Everything you do lives in that browser tab. Opening a second tab starts a fresh demo with a fresh gate — and needs the link again, so open it from the email rather than retyping the address.
2. Before you present: the three things to know
Nothing you do leaves the browser. No email or SMS is sent, nothing is published to a real website or social account, no card is charged, no account is created. The entire workspace — every page, every number — is served from inside the page itself.
Changes stick until you sign out. Publish a page, rename an artifact, add a sender, edit a journey: it stays changed for the rest of your session, so you can build something early and refer back to it later. Signing out is the reset — use the account menu, top right, when you want a clean workspace for the next prospect. Reloading the page does not reset it.
It is a recording, not a live model. Each supported prompt replays a real session the assistant actually produced — the same thinking, the same tool calls, the same streaming. It is faithful, but it only knows the prompts listed below.
3. Two ways to use it
Most good presentations mix both.
Tour what is already there. The workspace has a fictional quarter of history behind it — campaigns with real numbers, a journey that has been running for 38 days with three failed runs, a sent email with a full delivery funnel. This is the half you cannot produce live in a meeting, and it is usually the half that convinces people the product is real.
Build something in front of them. Run one of the example prompts and let the prospect watch the assistant work — plan, call its tools, stream the result — and then open the thing it made. This is the half that shows what the product does.
4. Running an example prompt
The prompts are listed in the app, so you never have to memorise one.
- Open a campaign and start a new session, or use the message box on any campaign page.
- Click the + button beside the message box.
- Choose Examples. A searchable list opens, grouped by what you are making: events, web pages, journeys, email, images, social, and so on.
- Click a prompt. It fills the message box.
- Press Enter.
The assistant answers the way it does in the live product. A long one takes a minute or two; let it run rather than clicking away — the artifacts land at the end.
You may also type a prompt by hand, as long as it matches one on the list. Capitalisation, extra spaces and a trailing full stop do not matter.
If you type something else, the assistant replies "That one is outside this guided demo" and shows you the list of prompts it does know. Nothing breaks — but it is a flat moment in front of a prospect, so prefer the Examples list.
5. Supported scenarios
The connected story: running a webinar end to end
Four prompts that build on each other. Run them in this order and each one picks up what the last one made — this is the strongest ten minutes of the demo.
| # | Prompt | What you get |
|---|---|---|
| 1 | Create a virtual webinar for November 18th at 2pm America/New_York called "Shipping Agents to Production", 45 minutes, with no speakers for now. | The event, with its date, capacity and registration tracking |
| 2 | Build a registration landing page for the Shipping Agents to Production webinar with a signup form. | A finished landing page bound to that event — open it, then publish it |
| 3 | Build a journey for people who register for the Shipping Agents to Production webinar: confirm by email right away, remind them 24 hours before, and text anyone who has not opened the reminder. | A draft journey on the canvas, with the confirmation and reminder written |
| 4 | Show me how the Atlas 2 Live Walkthrough performed — registrations, attendance, and which emails drove signups. | A performance report on the webinar that already ran |
Step 4 reports on the completed walkthrough that is already in the workspace, not on the one you just created — which is the honest way to show results, since a webinar created two minutes ago has no attendees.
Standalone scenarios
Each of these stands on its own; run whichever fits the conversation.
| Ask about | Prompt |
|---|---|
| Campaign planning | Plan a Q1 campaign to convert our Atlas-line accounts onto the Atlas 2 platform — channels, timeline, and the assets we would need. |
| Broadcast email | Draft a broadcast email to the Atlas-line accounts segment announcing our new agent observability dashboard … Leave it as a draft, do not send or schedule it. |
| Email templates | Design a reusable one-column email template for our monthly platform newsletter: a header, a lead story, two short updates, and a footer with an unsubscribe link. |
| SMS | Draft a text to the Atlas-line accounts segment about the Atlas 2 launch, under 160 characters. Leave it as a draft. |
| Social | Draft one LinkedIn post and one X post promoting the Atlas 2 launch — text only, no image, and leave them as drafts. |
| Image generation | Make a 16:9 hero image for the Atlas 2 launch landing page — abstract, no text in the image. |
| Documents | Put together a one-page PDF leave-behind on the Atlas 2 platform: what it does, the 30% agent-throughput gain, and three bullets on migrating off the Atlas line. |
| Segmentation | Create a segment of contacts in Germany, Austria or Switzerland whose job title mentions Platform and who opened an email in the last 30 days. |
| Adding a contact | Add Dana Whitfield, VP of Engineering at Harbor Cloud Systems, dana@harborcloud.example. |
Use the Examples list rather than retyping these — the table is here so you can plan your run of show in advance.
6. What is already in the workspace
Everything below is there before you type anything, and all of it is worth pointing at.
Campaigns — 4
- Atlas 2 Product Launch — the main one. A goal, a budget in EUR, a written brief, KPIs, a UTM slug, an attached and summarised spec sheet, and a plan with 8 included items.
- Atlas 2 Live Walkthrough (Webinar) — the event, its registration page, the confirmation template and the reminder SMS, with its own session.
- Q1 Platform Credits Promotion — a finished promotion that missed its target, useful for showing reporting on something that did not work.
- Onboarding
Sessions with real conversations
Every seeded session opens on the conversation that produced its work — the launch kickoff, the webinar prep, building the registrant journey, and two finished automations. Scroll one to show how the assistant and a marketer actually talk, with the artifacts landing inline as they are made.
Artifacts — 12, one of every kind
Blog post · Document (spec sheet) · Email · Email template · Event · File · Image · Insight · SMS draft · Social post · Web page · AI visibility report
Reachable three ways, and all three open the artifact:
- Artifacts in the left nav — click any row.
- The artifact types listed under a campaign in the navigation panel. Where a type holds a single artifact, as most do here, clicking it opens that artifact directly; where it holds several you get the Library filtered to that type.
- Each campaign's Library, and the session that created them.
Audience
- 800 contacts, with lifecycle stages, sources, companies and engagement history. The list pages 50 at a time.
- 6 segments, including an AI-defined one ("opened an email but never clicked"), keyword-defined ones, and a deliberately stale one so you can show the refresh affordance.
- A suppression slice of 40 addresses, so deliverability has something to report.
Automations — 3 active
- Atlas 2 webinar registrant journey — live for 38 days, 13 contacts through it, 3 failed runs on the Failures tab worth diagnosing. Click ✎ Edit journey to open the builder canvas and walk the steps: trigger, confirmation, wait, reminder, business-hours window, attendance branch.
- New-account welcome series
- Weekly deliverability digest — a routine rather than a journey.
Reporting
- The launch email's delivery funnel: 1,284 sent, 1,247 delivered, 562 opened, 193 clicked, with email clients, a click report, and 17 recipients the dispatch gate held back.
- The registration page's traffic (1,842 pageviews, top referrers) and form stats (193 submissions, 186 matched to contacts).
- The webinar's attendance: 120 registered, 68 attended, broken down by segment.
- Pulse and the campaign Insights tabs.
Settings — all populated
Business DNA (brand book, voice, imagery) · Users · Email (verified domain, senders, link branding, subscription lists) · SMS · Integrations · MCP Tools · Contact fields · Guards · Privacy · Usage.
The arbitration brief — the rules deciding which campaign wins a contact — is at /settings/arbitration by direct URL; it is deliberately not in the sidebar.
7. What the demo will not do
Be straight about these if they come up; each has a good answer.
- It will not answer an unlisted prompt. It says so and offers the list.
- You cannot fill in the registration form yourself and watch a new contact appear. Show the 186 registrations that already exist instead.
- Connecting a real integration is switched off. The Connect buttons on Integrations and MCP Tools are greyed out — a real connection would send the prospect to a third-party sign-in page.
- An artifact the assistant makes during the demo can be opened from the session it was made in. Its standalone detail page is not part of the recording.
- Nothing is saved. Close the tab or sign out and the workspace is as it was.
8. If something looks off
- A page looks empty. The demo contains the fictional business's data and nothing else — an empty list usually means that area genuinely has no data for this business. Move on rather than digging.
- The assistant says your question is outside the demo. You typed something that is not on the list. Use + → Examples.
- You are asked to sign in again. You signed out, or you are in a new tab. Enter your name and email again.
- You want to start over. Sign out from the account menu. That clears everything you changed and returns the workspace to its starting state.