An order records what the customer wants supplied
Choose an order when the request is specific enough to describe the service or items, quantity where relevant, agreed price and fulfilment arrangements. A customer ordering a standard repair package has made a different request from someone asking whether an unusual fault can be repaired. The second conversation may need assessment before an order is accepted.
An order gives staff a clear scope to work from, but it does not necessarily reserve technician time. If the work also needs an appointment, record that separately and reference the order. Keep a received request distinct from an accepted order, and tell the customer which stage applies.
- Check the scope, price and fulfilment details before marking work as accepted.
- Record unresolved questions rather than filling gaps with assumptions.
A booking reserves time, not every detail of the job
Choose a booking when the central commitment is an agreed date, time and service. Confirm the duration, location and any preparation the customer needs to complete. A request for Tuesday morning is not a confirmed appointment until the business has checked availability and communicated acceptance.
Booking early helps allocate capacity, but it can give false certainty when the job is still unclear. An assessment appointment may be appropriate even when the final repair cannot yet be priced. Make the limited commitment explicit: the customer has booked an assessment, not approval for unspecified work.
- Separate requested, provisional and confirmed appointments in your working process.
- State whether the slot covers assessment, delivery of the service or collection.
A callback keeps uncertainty visible
Choose a callback when someone must clarify suitability, price, access or timing before the business can commit. Record the customer's question, contact details, preferred contact time and the person responsible. A callback should describe the decision needed, not simply say that somebody called.
The trade-off is that callbacks protect against premature promises but can leave customers waiting. Give each one an owner and a realistic follow-up time. Tell the customer that no appointment or work has yet been confirmed. Once the question is resolved, update the record and create the appropriate order or booking without leaving two apparently active requests.
- Capture the specific question that prevents acceptance.
- Assign the next contact and record its outcome.
Hypothetical example: an uncertain repair request
A customer contacts a bicycle repair business asking for a full service on Friday and mentions a damaged wheel. The standard service is clear, but the wheel problem could change the work required and its duration. Recording a confirmed full repair immediately would promise more than the business has assessed.
The receptionist creates a callback for a mechanic to clarify the damage. After speaking to the customer, the mechanic agrees an assessment appointment for Friday. The booking confirmation explains that repair scope and price remain subject to assessment. If the customer later accepts the proposed work, the business records the agreed order and references the appointment.
The success check is observable: another staff member can identify what is confirmed, what remains undecided and who acts next without asking the original receptionist. The customer should give the same account when asked what Friday's appointment covers.
Choose software around the handover you need
NeroPay offers NeroPOS/ePOS software, NeroWeb online ordering and websites, and NeroBooking booking software. NeroWeb supports direct online ordering. When reviewing options, ask how your chosen setup distinguishes a submitted request from accepted work. Confirm product availability, supported devices and integrations with the team; do not assume records move automatically between products.
Where a connection has not been confirmed, plan a manual handover with a shared reference, named owner and clear status. Track payment separately: a payment entry alone should not tell staff that capacity or scope has been agreed. With an eligible NeroPay card terminal, NeroPOS, NeroWeb and NeroBooking software can be included without an additional software subscription charge. Terminal costs, payment processing charges, eligibility and applicable terms still apply.
- Test one enquiry from first contact through acceptance and completion.
- Check that the receiving colleague can find the reference and identify the next action.
GOOD TO KNOW
Common questions
Can one customer request need both an order and a booking?
Yes. The order can describe the agreed work while the booking reserves time to carry it out. Reference them clearly and avoid treating them as two separate jobs.
Does taking payment mean an appointment is confirmed?
Do not rely on payment status alone. Check availability and communicate the appointment status explicitly, including anything still awaiting agreement.
What should happen after an unanswered callback?
Record the attempt, keep an owner assigned and set the next action according to your contact process. Do not turn an unanswered enquiry into accepted work.