Keep the request, the person handling it, and the next action together. A notification tells you a message arrived. A follow-up record tells you whether someone answered it.
Follow one request all the way through
Someone fills out your contact form. The message arrives in an inbox. Then what?
If a few people handle inquiries, each might assume someone else replied. If one person handles everything, a request can disappear beneath the next day’s email. The first useful improvement is a clear record of the request and what happens next.
Consider an example: a prospective tenant asks whether a space could work for a bakery. The form contains a name, email address, and a short note. The business needs to confirm which property they mean, understand their requirements, and arrange a conversation. Sending a form confirmation completes only the first step.
Keep the original request.
Name the person handling it.
Check the details and reply.
Record the next action.
The bakery inquiry is fictional. These four steps are a suggested process you can adapt.
Give the team one place to check
You can start with a shared spreadsheet or a tool your team already uses. What matters is that someone can open the record and answer a few ordinary questions without searching several inboxes.
- What came in?
- The original message, its source, and when it arrived.
- What does the person need?
- A short summary, contact details, and the relevant property, service, or project. Leave unknown information marked as missing.
- Who is handling it?
- One named person who owns the next step. A shared inbox by itself does not settle that.
- What happened last?
- The last response and when it was sent. Distinguish an automatic acknowledgment from a substantive reply.
- What happens next?
- A specific action, a sensible due date, and a status such as new, waiting on us, waiting on customer, or closed.
Keep a link to the source conversation. A summary can help someone get oriented, but they still need a way to check the wording and attachments.
See how we connected it for Parker & Associates
For Parker & Associates, Endcap connected website inquiries, leasing calls, and emails in one portal. The system organizes the person, property, and requirements, and tracks replies. The brokerage team reviews the details and handles the next conversation.
The useful part is the connection between those steps: the person following up can see the request and whether it still needs a response. The team does not have to treat the form, the phone call, and the email as unrelated pieces of work.
Watch the Parker inquiry workflow ↗
A similar setup starts with understanding where your requests arrive and how your team answers them. The right implementation depends on the tools, access, and review process you already have.
Plan for the awkward requests too
A process is easier to trust when you know what to do with the requests that do not fit neatly. These are useful situations to test before depending on an automation:
- The same person contacts you twice. Check whether the messages describe the same request before merging them. Two messages from one person may concern different jobs.
- A contact detail is missing. Flag the gap and use the available reply channel. Do not guess a phone number or fill in a requirement that was never stated.
- The notification fails. Make sure the original submission is still available somewhere and that someone can notice the delivery problem.
- Someone has already replied. Check what counts as a response and how the status changes, so the team does not chase a completed task.
- The inquiry needs judgment. Route it to a person who can handle the question rather than treating every request as a standard booking.
Adapt these tests to your team’s process and check how your system handles each one.
Use the follow-up checklist
Take it back to your team
One inquiry, from arrival to next action
Try this with a fictional request first. Then agree on the routine your team will use.
Endcap · endcap.design/learn/website-inquiry-follow-up/
The CSV has one blank record with the fields described above. Checklist entries are not saved when you leave or reload this page.
Decide what is worth connecting
If your team handles a few requests and the routine is working, a clearer checklist may be enough. When gathering details, assigning work, and checking for replies becomes repetitive, connecting the tools can help.
Start with one channel or one kind of inquiry. Check that the team can find the source, correct a mistake, and understand the status before expanding the workflow. Use the automation planning worksheet to compare the work involved, including review and running costs.
If requests are arriving in several places, talk with us about your inquiry process. The initial 30–45 minute consultation is free and includes a short follow-up with practical ideas. Further planning and implementation have an agreed scope and price.