Keep addresses separate
A customer’s office address may be used for invoicing while the work happens elsewhere. Label each address by its purpose and keep that purpose visible in the staff handoff.
Clarify repeat service requests
Every two weeks and twice each calendar month describe different service requests. Collect the pattern, preferred start and end rule so staff can review the request before confirming dates.
Separate form request roles
The person who submits a form may be arranging work for someone else. Separate the sender, the subject of the request and the reply contact before staff choose the next step.
Collect usable form links
A well-formed URL can still point to the wrong page or require a login. Collect the link and its purpose so staff can check relevance and access before starting work.
Resolve form conflicts
A selected field and a written message can disagree. Preserve both statements, clarify unresolved differences and check the affected draft before staff act on the resolved answer.
Make optional answers clear
An empty optional field does not explain why it is empty. Give staff a clear way to distinguish unanswered, unknown and not applicable before asking for more detail.
Keep every form request visible
A customer can ask for a quote, a delivery change and a document in one message. Keep every ask visible without turning one submission into duplicate work.
Give deadlines a time zone
A deadline of Friday at 5 can mean different moments to the visitor and staff. Collect the date, time and zone together, then confirm the meaning before committing.
Identify the right product
A WordPress parts inquiry can describe several products. Ask for a model, SKU, or part reference staff can check, preserve it exactly, and give unknown answers a review path.