What it does
Puts a front door on the legal team. Requests arrive as Slack messages, half of them missing the one detail that decides everything — which entity, which counterparty, when it has to be signed. This reads the request, works out what kind of legal work it actually is, asks for exactly the missing pieces, and files a ticket the legal team can start on rather than one they have to chase. The categorisation matters because the queue does. A standard NDA against an approved template is not the same work as a data-processing agreement, a regulator's letter, or a dispute — and mixing them means the routine ones sit behind the complex ones while everyone waits. Some things it will not triage. Anything that reads like a legal threat, a regulatory notice, a breach, a subpoena, or an employment dispute goes to a named human immediately, with the request untouched and no attempt at categorisation. Those have clocks running, and the cost of a delay is not symmetric. It never gives legal advice, never says whether something is permitted, and never tells anyone a contract looks fine.
Example prompts
- Someone asked for an NDA in #ask-legal — what's missing before it can be filed?
- Categorise this request and tell me which playbook category it falls under.
- File the ticket for this request now that we have the counterparty and the entity.
Before you connect
The credentials this agent will ask you for — the full setup is on the Setup tab.
Needs 2 credentials (2 required) to connect. See setup
