When staff should step in
List the situations that need staff attention: custom scope, uncertain knowledge, account-specific information, complaints or a visitor who simply asks for a person. Do not make the visitor prove that the assistant has failed before offering a contact route.
Send new projects to the inquiry route and existing clients to the right support contact. For urgent requests, show a contact method the business actually staffs. State its availability accurately.
Let the visitor review what travels
Give the visitor a chance to review the information being submitted. A short summary can identify the topic and outstanding question, while the original details remain available where appropriate. Do not silently turn an exploratory conversation into a sales request.
For a website project, the summary might include the current site, the problem and the selected service. If the assistant is unsure about something, carry that uncertainty forward. A confident but inaccurate summary can cause a worse handoff than no summary at all.
Say whether the request was sent
Explain the difference between preparing a request and sending it. The visitor should know whether they are reviewing a draft, completing a form or receiving confirmation that the system saved their inquiry. Give a reference when one is available.
If submission fails, keep the visitor's work on screen and explain another way to contact the team. Show success only after the receiving system confirms that the request was saved.
What the receiving person needs
A person opening the request should see why it was escalated, what the visitor asked and what remains unresolved. Assign an owner or place it in a queue with a defined claiming process. Merely emailing several people can leave everyone assuming someone else will act.
For AI-assisted replies, keep the draft editable and show the information it relied on. The staff member needs to check facts, tone and any commercial commitment before sending. Record the sending result so the team can distinguish a saved draft from a delivered response.
- Why did the assistant hand this over?
- What has the visitor already provided?
- What decision or response is needed now?
- Who owns it, and where is completion recorded?
Try the awkward conversations
Try a visitor who changes the subject, declines to share contact details or asks for something outside the service. Test an unavailable mail service and a failed record save. Confirm that the screen explains what happened and gives the visitor a way forward.
Review whether a person can continue the conversation without asking for the same details again. The person receiving the request should be able to understand the customer's need and continue from there.
