Draft in your chatbot.
Send from Acre Forms.
Connect Claude, ChatGPT, or another AI assistant over MCP. It drafts transactions, prefills forms, maps PDF fields, and preps packages for you — while sending and final review stay right inside Acre Forms, under your control.
How the handoff works
Your AI assistant handles prep work in natural language. The moment a document needs to reach a client or be sealed, you take over in Acre Forms.
Step 1
Chat to prep
Draft deals, import clients, prefill forms, map fields, and assemble document packages from a simple conversation.
Step 2
Review in Acre Forms
Every draft, mapping, and template lands in Acre Forms for you to review, adjust, and approve before anything goes out.
Step 3
Send & seal
You — not the AI — hit Send. Final review, client delivery, signatures, and the cryptographic seal all happen inside Acre Forms.
What your assistant can do
Read your workspace
Ask about open transactions, sent forms, upcoming closings, or client history. All read-only tools are RLS-scoped to your account.
Draft and update
Create clients from a paste of an email thread, import a CSV, spin up a new transaction, or attach documents — all through natural language.
AI-assisted form mapping
Drop a fillable PDF; your assistant helps map the AcroForm fields to Acre Forms roles. The template lands in Acre Forms for review before it's ever sent.
AI preps. You send and seal.
- • Draft, prefill, map, and prep in your chatbot. The AI can create clients, spin up transactions, fill forms, and stage document packages.
- • Send and final review stay in Acre Forms. A person confirms every mapping and hits Send inside the app — never over MCP.
- • Imported templates are pending review. A Broker/Owner approves suggested field labels before the template is usable.
- • Every action is audited. MCP entries appear in your Integrations page and the brokerage Audit Log tagged as AI-initiated.
Transparent by design
- • We use AI to suggest field labels when a new template is imported. Humans review and approve.
- • Client and transaction data is never used to train third-party models. Requests go through providers with no-training terms.
- • Signature capture, PDF hashing, and audit logging are not AI — they are cryptographic and deterministic.
- • You can disconnect any AI assistant at any time from Integrations.
Ready to connect your assistant?
Signed-in users get connection instructions plus a live activity feed on the Integrations page.