Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Product Demo

How Spara's Product Demo channel delivers live, voice-narrated product demos to prospects.

The Product Demo channel delivers live, interactive product demos over voice. It narrates your product's key features, shows matching screenshots on screen, answers questions naturally, and books a follow-up meeting at the end, all without a rep on the call. It lets every interested visitor get a fast, personalized walkthrough the moment they want one, instead of waiting for a human demo slot.

The Spara team handles the initial setup for your Product Demo channel. Your starting prompt, features, screenshots, and opening slide are built for you before handoff. Once you're live, you control the sections described below.

A Product Demo channel's Overview: its instructions, features, and visuals.

Editing the AI Instructions

The AI Instructions are the natural-language prompt that drives the channel's behavior: how it introduces itself, which features it covers, how it handles pricing questions, and how it wraps up the call. To edit them, open Product Demo, click into your channel, and go to the Instructions tab.

The prompt is broken into sections with clear headers. You can edit any of the sections listed under Sections you can edit below. Please leave the sections under Sections currently managed by Spara alone. Those depend on tools and pacing logic that Spara tunes centrally, and changes there can break calendar booking, call termination, or the ability to show visuals.

Sections you can edit

  • IDENTITY AND PRIMARY OBJECTIVE: who the channel is and what it's trying to accomplish on the call

  • PRONUNCIATION: how to pronounce brand names, acronyms, and any tricky terms

  • DEMO FLOW: the order and pacing of the demo

  • PRICING: how to talk about pricing when a prospect asks

  • BOOKING AND WRAP-UP: how to end the call and book a follow-up meeting

  • COMPETITOR EMPLOYEE RULE: how to handle someone from a competitor

  • VOICE RULES: delivery style, sentence length, pauses, no markdown, etc.

  • SELLING PRINCIPLES: your high-level philosophy on how it should sell

  • DEMONSTRATION STYLE: tone and interaction style during the walkthrough

Sections currently managed by Spara

  • show_calendar_widget

  • end_call

  • OFF-TOPIC

  • TOOL USAGE FOR DEMONSTRATIONS

  • PROGRESSIVE DISCLOSURE AND PACING

If you need changes to any of these sections, reach out to the Spara team.

Saving and publishing

Save changes to the prompt by clicking Save draft. Drafts are safe to iterate on. They don't affect prospects until you publish them, and you can test a draft using the demo link described in Testing your channel.

Click Publish when you're happy with the results. The published version is the one your prospects interact with. For more on the draft/publish flow, see Saving & Publishing.

Features

A feature is a single unit of your demo (one product channel, value proposition, or story) along with the screenshots shown while narrating it. The channel chooses which features to cover and in what order based on what the prospect is interested in, so good feature content is what makes the difference between a generic pitch and a tailored walkthrough.

Features are shared across all Product Demo channels in your account.

Creating and deleting features

Open Product Demo, click the Features tab, and click Create new to add a feature. Click an existing feature to edit it, or use the delete action to remove one you no longer need.

Editing a feature

Each feature has a Description (markdown content the channel reads) and one or more Visuals (screenshots or images it can show on screen during the demo).

Description. The description is what the language model reads when deciding how to narrate this feature. Keep it dense and concrete. Think "notes for a rep", not marketing copy. Spell out the exact proof points, objection-handling lines, and examples you want it to draw from.

The base prompt is tuned to look for a specific markdown structure in every feature, so sticking with these headers gives the best results:

Add as much guidance under each header as you need. The more specific, the better the narration will be.

Visuals. Every feature should have at least one visual. Visuals are the screenshots displayed while narrating this feature. Add more than one if you want to walk through multiple screens for the same feature; leave it at one if the feature is mostly conceptual. Use the visual selector on the feature page to attach assets.

A feature without a visual will still work, but there will be nothing to show on screen while it's talking. Prospects get a much better experience when every feature has at least one image tied to it.

Documents

The Documents tab in Product Demo settings lets you upload source documents (PDF, DOCX, or Markdown files) that the demo's ingestion pipeline uses to build knowledge for the channel. Use this for demo-specific reference material (white papers, battlecards, detailed feature specs) that you don't want appearing in the main Knowledge Base. Documents uploaded here are excluded from the Knowledge > Documents tab.

To upload a document, open Product Demo, click your channel, and go to the Documents tab. Click Upload and select a PDF, DOCX, or Markdown file. The document is processed in the background once uploaded. To edit or remove a document, click it in the list to open the edit drawer.

Opening slide

The Spara team currently controls the opening slide for your Product Demo channel. This is the first screen a prospect sees when the demo loads. If you want to change what's shown there, reach out to us and we'll update it for you.

Testing your channel

To test a Product Demo channel end-to-end, open it and click Open demo. This launches the demo in a new tab in test mode, running exactly as a prospect would experience it: voice, visuals, calendar booking, and all.

Use it to review your changes before publishing, and share the link with teammates on your Spara account for feedback. The workflow is: click Save draft, open the demo, talk through your changes, then click Publish once you're happy with how it sounds.

FAQ

Who controls what?

The Spara team handles initial onboarding: your starting prompt, the first set of features, the screenshots tied to each feature, and the opening slide. After handoff, you control the editable sections of the AI Instructions, the feature descriptions and visuals, the documents, and when to publish changes. For anything else (opening slide, tool sections of the prompt, or structural changes), reach out to Spara.

How do I know if a feature is working?

Open the demo with Open demo and ask about that feature directly. Listen for whether it mentions the hook, covers the key points you listed, and uses the right proof. If it's skipping things, tighten up the description and try again.

Can I test a draft before publishing?

Yes. Click Save draft, then click Open demo. The demo runs in test mode against your latest saved state, so you can iterate on the prompt and features before clicking Publish.

Can I link directly to the Product Demo from an email or CTA?

Yes. You can trigger a Product Demo session by calling SparaActions.openProductDemo() on your website. For email campaigns, add a query parameter to your landing page URL (e.g., ?demo) and include JavaScript on your site that checks for the parameter and opens the demo automatically.

See https://docs.spara.com/guides/product-demo-use-cases for step-by-step setup for website CTAs, outgoing email campaigns, chat-to-demo transitions, and more. For the full JavaScript reference, see https://docs.spara.com/developers/spara-api/javascript-api.

Last updated