Process VaultRE Holding Area enquiries with AI

1. Go to Prospecting > Enquiries, or Contacts > Enquiry/Holding Area. Filter by Status (Awaiting review, Processed or Ignored), Department, Source, Agent or Property, then click Apply Filters.
2. Click Review beside an enquiry and fix the contact details, Categories, Marketing contacts and Access settings. Tick or untick Buyer Requirement.
3. If Vault finds a likely match by phone number or email address, it preselects that contact. Choose Create new contact only when the enquiry is a different person, then click Create Contact & Enquiry.
4. Enquiries cannot be added in bulk, so each one is processed on its own. Spam is cleared with Ignore Enquiry, and Vault deletes ignored enquiries permanently after 3 months.
5. Office Automation can switch the Holding Area off so every enquiry goes straight in. Vault leaves that off by default, because manual review filters spam and gives better duplicate checks.

Go through the VaultRE Holding Area enquiries awaiting review. Add real buyers to their existing contact or a new one with a buyer requirement, ignore spam, and leave anything unclear for me with a one-line reason.

1. 01

   Read the whole queue

   list_enquiries returns the enquiries with status awaiting_review, each with its source, message, the property asked about and the duplicate Vault suggests. The agent reads the full list first, so a person who enquired on two portals is one decision, not two.

2. 02

   Check the suggested match

   Where Vault suggests an existing contact, the agent confirms it with search_contacts on the email and mobile. A matching phone number with a different name is treated as a new person, the same call Vault asks you to make.

3. 03

   Sort into three piles

   Real buyers and tenants go to process, spam (an empty message, random text, only a link) goes to ignore, and anything unclear, such as an enquiry about a property no longer listed, stays in the queue with a note for you.

4. 04

   Process with the requirement

   process_enquiry adds each real enquiry to the matched contact, or creates a new one when the person is different. With create_buyer_requirement on, Vault links the requirement to the property they asked about. Each call waits for your OK until you switch confirmation off for it.

5. 05

   Ignore only after your OK

   ignore_enquiry runs for the spam pile only. Vault deletes ignored enquiries after 3 months and Cotlet has no tool to bring one back, so the agent lists each one with the reason before it is ignored.

Enquiries awaiting review: 9
Added 6 (4 to an existing contact, 2 new), buyer requirement set on 5
Ignored 1 (message was only a link)
Left for you 2:
- Tom Gallagher: asks about a property that is no longer listed
- Mei Chen: same mobile as a contact with another name

curl -X POST https://cotlet.dev/api/v1/vaultre/enquiries/enq_80412/process \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"contact_id":"51377","create_buyer_requirement":true}'

{
  "enquiry_id": "enq_80412",
  "status": "processed",
  "contact_id": "51377",
  "contact_created": false,
  "note_added": true,
  "buyer_requirement_created": true
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is vaultre_write → process_enquiry. Example data.

• Book VaultRE scheduled viewings with AI
• Add VaultRE appraisals from new owner leads
• VaultRE API and MCP server: every tool
• All use cases