Enquiries
Where a form goes once somebody presses send.
An enquiry arrives twice: as a message to the people who answer it, and as a record that does not live in anybody's inbox. Both rather than either — a shared mailbox is where enquiries go to be forgotten, and a database nobody is notified about is worse.
What we need from you
- Who answers, and who answers when that person is away
One named person is enough to begin with. The second name is what stops enquiries sitting unread through a holiday.
- What you genuinely need to know before you can quote
The smallest set of questions that lets you reply usefully. Everything beyond that is a field somebody has to complete and you have to read.
- Where the record should live if you already keep one
If enquiries already go into a spreadsheet or a CRM, that is where they should keep going, rather than into a second place nobody checks.
What is true once it is in
- Every enquiry in one place, in the order it arrived
Including the ones that came in overnight and the ones somebody has already replied to.
- Nothing lost because somebody was on holiday
The record does not depend on one person's inbox, so covering for them is a matter of access rather than of forwarding.
- The job already described before you call back
The form asks what you said you need, so the first call starts from the details rather than from the beginning.
Fun fact
The web form is almost as old as the web page. Mosaic shipped one in 1993, and HTML 2.0 wrote the rules down in 1995 — the text box, the tick box, the drop-down and the submit button were all there, and they have barely changed shape since.
The other connections
Get in touch
Every one of these reaches us directly, and is answered by a person.
A new project, a quote, or a question about one that is running.
- Reaches us at
- +355 69 752 2209
- Carries
- Messages