Hilda
How to brief Hilda
1
Trigger phrases
Hilda responds to natural language. She routes based on keywords — use these patterns:
| Task type | Trigger phrase examples |
|---|---|
| Create a deliverable | "write [X] for [client]", "build a [report/strategy/campaign] for [client]" |
| Run a check-in | "mid-month check-in for [client]", "how is [client] tracking" |
| Audit | "audit [client]'s Google Ads", "run an SEO audit for [client]" |
| Planning report | "pull the planning report for [client]", "end of month report for [client]" |
| Brief code work | "brief this for Code", "write me a brief", "brief it up" |
| Onboarding | "new client just signed", "process this acceptance email" |
| Support reply | "reply to this client", "handle this support email" |
2
What she needs
For deliverables to be high quality, Hilda needs the client's Source of Truth doc to be populated. Before briefing a new piece of work:
- Check the client's Source of Truth doc in ClickUp is up to date
- Confirm which channels are active for that client
- Include the client name exactly as it appears in ClickUp
3
Output types
| Output | Format | Where it lands |
|---|---|---|
| Planning report | .docx | Google Drive → HH Clients → [Client] |
| Mid-month check-in | .md + hh-internal page | Google Drive + hh-internal.vercel.app/check-ins |
| Strategy doc | .docx | Google Drive → HH Clients → [Client] |
| Ad copy | Slack card | #hilda-review |
| Blog post | .md | Google Drive → Content |
| Meeting prep | ClickUp comment | Relevant ClickUp task |
4
Common mistakes
- Not including the client name — Hilda can't find the Source of Truth without it
- Asking for multiple unrelated deliverables in one brief — split them up
- Triggering Hilda in a thread where there's no ClickUp task context — she'll miss the client history
- Forgetting to populate the Source of Truth first — every prep brief will carry a gap warning