Knowledge
It checks contracts against the knowledge base you attach. It cannot change any knowledge base.
AI contract review agent that checks each clause of a contract against your playbook and flags the ones that differ. Your playbook is the set of clause positions your company accepts, kept in a knowledge base you attach. The agent reads contracts from Google Drive, Google Docs, Notion or other connectors you add, or from a file you upload in Conversation, Slack, Microsoft Teams or Telegram.
Every contract needs a careful read against the same rules. That read takes time and depends on who does it. A contract review agent that works from your own playbook applies the same rules each time. It does the first pass of AI contract analysis, so a person starts with the flagged clauses.
Put your accepted clause positions in a knowledge base.
The agent checks contracts against that knowledge base.
Connect Google Drive, Google Docs or Notion, or upload the contract in Conversation, Slack, Microsoft Teams or Telegram.
The agent reads the contract against your playbook.
You get the clauses that differ from your playbook where you asked. Save the list to Google Docs or Notion if you want to keep it.
It checks contracts against the knowledge base you attach. It cannot change any knowledge base.
It reads contracts from the connectors you add. In Slack, Microsoft Teams and Telegram it replies when mentioned in a channel it is invited to or when messaged directly. It does not watch channels unprompted. It writes findings to Google Docs or Notion only when you ask.
Web access is off by default. The agent reaches your playbook, the connectors you add and the contracts you share.
Message text is kept for 30 days, encrypted, to measure answer quality. Keeping conversations longer is your choice.
AI contract review is an agent that checks a contract for clauses that need attention. The agent compares each clause with your playbook, which you keep in a knowledge base. It flags the risky ones so a person can look at them first.
It works from your own playbook in a knowledge base instead of fixed rules, so the flags follow the positions your company accepts. You create it on Commt from a template.
A contract playbook lists the clause positions your company accepts, such as the limits you will agree to. You store it as a knowledge base and the agent flags any clause that differs from it.
Yes. Store your rules as a playbook in a knowledge base and attach it to the agent. It compares each clause with the playbook and cannot change it, so your playbook stays as you wrote it.
Yes. Connect Google Drive, Google Docs or Notion to have it read contracts stored there, or upload a contract in Conversation, Slack, Microsoft Teams or Telegram. In a channel, invite the agent and mention it with the contract, or message it directly. It does not watch channels unprompted. It replies where you asked and can write its findings to Google Docs or Notion on request.
Fills in vendor security questionnaires from your policies.
Drafts answers to a request for proposal (RFP) from past proposals and product docs.
Create a contract review agent from this template, add your playbook, connect Google Drive and check your first contract.