Your email assistant with a memory that doesn't quietly drift. Teach it once, it stays taught — every rule stays visible, editable, and always a human's call.
Invite-only — ask your ZRM admin if you don't have access yet.
Google OAuth, domain-restricted to zrm.dk. A quick scan of a few past sent emails suggests your signature, reply style, and tone as a starting point in Setup — you review it before anything saves.
Approve, edit, or ask for a rewrite. Anything worth remembering gets promoted into your Playbook with one click.
Every future draft reads from the same Playbook — org-wide rules, your own preferences, all visible and editable anytime.
Scroll to watch a real inbound email travel through Playbook, step by step — from Gmail, to a drafted reply, to what actually gets stored.
Mikkel from Nordic Retail asks Fran to confirm the contract value and resend an invoice — real billing details. Playbook reads it the moment it arrives.
Using your organisation's rules, guidance, and knowledge — the ones set up under Organisation setup — a reply is drafted automatically.
Untouched, exactly as drafted — sitting in your Gmail Drafts folder, ready to send, whether or not you ever open Playbook.
A deterministic filter strips signatures and boilerplate from the copy that reaches Playbook's own database — the Gmail draft above is never touched.
A sensitivity check flags — never rewrites — anything that looks like it could be an issue, for later human review. Nothing is guessed at or removed.
Whatever Playbook stores is encrypted, not plain text sitting in a database.
The original message and every draft version, side by side — edit it, ask for a rewrite, or just read it. Nothing is hidden from you.
The draft is already sitting in Gmail either way — leave it as-is and send it yourself whenever you want, or approve it in Playbook first to mark it reviewed. Sending itself always happens in Gmail, by you.
Change your mind as many times as it takes — join your ZRM colleagues already drafting with a memory that sticks.
Invite-only — ask your ZRM admin if you don't have access yet.
Nothing about how it drafts lives only in a model's head — it's all inspectable, editable, and gated by a human before it sticks.
Facts and preferences live as structured rows, deterministically injected into every draft. Nothing to forget, because nothing is left to the model's own memory.
Describe the change you want and get it regenerated, or edit the draft's text yourself directly — either way the previous version stays visible, nothing is silently overwritten. Approve it right from Playbook once it's ready to send.
Good feedback can be explicitly promoted into a durable rule. Nothing is learned silently in the background — you always confirm or edit first.
Admins set rules organisation-wide, scope them to a specific role, or leave room for personal preference — a Developer and a Project Manager don't have to share the same defaults, and every new teammate starts consistent with what's already established, not from a blank slate.