The customer gets an answer
The assistant answers when you cannot, using the information and channels you have connected.
One customer wants a kitchen tap replaced. Another needs to speak to someone about an urgent enquiry. You choose what the assistant collects and how it hands over to staff.
A request for you to follow up
A saved request provides details for your callback. It does not mean a plumber is booked or on the way.
The assistant answers when you cannot, using the information and channels you have connected.
You receive what the customer wants done, where the job is and how to reach them.
You decide what the work needs, whether you can take it and when you can help.
Illustrative example. This is a suggested process, not a customer result or an actual booking.
For example, the customer says
We would like to replace the kitchen tap. Can you help, and what does it cost?
Use your own test requests before launch. Check both what the customer hears and what you receive after the call.
Use requests when you need to assess the job first. Connect a calendar only for visits you can book under clear rules.
Without a connected system that can confirm a time, the enquiry must remain a request.
A separate booking setup can use a connected calendar. Confirm a time only after checking it and saving the booking.
See how the calendar connection works and what it can check. A preferred date is not a booking on its own.
You choose how urgent calls are handed over. Test this with your staffing and contact route. The assistant must not promise someone is on the way.
This setup captures the request and leaves the assessment to staff. You decide which approved information the assistant may repeat during setup.
A saved request with the customer contact details and a work summary. Check the recipient and contents using your own test requests before launch.
We test a routine enquiry and a handoff using the rules you want for your business.