Shortcuts are saved prompts that help you quickly reuse the same instruction again and again. They make it easy to get consistent results and to share useful workflows with your teammates.
Use the tips below to create shortcuts that are clear, reliable, and easy for anyone to use.
1. Say What Role You Want the AI to Play
A shortcut works best when it knows what kind of help you’re looking for.
Examples
“Act like a professional coach”
“Write an update for my manager”
“Summarize this for my team”
2. Ask for a Clear Format
Shortcuts are easier to read and reuse when the output is well organized.
Examples
“Use sections like Decisions and Action Items”
“Use bullet points”
“Keep it short and easy to scan”
3. Focus on What Matters Most
A good shortcut helps filter out noise and focuses on what actually matters — like decisions, risks, and next steps.
Examples
“Only include decisions and next steps”
“Highlight risks or blockers”
“Skip casual or social conversation”
4. Make the Output Actionable
Good shortcuts help you act, not just read.
They should clearly show what needs to happen next, what to focus on, or what requires follow-up. This turns meeting information into progress, instead of just notes.
Examples
“End with next steps”
“List my priorities for the week”
“Call out anything I need to follow up on”
5. Use Tools to Get More Done
Just like you can use tools while chatting with Ask Fellow, you can also use them in shortcuts.This means a shortcut can do more than generate text. The available tools include:
Create a document
Write an email
Clip a recording
Share a meeting to users and channels
View, create, update, and delete calendar events
Check teammates' calendar availability
Find and track action items
Many more
Shortcut Examples
Write a follow up email
Write a clear and concise follow-up email from this meeting. Take into account my job title, meeting title, description, whether the meeting is internal or external, and the AI notes from the meeting to make it highly contextual and specific. Focus on making the email action-oriented and list out any commitments that were discussed. When you write the email, do not surround it with any commentary, instruction, summary, or explanation.
Create a knowledge based doc
Your task is to create an internal knowledge base article about a product feature or process for team use based on this meeting. First, identify the features or processes identified and provide a 1-2 sentence summary of what it does. Wait for the user to confirm the feature they want to focus on before drafting the article. After confirmation, write the article using this format:
Overview Summarize what this feature or process does and why it matters internally.
When to Use It Explain in what situations or workflows this feature/process should be used (optional if self-explanatory).
How to Use / Follow the Process
Customer feedback
Your task is to analyze a customer meeting for feedback. Group insights into short themes (2 to 4 words), each starting with a relevant emoji. For each theme, output in this order:
##**Theme Title**
**Implication:**
One clear, actionable takeaway on what the product should improve, add, or emphasize, including any tradeoffs.
**Quotes:**
A bullet list of 1 to 3 verbatim product-related quotes with persona tags, labeled as positive, frustration, or request.