The property
Service address, site access, and the contact the team should follow up with.
Every call starts
with a different need.
Make the next step clear.
Repair inquiries, maintenance requests, and replacement projects need different questions. Bring the customer’s words and the useful details together for the person taking over.
Discuss your HVAC workflow Explore three common requestsOne front desk. Different next steps.
Start with what the customer needs.
Choose an inquiry to see what’s known, what’s missing, and who should review it.
At the front deskFictional inquiries
Choose a request
Different questions.
The right person next.
What the team receives
Repair inquiry
“Our upstairs AC is running, but it isn’t cooling the rooms. Can someone take a look?”
- Customer reports
- Upstairs rooms are not cooling
- Equipment
- Air conditioning · Model not provided
Still to collect
Service address, contact details, and when the issue started.
Proposed next step
Prepare a service request for the dispatcher.
The symptom is recorded as reported. A technician determines the cause.
Illustrative examples · No live requests or bookingsRepair inquiry selected
Useful before anyone heads out
Give the team
the details to prepare.
Choose the information your team actually uses. Keep missing details visible so they can be collected before the next step.
The equipment
System type and any model or service-history details the customer can provide.
The timing
When the issue began, preferred visit times, or a planned project window.
The team makes the call
Clear information.
Qualified judgment.
Organizing an inquiry is one part of the work. Your people decide what it needs and what you can commit to.
See the AI controlsKeep symptoms separate from diagnosis.
Record the customer’s description. Leave the cause and required work for a technician to assess.
Confirm the visit before promising it.
Service area, crew availability, and customer preferences need to line up before an appointment is agreed.
Prepare the estimate conversation.
Give the estimator the request and property context. Scope, equipment, and pricing need their review.
Pick one request your team knows well.
We’ll map the questions, the software it touches, and the handoff. Then test the routine path and the exceptions together.
Before you start
A few practical questions.
Can we start with maintenance inquiries only?
Yes. A repeatable request with clear questions and a defined team handoff is a useful starting point. We agree the scope, current tools, and review steps before building it out.
Does LBOS diagnose a fault or recommend equipment?
The examples here organize what the customer says and the details still needed. Diagnosis, equipment recommendations, and work requirements stay with a qualified person.
What about urgent or uncertain calls?
We define the requests that should go to a person, who receives them, and the fallback if they are unavailable. The workflow should not make an unsupported promise about safety, arrival time, or a repair.
Can it connect to our scheduling or customer software?
We review your existing setup and confirm the proposed connections, permissions, and fallback. Booking or changing an appointment is a separate action to agree and test; it is not part of these examples.
Built around your HVAC team
Which requests need
a better handoff?
Bring a real example. We’ll work through a useful first scope together.
Map your first workflow