Overview
By using the@ symbol, you can mention existing Collections or Files directly within your prompts. This allows you to pinpoint the scope of your query and receive more relevant results.
Mentioning Collections in Your Prompts
To specify the scope of your query, simply type@ followed by the name of an existing Collection in your prompt. This will allow you to focus your analysis on specific data sets that you’ve created or that have been shared with you.
For example, let’s say you want to compare customer data with competitor insights. You can type the following in your prompt:
@Customer Dataand@Competitor Target Marketare Collections that either you’ve created or have been shared with you.- Typing
@into the prompt input field will bring up a list of your Personal Collections and Shared Collections. - You can either select an existing Collection from the list or continue typing to narrow it down.
Using
@ enhances your ability to target specific data sets and generate more accurate results.Example Use Cases
Analyzing Customer Data
Analyzing Customer Data
If you’re a Product Manager and you want to compare your Customer Data to competitors’ target markets, you could use a prompt like this:This will pull relevant data from both Collections and help you understand how your customer base compares to competitors.
Market Analysis Across Multiple Data Points
Market Analysis Across Multiple Data Points
If you’re a market analyst and want to examine insights across various datasets, you might have a Collection called This narrows the analysis to the
Market Trends and nested sub-Collections for specific industries. To ask Storytell a targeted question, you might write:Tech Industry sub-Collection, giving you focused insights.Product Comparison Analysis
Product Comparison Analysis
If you’re a Product Manager trying to understand the competitive landscape for your product, you could create Collections like This helps you focus on comparing specific features between your product and the competitors’.
Product Features and Competitor Products. To ask a question comparing your product to a competitor, you might write:Tracking Portfolio Performance
Tracking Portfolio Performance
If you’re a venture capitalist monitoring your portfolio companies, you could create a Collection called This helps you drill into the performance of a specific company within your portfolio to analyze it separately.
My Portfolio and use sub-Collections for each individual company. You might write:Customer Sentiment Analysis
Customer Sentiment Analysis
If you’re a Customer Success Manager analyzing feedback across customers, you could create a Collection for This will provide you with insights into how customers feel about your product during that quarter, giving you a clearer picture of customer sentiment.
Customer Feedback. You could write a prompt like:Mentioning Files in Your Prompts
To mention a file, simply type the@ symbol followed by the file name, similar to how you mention Collections. The more precise the file name you provide, the easier it will be for Storytell to locate the files you want to mention.
You can mention multiple files in your prompts, enabling you to specify which assets you want Storytell to draw insights from.
As you continue using Collections and Files, it’s helpful to keep your naming conventions clear and consistent, making it easier to search for relevant data in future queries.
Searching for your Collections and files
When you type@, a search box will appear showing your existing Collections and assets. If you’re not sure of the exact name, you can start typing and the list will filter in real-time based on your input.
- Personal Collections: These are Collections you’ve created.
- Shared Collections: These are Collections that have been shared with you by other users.
Troubleshooting
Error when @mentioning a Collection inside another Collection
Error when @mentioning a Collection inside another Collection
When you’re scoped into one Collection (e.g., Collection A) and try to @mention another Collection (e.g., Collection B), Storytell may not automatically resolve the reference. This can result in errors, even if both Collections contain assets that should be in scope.Workaround:
If you want to compare or pull insights across multiple Collections, mention both Collections explicitly in the same prompt.
For example:This ensures Storytell knows exactly which data sets you want included in the response.