Use case · People and onboarding
The answers a new hire would otherwise ask around for
Policies, who owns what, how things are done and why: Memtro learns them from documents, conversations and the systems you connect, and keeps personal matters personal.
The problem
- New starters spend their first month asking who to ask
- Policies live in a wiki nobody updates and a thread nobody can find
- Tribal knowledge leaves with the people who hold it
How Memtro helps
- Confluence, Notion, Drive and Slack are searchable from one place, with memory of what was decided and by whom
- Per-fact scope keeps organisation knowledge shared while anything about an individual stays with them
- Teams decide which connections a group can use, so a new hire sees only what their role needs
Example queries
- › How do I request a laptop, and who approves it?
- › Who owns the on-call rota, and where is the runbook?
- › What is our policy on expenses over £500?
Jobs to schedule
- schedule: Every Monday at 9, this week's new starters with their team, manager and first-week meetings
- schedule: First of the month, policies in Confluence not updated in a year
Say any of these in Chat and Memtro creates the job. See Jobs.