Published: 7 October 2026
After-hours enquiries: what to capture and when to involve a person
Build useful after-hours handoffs for accounting, legal and cleaning enquiries. See example messages, booking confirmation rules and unavailable-staff fallbacks.
By Matthew WalkerFounder, Valory AI
A useful after-hours message lets someone pick up the enquiry without asking the caller to start again. It explains what they wanted, what happened during the call and who needs to act next.
That record matters whether a person or an AI receptionist answers. A caller can request a time, ask for a particular staff member or describe something as urgent. Each needs a clear outcome and an owner.
This guide gives you a handoff format to adapt with your team. For coverage options and rollout steps, see the general after-hours call-handling guide.
Decide who picks up each enquiry
Start with the person or team responsible for the next action. An email destination is only useful if someone checks it and knows which requests they own.
For every call type, agree a primary owner and a fallback when that person is away. Also decide what the caller can be told about timing. A preferred callback window should be recorded as a preference unless the team has agreed to meet it.
| Caller needs | Capture | Next owner | What can be confirmed |
|---|---|---|---|
| A named accountant | Requested person, brief reason and callback details | Named staff member or agreed intake fallback | A message recorded or transfer connected, when verified |
| A legal consultation | General matter type, contact details and any caller-stated deadline | Firm's intake team | Consultation booked only after the approved booking succeeds |
| A cleaning quote | Clean type, suburb, approximate site size and preferred date | Quoting team | Quote request recorded; price and job date await review |
| Help with an uncertain booking | Appointment type, requested time and the result received | Booking support owner | Confirmed booking details, or an explicit pending request |
Keep questions proportionate. Gather enough to route the enquiry and prepare a useful callback. Sensitive documents and detailed case histories can follow through the business's approved process.
A handoff record you can copy
Use the same fields across your workflow, with a few questions specific to the service. Put the action and owner near the top so a busy team member can scan it.
The record below is fictional, showing a cleaning quote request. Contact details are placeholders.
Next action: Review quote request and contact the caller.
Owner: Quoting team; duty manager is the agreed backup.
Call received: [Date, time and local time zone]
Caller and callback: [Caller name], [callback number checked with the caller]
Request: One-off office clean in [suburb], approximately [site size].
Preferred timing: Caller would like the clean on [date]; availability not yet checked.
Completed: Enquiry saved; notification sent to the quoting team.
Still needed: Confirm scope, decide whether a site visit is needed and prepare a quote.
Caller expectation: Team will review the request. No callback time, price or job booking promised.
Only mark a notification as sent when the sending step succeeds. If sending fails, record that status and use the agreed fallback. The enquiry still needs an owner.
A short summary should distinguish completed actions from requests awaiting review. “Appointment requested for Tuesday” and “appointment confirmed for Tuesday” lead staff to do different things.
When the usual next step is unavailable
The requested person cannot answer
Use the approved directory to identify the person. If the name is unclear, ask a brief clarifying question or route the enquiry to the agreed intake team.
Where transfers are configured, record whether the caller actually connected. If nobody answers, capture the callback request and use the fallback recipient. The caller should hear the next step that the team can support, such as: “I can take a message for the team and include when you'd prefer a callback.”
The calendar fails or gives an uncertain result
Keep the requested appointment type, date and time with the handoff. State whether the booking failed or whether its outcome could not be confirmed. Those are different situations for the person checking it.
The caller can be told: “I couldn't confirm that appointment. I've recorded your preferred time for the team to check.” Use that wording only after the request has been saved.
If the result is uncertain, staff should check the connected calendar before trying again. This helps avoid a second appointment being created for the same request. Until there is a confirmed result, the handoff remains open.
Three examples to work through with your team
These are fictional scenarios for planning and testing, not customer call records.
An existing client asks for their accountant
The caller wants to discuss a bookkeeping question with a named staff member after the office has closed. Capture the requested person, a short description and callback details. Use the approved staff route, with the intake team as the agreed fallback.
The next action is for the relevant person to review and respond. Keep any tax or accounting advice with the qualified staff member. The accounting service page explains the broader workflow.
A caller wants a legal consultation about a deadline
The caller says documents are due tomorrow and asks to speak with a lawyer. Record the date or time they state, the general matter type and the contact details needed for follow-up.
Use a staffed escalation route if the firm has agreed one. Otherwise, explain when the intake team is available and that the request is awaiting review. The handoff should label the deadline as caller-stated. A lawyer determines the advice, the actual deadline and whether the firm can take the matter. See call handling for law firms.
A customer wants to change a cleaning booking
The caller asks to move tomorrow's office clean to Friday. Capture the existing booking reference where available, the requested change and callback details for the scheduling team.
If the workflow cannot confirm the change in the connected system, keep it as a rescheduling request. Do not tell the caller the original booking has moved. Staff need to check availability and any crew arrangements before confirming the new time. The cleaning-business workflow shows how enquiry capture fits the team's follow-up process.
What a real implementation can show you
The published MGI South Queensland case study covers named-staff routing, Outlook booking workflows and structured staff notifications. Those are concrete examples of the connections a handoff needs.
Use that example to plan your own recipients, calendar checks and fallbacks. The accounting call-handling walkthrough goes further into staff lookup, booking fallbacks and ongoing refinement. Your firm's coverage and follow-up rules need their own agreement.
FAQ
Does every after-hours enquiry need an immediate callback?
No. Agree which requests can wait for the next staffed period and which have a genuine on-call recipient. Explain the available response clearly. Recording urgency alone does not create an after-hours service.
Can an AI receptionist confirm a booking?
Yes, where the appointment type and calendar connection are configured and the booking succeeds. A preferred time or an attempted booking should remain a request until confirmation is received.
How do we check whether the handoff is working?
Review a small sample with the people receiving the messages. Check the recipient, completed action, remaining task and caller expectation. Include an unavailable person and an uncertain booking in your test scenarios, then check that staff can follow each request through to completion.
Work through your handoffs
Bring three common call types and the person who handles follow-up. We can map the useful questions, next owner and fallback together.