Skip to main content

​
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: 
Compare @Customer Data with @Competitor Target Market and see if there are any overlaps.
In this example:
  • @Customer Data and @Competitor Target Market are 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

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:
Compare @Customer Data with @Competitor Target Market to identify any overlaps in customer segments.
This will pull relevant data from both Collections and help you understand how your customer base compares to competitors.
If you’re a market analyst and want to examine insights across various datasets, you might have a Collection called Market Trends and nested sub-Collections for specific industries. To ask Storytell a targeted question, you might write:
What trends can I see in @Market Trends > @Tech Industry that might impact my portfolio?
This narrows the analysis to the Tech Industry sub-Collection, giving you focused insights.
If you’re a Product Manager trying to understand the competitive landscape for your product, you could create Collections like Product Features and Competitor Products. To ask a question comparing your product to a competitor, you might write:
How does @Product Features compare to @Competitor Products in terms of user experience?
This helps you focus on comparing specific features between your product and the competitors’.
If you’re a venture capitalist monitoring your portfolio companies, you could create a Collection called My Portfolio and use sub-Collections for each individual company. You might write:
What is the financial performance of @My Portfolio > @Company A in Q4 2024?
This helps you drill into the performance of a specific company within your portfolio to analyze it separately.
If you’re a Customer Success Manager analyzing feedback across customers, you could create a Collection for Customer Feedback. You could write a prompt like:
What is the overall sentiment in @Customer Feedback for Q1 2024?
This will provide you with insights into how customers feel about your product during that quarter, giving you a clearer picture of customer sentiment.

​
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.
This feature allows you to quickly find the right data for your queries without needing to manually navigate through your Collections.

​
Troubleshooting

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:
Compare insights from @Collection A with @Collection B.
This ensures Storytell knows exactly which data sets you want included in the response.