Choose between an answer, a transfer and a callback
Start by separating information from decisions. Opening hours and other approved business information can stay with AI Reception when the answer is covered by its configured knowledge. Enabled NeroWeb and NeroBooking workflows can also support orders and bookings. That does not mean every exception or requested change can be completed without staff.
A transfer suits a caller who needs a discussion now and a team that is available to have it. A callback request suits a non-urgent enquiry when the right person is busy or absent. The trade-off is straightforward: a transfer offers immediate access if answered, while a callback avoids keeping someone waiting but creates follow-up work for your team.
Set boundaries around unresolved questions
Define the requests your team should handle: complaints needing a decision, exceptions to your usual terms, disputed order details, or questions not answered by your approved information. A caller should not have to repeat the same question indefinitely before reaching a person. Treat a clear request for human help as a reason to offer that route.
Write boundaries in practical language rather than relying on a vague instruction to transfer anything complicated. For example, distinguish explaining your published cancellation policy from deciding whether to make an exception. If a question remains unresolved after clarification, move towards a transfer or callback rather than another uncertain answer. Confirm how these expectations can be reflected in your configuration with the NeroPay team.
- List five routine requests the receptionist can answer from approved information.
- List five requests that need a named staff role or decision-maker.
- Identify questions where clarification is useful, but guessing is not.
Make the destination and fallback work together
AI Reception supports handover to a configured UK number or SIP destination. Choose a destination based on who can resolve the request, not simply which number is easiest to enter. A general reception line may suit varied enquiries; a responsible manager may be better for exceptions, but less available during busy periods. Do not assume automatic routing between several destinations is available.
Opening hours should inform your handover plan, but an open business does not always have someone free to answer. Agree what callers should be told when staff are unavailable and how callback requests will be handled. Confirm the behaviour for unanswered transfers with the team rather than assuming a failed transfer automatically becomes a callback. Avoid promising a response time your staff cannot support.
- Check that the configured destination is correct and staffed at the intended times.
- Decide who owns callback follow-up and what information they need.
- Test busy, unanswered and out-of-hours situations before relying on the arrangement.
Hypothetical example: a booking request becomes an exception
Imagine a small appointment-based business with an enabled NeroBooking workflow. A caller wants to make a routine booking, so the enquiry can follow the supported booking process. The caller then asks for an exception to the business’s cancellation policy on an existing appointment. That is a separate decision: explaining the configured policy is not the same as approving an exception.
If the responsible person is available, handover to the configured destination is the appropriate route. If not, offer a callback request without implying that the exception has been approved. The observable success check is whether the caller finishes knowing that their request still needs a decision and what the next step is. A request for help must not be mistaken for a confirmed change.
Test understanding, not just whether the phone rings
Run short test calls covering a routine question, an unresolved enquiry, a request for a person and an unavailable recipient. Check whether the answer stays within approved knowledge and whether the next step is clear. Optional recordings and transcripts can support review where enabled, subject to your settings and retention. Also review current call and usage limits when planning coverage.
Include payment-related enquiries in your boundaries. Card payments use secure checkout links; customers must not speak full card details to the AI. Transferring a call is not a reason to invite those details. Your next action is to write a one-page handover plan, then confirm the destination, supported configuration and unavailable-person behaviour with the NeroPay team.
GOOD TO KNOW
Common questions
Should every complaint go straight to a person?
Complaints needing judgement, investigation or an exception should reach staff. Approved factual information may help, but it should not replace human help when the issue remains unresolved.
What if nobody answers the transferred call?
Confirm the configured behaviour before launch. Agree a callback process and clear caller wording rather than assuming automatic recovery or repeated transfer attempts.
Can AI Reception transfer to our existing phone setup?
Handover supports a configured UK number or SIP destination. Ask the NeroPay team to confirm suitability for your setup and test the destination.
Does a callback request confirm a booking change?
No. A callback request asks your team to follow up. Keep it distinct from a confirmed booking, approved exception or completed transaction.