Notes
Context is all you need
Notes allow you to add useful context to Dot or to provide instructions on how to behave in certain situations. Helping business users with their data questions or creating an impactful churn analysis requires Dot to understand more about your business and your information architecture than can be found on the internet (usually).
Here are four types of notes that we found to be most useful:
Organization Notes
This is Wikipedia style knowledge about your company, the products and services your selling, the internal processes that you follow, etc. While these things can change aim to go top down and start with the things that are probably still true two years from now.
Example
TinyTrucks is a children's toy company.
We manufature educational and entertaining toy trucks.
We sell directly them online to parents in Europe and the US.The example is a lot shorter than what you usually want to add as background.
Agent Operating Principles
These are instructions on how to behave in certain situations and what principles to follow. The key is to write these as instructions and to use strong language with words like: Always, Never, Only
Example
Always clarify with the user if they want live or booked revenue when they ask about revenue.
Always by default filter out internal users (IS_INTERNAL = FALSE).
Always use the table fct_arr_consolidated when this table is enough to answer questions about ARR.
Never answer questions about a/b tests and rather refer them to https://experiments.internal.comPlaybooks / Use Cases
For your high value use cases, you already have a lot of intuition and tribal knowledge on how to analyze certain situations. For example, when you review a marketing campaign, you have your go to data sources, you know which metrics you care most about, how you think about attribution etc.
Playbooks are about encoding and documenting this knowledge, so that the analytics agent can replicate it.
Example
Metric Glossary
You wouldn't trust an analyst that regularly reports different numbers than what your well-maintained dashboards show. It's not because the numbers are necessarily wrong, but since they are inconsistent you have to figure out which one is more correct. A metric glossary can help with that. Here you just list all your most important KPIs/metrics with
name of metric
short description (maybe with synonyms)
query on how to calculate the metric
Dot will use those definitions when giving answers.
Example
This is our metric glossary.
Always use the definitions specified here to write queries
## ARR: Annual Recurring Revenue
```sql
SELECT sum(contract_value)
FROM opportunities_table
WHERE status = 'closed'
```
## NRR: Net Revenue Retention
...Last updated