Illustrative workflow, not a customer case study. An earlier version of this page presented a named customer story, quotations and performance figures that we cannot substantiate. Those claims have been removed. The scenario below is hypothetical and reports no customer results.
The situation
Imagine a landscaping team receiving enquiries while working on site. A caller wants to discuss garden maintenance, but the team needs to assess the job before agreeing a price or visit.
An enquiry-handling checklist
- Ask which service the caller needs and whether the property is within the team's service area.
- Capture only the contact and job details needed for a follow-up.
- Keep an enquiry separate from an accepted quote or confirmed appointment.
- Pass unusual requests and questions about machinery or hazardous work to a qualified member of the team.
- Explain the next step without promising a response time or availability that has not been agreed.
Before automating the workflow
Review the actual services, escalation rules and data-handling requirements. If calendar booking is part of the proposed setup, test availability and verify the external appointment record. Also test what happens when that system is unavailable. These are evaluation steps, not claims that a particular product or integration has passed them.
Measure the outcome honestly
Compare enquiry records with confirmed appointments over matched periods. Keep requested visits, accepted work and paid invoices separate. Do not count every unanswered call as lost revenue or attribute a sale to automation without supporting records.
For current VoiceFleet plans, see pricing. No savings, implementation time or business result is promised by this illustration.
