While Dashworks can answer open ended questions, prompting it with an overall structure like this can improve its responses by providing it helpful context:
Task: What you need from Dashworks
Context: Background info or motivation behind what this is for
Response format: How should it format its response to be most effective
Search focus: Are there specific information sources it should focus on?
Task
Ask it to answer a direct question, find some docs, fix a bug, summarize notes, write an email, rephrase content for clarity, and more.
Context
Provide background on what this task is for as this can help Dashworks look for related information and focus the response on the key points based on the context. Please see the examples below for inspiration.
Response format
State the tone you want (ex. professional email, casual message), the response length (ex. short answer, one pager, report with max 3 paragraphs), and structure (blog outline, Twitter thread, bulleted list).
Search focus
Mention specific app names to search or specific files, folders, or project names in them. You can also add up to five URLs for some apps (like Google Drive and OneDrive) and Dashworks will use them as context to respond to the question.
Try it yourself with these examples
Find a case study
Task: find a case study with a fintech customer
Context: to share with Stripe's CMO who is interested in our omnichannel marketing platform
Response format: link
Search focus: Google Drive, Slack, website blog
Putting it together:
Do we have any case study links with fintech customers? I'd like to share them with Stripe's CMO who is interested in our omnichannel marketing platform. It'll likely be in GDrive, shared in Slack, or on our website blog.
Fix a bug
Task: fix the rate limit error for the analytics dashboard
Context: console log: 429 Too Many Requests while deploying Lambda
Response format: causes, solutions
Search focus: Github backend code, Confluence docs from Infra team, Slack threads
Putting it together:
Running into a rate limit error for the analytics dashboard, seeing this console log: 429 Too Many Requests while deploying lambda. Give me some likely causes and possible solutions. Check github backend code, confluence docs from the Infra team, and slack threads.
Summarize a product document
Task: summarize a PRD
Context: to catch up on upcoming initiatives from the Billing team
Response format: include 3 main pain points, proposed solutions, and next steps
Response format: motivations, key people involved, learnings, and follow ups
Search sources: -
Putting it together:
Can you give me a detailed overview of the AWS to GCP migration project that the Infra team worked on last year? This will be helpful to plan for 2025 OKRs. I'm looking for their motivations, the key people involved, learnings, and follow ups.
Debug a support ticket
Task: debug ticket #4321
Context: from Acme about integration issue with Airbnb
Response format: possible explanations, resolutions, and feature owner
Search focus: help center articles, Jira issues, Confluence docs, and Github pull requests in the integrations repo
Putting it together:
can you help me debug ticket #4321 from Acme about integration issues they're running into with Airbnb? Include possible explanations, resolutions, and the feature owner so I can reach out to them for further help if needed! Search help center articles, Jira issues, Confluence docs, and Github PRs in the integrations repo.
Prepare for a customer meeting
Task: summarize ongoing deal with Acme
Context: prepare for a meeting with their CTO to discuss the Europe rollout plan
Response format: 3-5 bullet points
Search focus: Salesforce notes, Slack conversations, Google Docs, and emails
Putting it together:
can you summarize the ongoing deal with Acme to help me prepare for a meeting with their CTO to discuss the Europe rollout plan? Please respond in 3-5 bullet points so I can get up to speed quickly! Look for information in Salesforce records, Slack conversations, Google docs, and emails.
Write a blog post
Task: write a blog post about the new API V2 release
Context: geared towards engineering leaders at small and medium enterprises
Response format: include the motivations behind shipping the API, example use cases this unlocks for engineering leaders, and a CTA for how to
get started. Optimize for conversion.
Search focus: Confluence PRD, API developer docs
Putting it together:
Write a blog post about the new API V2 Release geared towards engineering leaders at small and medium enterprises. Include the motivations behind shipping the API, example use cases this unlocks for engineering leaders, and a CTA for how to get started. Optimize for conversion. Use the info in Confluence PRDs and our API developer docs available at docs.acme.com.
.svg?alt=media&token=4dcba59f-0ed4-402a-88ba-6a9fa420bacf)