Skip to main content

Using @ to Specify Tools

When information could live in multiple places, use @ to tell Doe exactly where to look. This reduces errors and speeds up responses. Type @ and select from your connected integrations: Using @ mentions to specify tools in Doe Examples:
@Gmail show me emails from [email protected] about the Q4 budget
@Slack summarize the #engineering channel from last week
@HubSpot show me all deals over $100k in the negotiation stage
Instead of “Show me customer data” (which could come from anywhere), ask “@HubSpot show me enterprise customers created this quarter.”

Be Descriptive

Doe can’t read your mind. Like delegating to a colleague, describe what you want clearly. Doe learns your preferences over time, but you need to provide details upfront. Specify format:
  • “Show me Q3 revenue by region as a bar chart”
  • “Display as a table sorted by highest to lowest”
  • “Give me a bulleted summary, not a paragraph”
Add context:
  • Time range: “last quarter”, “past 30 days”, “year to date”
  • Filters: “only deals over $50k”, “excluding test accounts”
  • Grouping: “by department”, “by month”, “by region”
  • Sorting: “highest to lowest”, “alphabetically”
Vague: “How are we doing?” Better: “Show me sales performance for Q3 2024 vs Q3 2023, by region”

What to Avoid

Overly vague requests - “Show me data” doesn’t give enough direction. Be specific: “Show me Q3 sales from HubSpot for enterprise accounts” Visual design tasks - Doe handles data analysis, not design. Avoid “make this look modern” or “choose better colors.” Instead: specify what data to show and what type of chart. Subjective descriptions - Don’t say “make it better” or “find interesting patterns.” Be specific: “Sort by revenue” or “Show metrics where growth is above 20%“

Next Steps