Project stories / Hearthwick · Demonstration project

Reply to customer requests

An after-hours request becomes a booked job with the details ready for the team.

Try the demo

What changes

Before

In this demonstration, a customer gets in touch after closing. The next morning, someone has to check what they need, where the job is, and when the team can visit.

With the workflow

The same workflow collects the missing details, checks available times and prepares a complete owner handoff.

See the complete workflow

Before

  1. A customer leaves a brief message after closing.
  2. The owner replays it, asks for missing information, and checks the calendar.
  3. Booking details are copied into a customer record and passed to the person doing the job.

With the solution

  1. Collect the customer, job and service details needed to check the request.
  2. Offer a time from the example calendar, or ask a person to handle an unavailable time or urgent issue.
  3. Confirm the simulated booking and prepare a customer record and job summary for the owner.
What this demo does

Working features

  • Try a complete request, missing details, an unavailable time or an urgent issue.
  • Follow each intake and booking step, inspect the records, and reset the example.
  • Adjust the booking and completed-job assumptions to compare monthly channel revenue.

What is simulated

  • Call transcript and customer conversation
  • Calendar availability and reservation
  • CRM creation and owner notification

The conversation is scripted. Appointments, customer records and notifications stay inside this demonstration.

No phone call, live language model, calendar booking, CRM write, or outbound message happens here. The model does not estimate acquisition costs, staffing costs, cancellations beyond its completion assumption, or overall company profit.

How the estimates work

Modeled additional channel gross revenue / month, before costs

$4,200in modeled additional channel gross revenue per month, before costs

At 100 inquiries, 20% versus 35% booking, 80% completion/payment, and $350 per completed job.

Channel gross revenue = qualified monthly inquiries × booking rate × completion/payment rate × average completed-job revenue. All four inputs are assumptions. The comparison changes the booking-rate assumption, not observed business performance.

These calculations use the stated assumptions. They are not client results, forecasts, or guarantees.

Try the demo
How a real project would be built and supported

Project stages

  1. Agree what the team needs to know, where it works and which requests need a person.
  2. Build the intake flow with a test calendar and customer records.
  3. Test normal and exceptional requests with the team before a staged launch.

Support

Support would cover requests that fail to reach the team, calendar or coverage changes, and inquiries needing a person. We would agree the responsibilities and changes with the business.

Discuss a similar projectBack to project stories