Explain intake clearly
Help colleagues ask a better initial question.
Them AI for Legal
Explain the process without replacing legal judgment
Legal teams repeat useful guidance that should not require a fresh explanation every time. Share approved, organization-safe process knowledge with sources and owners, while keeping privileged material and case-specific judgment outside the shared workspace today.
Mac-only for now. Free during the beta (invite-only).
Legal operations roomShared room
You with your team
What should we prepare before asking legal?
Them AI with company contextPrepare the business purpose, document type, and decision needed. The intake guide uses those details to route the request; actual documents go through the designated legal intake system.
↗ Example intake guideReview with Legal operations
After human approvalGeneral intake guidance
A useful record for the next person.
Illustrative workflow. Not a live conversation.
The work gets better when the context stays.
Good judgment belongs
with the whole team.
Keep boundaries visible
Separate general guidance from matter-specific legal judgment.
Point to the owner
Make the authorized review path easier to find.
In the day-to-day
Work your team can bring to Them AI.
Start with the question. Keep the source. Make a person responsible for what comes next.
Legal room Example 01
What does legal need to understand the request?
Lead with the decision the business needs, then give the document category and purpose. The intake checklist helps legal route the request before collecting the actual matter details.
↗ Example intake checklistPrepared intake
Help colleagues understand what a useful legal request contains. Explain the business purpose, document category, and decision needed, then identify the approved intake path and owner before preparing the request.
See how the workflow fits
- Bring
- General intake checklist
- Review
- Legal operations
- Keep
- Preparation guidance
Legal room Example 02
How do we know which template fits?
Compare the intended purpose with the template's usage notes. If the request falls outside that description, bring the question to the template owner through the documented review path.
↗ Example template guidanceTemplate guidance
Make approved template guidance easier for colleagues to understand. Keep each document's intended purpose, responsible owner, and exception route together, so requesters know what to establish before asking legal for review.
See how the workflow fits
- Bring
- General template notes
- Review
- Template owner
- Keep
- Usage explanation
Legal room Example 03
When does a change need legal review?
Changes outside the approved guidance go to the legal owner. The review policy asks the requester to identify the proposed change and the business reason through the designated intake path.
↗ Example review policyReview boundaries
Help colleagues recognize where standard guidance ends. Explain the approved escalation criteria and the responsible reviewer, giving the business a clear next step when a request needs a lawyer's attention.
See how the workflow fits
- Bring
- General review policy
- Review
- Legal owner
- Keep
- Escalation guidance
Legal room Example 04
Who can clarify this policy requirement?
The policy names legal operations as the first contact for process questions. They can identify the responsible reviewer and the information required for a question about a particular situation.
↗ Example policy guidancePolicy navigation
Give colleagues a place to understand general policies that legal has approved for everyone. Keep the source and responsible owner together, making it easier to ask the right followup question.
See how the workflow fits
- Bring
- Organization-safe policy
- Review
- Policy owner
- Keep
- Cited explanation
These are example workflows to evaluate, not customer results. Connected agents use their own tools; Them AI is the shared context and review workspace.
From useful work to reusable knowledge
The conversation is
only the beginning.
Memory keeps the facts and decisions. Skills keep a way of working. People decide what deserves to become a shared reference.
Meet Rooms and the Collective- 01
Bring the context
Example intake guide
- 02
Make the human call
Legal operations reviews the sources and proposed record.
- 03
Keep the method
Intake preparation
Make it real
Start with the intake guide
Choose a general process legal is comfortable sharing with everyone in the workspace.
Discuss a design partnership
Before you begin
A few things
worth knowing.
Can Them AI make legal decisions?
No. These examples explain general processes. Qualified people remain responsible for advice, interpretation, approvals, and legal decisions.
Can we add confidential matters?
Not to this shared workspace. Human access is organization-wide today; privileged material and sensitive contracts belong elsewhere.
What is appropriate for the beta?
Mac-only for now. Free during the beta (invite-only). Use only general guidance approved for the whole organization.
What does the current beta include?
Shared rooms, memory with sources and review status, reusable skills, and MCP access for connected agents. Mac-only for now. Free during the beta (invite-only). Human room and memory access is organization-wide. Client-scoped MCP feeds restrict agent retrieval to that client's approved records plus approved firm-wide material. Do not treat a room as a private boundary for individual members. Read the access boundaries.
Bring one real workflow
Make the next project
better informed than the last.
Start with a question your team keeps answering. Bring the sources, the people who know, and the decisions worth keeping.
Mac-only for now. Free during the beta (invite-only).