Process enquiry
Add a Holding Area enquiry to the database as a contact, with its note and optional buyer requirement.
MCP tool vaultre_write → process_enquiry
write Confirm
Does what Review and Create Enquiry does. Without contact_id, Vault's suggested match is used if there is one; set create_new_contact to true when the enquiry is a different person. Vault writes the enquiry as a note on the contact, and with create_buyer_requirement it links a requirement to the property asked about. Office automations in Vault can react to the new contact. By default you confirm each call; you can switch that off for this tool.
Parameters
| Name | Type | Description |
|---|---|---|
| enquiry_id string required | string | Enquiry ID from list_enquiries. |
| contact_id string | string | Add the enquiry to this existing contact. |
| create_new_contact boolean | boolean | Create a new contact even if Vault suggests a match. Default: false. |
| categories array | array | Contact categories to apply. |
| create_buyer_requirement boolean | boolean | Add a buyer requirement for the property asked about. Default: false. |
tools/call
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "vaultre_write",
"arguments": {
"operation": "process_enquiry",
"arguments": {
"enquiry_id": "enq_80412",
"contact_id": "51377",
"create_buyer_requirement": true
}
}
}
}Example response
{
"content": [
{
"type": "text",
"text": "{ ... same JSON as structuredContent ... }"
}
],
"structuredContent": {
"enquiry_id": "enq_80412",
"status": "processed",
"contact_id": "51377",
"contact_created": false,
"note_added": true,
"buyer_requirement_created": true
},
"isError": false
}