Stop being the company’s FAQ page.
Let people ask about leave, expenses and payroll. They get the source1 with every answer. Then hand it the post for #people.
“How many leave days do I have?”, “who approves this expense?”, “where is the travel policy?”. The handbook exists, but it is spread across Drive, Notion and pinned Slack messages, so people DM you instead. Enhanciar answers from the current policy, flags the old copy, and writes the announcement, the policy page or the reply for you to approve.
Illustration. Names and content are made up.
Team leads approve expenses up to $1,000. Anything above that also needs a sign-off from Finance.
Later, in the web app: the follow-up she asked for.
Say it. See it done.
Two things people in your role hand it, in their own words, and what comes back. Each one waits in your Actions queue until you approve it.
The policy is written down. People DM you anyway.
The same ten questions, every week
Leave, expenses, laptops, payroll dates. Each one takes two minutes. Together they take your Fridays.
Policies change, old copies don’t
Last year’s travel policy is still the top result in Drive search.
Process knowledge is in one person’s head
Only Sam knows how vendor onboarding actually works, and Sam is on leave.
Questions you can ask
In plain English, in Slack, in the web app or from your phone. Every answer links to the policy doc, page or message it came from, so people can read the rule itself.
- “How many days of parental leave do we offer, and does it apply to contractors?”
- “Who approves expenses over $500?”
- “What are the steps to onboard a new vendor? Who signs the contract?”
- “When is payroll this month, given the public holiday?”
Things it does for HR & ops
Say what you need after the answer, or let it spot the next step. It drafts the work and waits in your Actions queue for you to approve.
Posts and pages go out only after you approve them. Gmail replies are saved as drafts: you read them, change what you like, and press send yourself.
Your Actions queue, on a Friday afternoon. Illustration.
The places the handbook actually lives.
Three steps, no code.
- Connect the drives and Notion spaces where policies live; mark private folders as HR-only.
- Point people to the bot in your #ask-hr channel, or to the web app.
- When a policy changes, it marks the old answer stale and re-checks it, so nobody quotes last year’s rule. Then hand it the follow-up: the #people post, the policy page or the reply waits in your Actions queue for you to approve.
Sales · Support · Founders · New hires · Engineering
Same brain, same sources, same Actions queue. Each role has its own page with the questions it asks and the jobs it hands over.
Want this for your people team?
Sign up, pick a plan and add your own AI key. Paid plans only.