If I were handing an enquiry to a colleague, I would like the note to do a small amount of the work before the conversation begins.
Something like this:
A visitor asked about the assessment service after reading the page linked below. They described an unfinished project and would prefer an email reply. The page explains that the next step is a short suitability conversation. They have not been promised a confirmed appointment.
That is an invented example, but it contains the kind of context I want. The colleague can see what the customer asked, where they came from and what they expect next.
It is considerably better than “new website lead.”
A notification doesn't have to become a miniature dossier. It needs enough relevant information for the next person to respond sensibly.
The five details I would check
The request. Keep the customer's actual question recognisable. A form label should not replace the substance of what they described.
The offer. Name the service or product involved and keep a route back to the page. Several different advertisements can lead to the same inbox.
The expectation. What did the page say would happen next? A request for a conversation and a confirmed booking are different arrangements.
The reply route. Carry the preferred method if the process supports it. If somebody asked for an email, a surprising phone call may be an awkward start.
The timing. Include a relevant deadline or the stated response expectation when it affects the next action.
Some forms already collect these details. The handover can still lose them through an abbreviated notification or a route that strips out the page context.
That makes the exercise as much about the message as about the form.
Read the first reply
I like asking a receiving colleague to draft an answer to a representative request. The opening questions tell us what is missing.
If the first sentence asks which service the customer meant, perhaps the notification should already say. If it explains that a booking isn't confirmed, perhaps the invitation needs closer attention.
There will be details that properly remain a conversation. I don't want to turn the form into an interrogation merely to avoid every possible follow-up question.
I do want to avoid making the customer repeat information they have just given.
The process also needs an owner. A beautifully prepared request sitting in an unowned inbox is still sitting in an unowned inbox. Improving the handover note cannot conjure a colleague out of thin air.
Keep it readable
The useful note should be easy to scan on the devices the team actually uses. Label the details clearly. Keep internal campaign codes secondary to the ordinary description of the request.
I enjoy tidy campaign names more than is probably healthy. They do not tell a salesperson what the customer needs.
Test an agreed sample request and inspect what arrives. Follow the route into the working process. Check the actual reply arrangement rather than declaring success when a notification exists.
This is a small piece of maintenance with a rather practical consequence: the next conversation can begin further along.
And nobody has to spend the first two minutes asking, “Which bloody form was this from?”
A thought worth keeping?
