> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/mcp/storylane-mcp/prompts-and-workflows.md).

# Prompts & Workflows

**Jump ahead:**

* [Prompt library](#prompt-library)
* [Product marketing workflows](#product-marketing)
* [Sales and AE workflows](#sales-and-account-executives)
* [Sales engineering workflows](#sales-engineers)
* [Customer success workflows](#customer-success)
* [Revops & Marops workflows](#revops-and-marketing-operations)

### **Prompt library**

Ready-to-paste prompts for running Storylane from your AI client. Pick one, copy it, and swap anything in \[brackets]. Here are a few of our favourites.

{% hint style="info" %}
The full set of 26 prompts, filterable by team, lives in the [MCP Prompt Library](https://www.storylane.io/mcp).
{% endhint %}

### Weekly report to Slack

A ranked digest of your top demos in the same shape every week, with movement called out instead of a wall of metrics.

{% prompt description="See the prompt" %}

```markdown
Using the Storylane MCP, build this week's demo performance report.
Pull demo analytics for the last 7 days and compare against the previous 7. Exclude internal team views, I only want real prospect sessions.
Take the top 5 demos by sessions. For each, capture sessions, engagement rate, CTA clicks, and the change vs last week.
Also flag the single biggest mover, even if it sits outside the top 5.
Use demo names, never IDs.
Format it exactly like this, every week:
Storylane demos, week of [date]
Top 5 by sessions
[name] - [n] sessions ([+/-]%) · [x]% engaged · [n] CTA clicks
Biggest mover: [name] [+/-]% - [what changed, one clause]
Watch: [one demo with a drop or weak progression, one line]
Then post it to [#marketing]. Ignore moves under 10% as noise.
```

{% endprompt %}

### Personalized leave-behind

A tailored demo, a tracked link, the CTA set, and an opener ready to send, built after a call.

{% prompt description="See the prompt" %}

```markdown
Using the Storylane MCP, build a leave-behind demo after my call.
Company: [NAME], [industry]
They cared about: [TOPICS]
Objection raised: [OBJECTION]
Base demo: [DEMO NAME]
Work on a copy, never edit the original.
Personalize it for this company: emphasize what they cared about, address the objection, keep the tone confident and concise. Tie it to something specific from the call, not just the company name.
Poll until personalization completes.
Publish the copy. It stays a draft with no shareable link until you do.
Set the CTA to "[Book a follow-up]" pointing at [MY BOOKING LINK]. Copies inherit the base demo's CTA, so always set this explicitly.
Create a tracked share link with the company name as a variable.
Give me the link plus a two-sentence follow-up opener I can send as-is.
```

{% endprompt %}

### What buyers are asking RepX

Every topic your agents have been asked about, ranked, with the ones you have no answer for flagged.

{% prompt description="See the prompt" %}

```markdown
Using the Storylane MCP, tell me what buyers have been asking RepX about.
Pull the full topic list with session counts.
Group topics that are clearly the same subject under different IDs.
Rank by session count and show me the top 15.
For the top 5, tell me whether we have a page, a demo, or a doc that answers it.
Flag any topic in the top 15 where the honest answer to step 4 is "nothing". Those are the content gaps.
```

{% endprompt %}

### **Product marketing**

#### **Create a launch demo from media**

1. Upload screenshots or a screen recording.
2. Create the demo with `convert_images_to_demo` or `convert_video_to_demo`.
3. Check completion with `get_demo_status`.
4. Set the title, description, branding, and gating with `update_demo_settings`.
5. Publish it with `publish_demo`.

Pair this workflow with Linear or Jira. Create demos from completed feature tickets.

#### **Audit your demo library**

1. List published demos with `list_demos`.
2. Retrieve analytics for each demo with `get_demo_analytics`.
3. Rank demos by engagement.
4. Flag low-performing demos for updates, personalization, or retirement.

Try this prompt:

> List all published demos. Show demos below 40% completion that had no views in 30 days. Rank them worst to best. Recommend an action for each.

#### **Apply your brand theme across demos at scale**

1. List available themes with `list_themes`
2. List demos with `list_demos`
3. Filter by demos missing the correct theme or label
4. Apply the right theme and labels with `update_demo_tool`

Try this prompt:

> List all published demos. Check which ones don't have the \[THEME NAME] theme applied. Apply it to all of them.

### **Sales and account executives**

#### **Prepare a personalized demo before a call**

1. Find relevant demos with `list_demos` and `get_demo`.
2. Create an account-specific variant with `personalise_demo`.
3. Publish it with `publish_demo`.
4. Generate a trackable link with `create_link`.

Combine this workflow with HubSpot or Salesforce. Log the generated link on the contact record.

#### **Prioritize follow-ups from engagement**

1. Get recent leads with `get_leads`.
2. Review account activity with `get_accounts`.
3. Rank accounts by engagement.
4. Draft follow-up actions for hot, nurturing, and inactive accounts.

#### **Build an AI Hub for a prospect in seconds**

1. Find relevant demos with `list_demos`
2. Create the hub with `create_hub` — pass the prospect's company name and a note on use case or audience
3. Poll with `get_demo_status` until the hub is ready
4. Generate a tracked share link

Try this prompt:

> Create an AI Hub for \[COMPANY NAME]. They're a \[INDUSTRY] company focused on \[USE CASE]. Use our best demos and make it feel like we built it specifically for them.

#### **Prioritize outreach from active deals**

1. Pull active deals with `list_crm_deals` — filter by pipeline and stage
2. Cross-reference with demo engagement from `get_accounts`
3. Rank deals by engagement and recency
4. Personalize a demo for the top accounts with `personalise_demo` and create tracked links

Try this prompt:

> Show all active deals in \[PIPELINE] at \[STAGE]. Cross-reference with Storylane engagement. Rank by who's most active and hasn't been followed up with. Personalize a demo for the top 3 and send me tracked links.

### **Sales engineers**

#### **Convert a screen recording into a demo**

1. Convert the recording with `convert_video_to_demo`.
2. Add missing steps with `add_step`.
3. Select narration options with `list_voices`.
4. Publish the demo and create a prospect link.

#### **Plan an enterprise deal hub**

1. Find persona-relevant demos with `list_demos` and `get_demo`.
2. Review existing hubs with `list_hubs` and `get_hub`.
3. Personalize selected demos with `personalise_demo`.
4. Create a recommended hub structure for the buying committee.

### **Customer success**

#### **Refresh stale onboarding demos**

1. List onboarding and help demos with `list_demos`.
2. Find low-engagement demos with `get_demo_analytics`.
3. Prioritize demos to update, recreate, or retire.

#### **Identify customer expansion signals**

1. Query customer engagement with `get_accounts`.
2. Check demo-level activity with `get_demo_analytics`.
3. Flag customers exploring advanced features for follow-up.

### **RevOps and marketing operations**

#### **Send a personalized demo when a deal reaches Demo stage**

1. Trigger the workflow from a CRM stage change.
2. Find a relevant demo with `list_demos`.
3. Personalize it using CRM data with `personalise_demo`.
4. Publish the demo and create a tracked link.
5. Write the link back to the CRM record.

Use HubSpot, Salesforce, Zapier, or webhook workflows as the trigger.

#### **Manage alerts programmatically**

1. List existing alerts with `list_alerts`
2. Identify gaps — demos with no alerts, or alerts with outdated conditions
3. Create new alerts with `create_alert` — set demos, labels, Slack channels, and CRM stage triggers
4. Update existing alerts with `update_alert`

Try this prompt:

> Show all active alerts. Find any demos that have no alert set up. Create a Slack alert for each one that triggers when a contact from an active deal views it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.storylane.io/mcp/storylane-mcp/prompts-and-workflows.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
