Instance · Locator
Enquiries Introduction
Last updated 1 November 2026
Messages visitors send about a location, stored with it and assigned to your team.
An enquiry is a message a visitor sends about one location, for example a question to a clinic from its page on your site. Enquiries are stored in the Locator, linked to the location, so your team can answer them, assign them and track their status.
Where to find enquiries
In the admin, open Locator and choose Enquiries. You can open an enquiry, assign it to an administrator, and import or export enquiries as CSV.
What an enquiry holds
| Field | Meaning |
|---|---|
| Location | The location the enquiry is about. Required |
| Name | First and last name |
| Email and phone | How to reply, with the phone country code |
| Message | What the visitor wrote |
| Status | Where the enquiry is up to |
| Assigned to | The administrator handling it |
How enquiries arrive
Your website sends them. A developer adds a form to the location's page that creates an enquiry through the Locator API:
POST /locator/api/v2/enquiries
{
"location.uuid": "LOCATION_UUID",
"first_name": "Sam",
"email": "[email protected]",
"message": "Are you open on public holidays?"
}The API strips a leading + from the phone country code. Send the raw instance API key in the Authorization header; never put the key in browser code.
Note
The docs instance has no enquiries, so none was read. The fields come from the Locator module reference in the Insites Logic Engine.
Common mistakes
- Calling the API from the browser with the instance key. Send the form to your own page, which calls the API on the server.
- Leaving out the location. It is required.
- Not assigning enquiries. Assign each one, so someone owns the reply.