New manager orientation
Ask for a department: Memtro returns headcount, the managers and their reports, so the new lead can learn the org before the first 1:1.
Who's who, who reports to whom, and who's out today.
Connect HiBob and Memtro knows your org: every person's role, department, site and manager, team sizes, who is on leave, and who joined or left recently. Read-only through a service user; only directory-level fields are requested and salary or personal data never are.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right HiBob tool, reads what it needs, and answers with the source cited.
Ask for a department: Memtro returns headcount, the managers and their reports, so the new lead can learn the org before the first 1:1.
Ask who is out during a release week: Memtro lists the people and leave dates so owners can be reassigned in time.
Questions people ask once HiBob is connected. In agent mode each one also checks the other systems that know about the same people, companies or identifiers.
Teams that get the most from HiBob in Memtro, with the rest of their stack attached.
A record in HiBob is rarely the whole story. Connect the systems that hold the rest and the agent cross-references them by default, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The HiBob tools are the same everywhere.
Set it up as an MCP server →Clients and agents →Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.