Skip to content
Start with enquiries. Explore quotation drafts.

Quotation follow-up and enquiries

After-hours enquiries: a useful next-day handover

Staff should be able to continue an after-hours enquiry without making the customer start again. Record the question, stated contact preferences and missing information. Accurately distinguish received messages from handled requests.

Understand the task

An available chatbot is not a continuously staffed team. Its receipt must not invent a rapid response time. Choose a few qualification questions around what the recipient needs next working day. Separate quotation, booking and contact requests.

Prepare these inputs

  • Staffed contact periods and exceptions.
  • Minimum fields for the relevant task type.
  • Recipient, deputy and visible waiting status.

A practical workflow

  1. Answer approved practical questions and state staffing accurately.
  2. Clarify the requested next step without repeating questions already answered.
  3. Hand over the original message, short summary and open points. Staff confirm the actual next action.

Worked example, not a customer case

An illustrative example

Illustrative example: on Sunday a visitor asks about a service and requests Monday-afternoon contact. The answer can provide approved information and record the preference. It does not promise a call at a particular time unless the business has approved that service.

Test failures and exceptions

Suggested bounded tests using fictional information
Test inputExpected outcome
The following Monday is a closure day.Use the current exception in the receipt.
The staff member cannot receive the task.Show failure and manual fallback rather than handled status.

Evaluate whether it helps

Measure handovers containing necessary details and time to human takeover. Keep unknown outcomes unknown. An after-hours enquiry is not evidence of a customer, order or confirmed appointment.

Next step: Test Sunday, holiday closures and recipient absence before calling the contact journey ready.

Sources and scope

Examples are editorial exercises using fictional information. They do not describe completed customer tests or activated integrations. The authority source below provides AI and data background rather than approval of the exercise.

Want to clarify your own workflow?

Bring one task and a non-sensitive example. Scope, price and timing are agreed individually before work. Reading a guide activates no customer messages or system actions.

Describe your task

Read the related service guide →