The phone rang while you were on a roof, and the job went to whoever picked up first. The week the phone does not stop is the same week nobody in the office can get to the estimate you sent Tuesday, or the invoice that went out before that.
The first cold snap hits, and the phone beats the office.
A cancel, a job running long, and the board is holes.
Nobody is home, the gate is locked, the truck leaves empty.
The estimate went out and nothing came back.
The invoice went out, and nobody in the office chased it.
What Lucent covers here
The work that has to happen anyway.
Lucent builds the same underlying capabilities for every operation it works with. What changes is the shape they take in yours. These are those capabilities, in the terms this business already uses for them.
Covering the Phone While You Work
Every call, web form, text, and lead-site inquiry becomes a job record when it comes in, and gets a reply with a next step. The call you could not take gets answered and turned into a booked visit, or a call back at a time you set.
Answer the call that came in while you were on a roof.
Answer the lead-site inquiry before the shop across town does.
Take the address, the problem, and the access details on first contact.
The job you are standing in stops costing you the next one.
Lucent capability: Inbound Response
Sorting the Emergency From the Quote
Every new call gets the same few questions, then gets sorted the way you would sort it: the emergency that has to move today, the job that can wait for a slot, the quote that can go on the estimate schedule. What it costs to come out is said before a truck rolls.
Ask the same questions every call: what, where, how urgent.
Say the price to come out before a truck rolls.
Send the emergency to dispatch, the quote to the estimate schedule.
Emergency work stops sitting behind quote work in the same inbox.
Lucent capability: Qualification and Routing
Running the Schedule Board
Service windows are offered against the drive time between jobs, confirmed, reminded, and rebooked when plans change. Before a truck leaves the yard, the job already carries the gate code, the lockbox, the dog, and who is letting you in.
Offer service windows that respect the drive time between jobs.
Confirm who is letting the truck in before it leaves the yard.
Put the cancelled slot back on the board so dispatch can refill it.
A cancel gets refilled instead of a truck sitting, and the board matches the day you are actually having.
Lucent capability: Scheduling and Reminders
Keeping the Office Off the Phone While the Trucks Run
When a job is marked on the way, or marked waiting on a part, the customer and the office both hear about it without anyone stopping to make a phone call. The job that is stuck says why: the part on order, the permit, the inspection, the second trip it is going to take.
Send the on-the-way note when the truck leaves the last job.
Tell the customer the part is on order without anyone calling.
Flag the job waiting on a permit or an inspection to close.
Nobody has to call the office to find out where the truck is or why the job is still open.
Lucent capability: Delivery Coordination
Following Up on Open Estimates and Work That Is Due
The estimate that went out and never got an answer gets followed up on a schedule you approve, and it stops the moment the customer replies. The same holds for the seasonal and recurring work that comes due again. No discounting, no pressure.
Follow up on the estimate that went out and never got answered.
Reach the customer whose tune-up is due before the first cold snap.
Stop the follow-up the moment the customer replies or books.
You know which estimates are still live and which are dead, without going through the folder.
Lucent capability: Follow-Through on Open and Repeat Work
The Office Work Behind the Job
The typing that happens after the truck leaves. The job closed out, the booking moved into your job software without anyone rekeying it, the invoice raised, and the unpaid one put back in front of the office instead of sitting in a folder.
Close the job out with the notes, the parts used, and the photos.
Send the invoice off the closed-out job ticket, before the truck reaches the next call.
Put the unpaid invoice back in front of the office, not the folder.
The office stops rekeying the same job twice, and the money you are owed stops sitting where nobody looks.
Lucent capability: Internal Admin Execution
Where Lucent would start
One system first, not all of them.
Nothing above gets built at once. A first build takes the one constraint that is costing the most and closes it, and the operation earns the next one.
The phone and the web form: the call you could not take becomes a job record with a reply already sent and a service window offered against the real board.
Then the open estimates and the unpaid invoices, put back in front of the office on a schedule you approve instead of into a folder nobody opens.
And the ones not shown
The capabilities above are the common starting points here, not the limit of what Lucent designs. They are assembled around how a business actually runs, so the ones that matter in yours may not be the ones on this page.
This is built for an operation that looks like this.
Fit is operational, not a size or a sector. If several of these are true this week, there is something here to build.
You run one truck, or a yard full of them, and the phone still rings to somebody who is also on a job.
Your estimates go out on time, and then nothing comes back.
Emergency work and quote work arrive on the same line, in the same inbox.
You already pay for job software, and nobody has time to keep it filled in.
The schedule board gets rebuilt by hand most mornings, and the busy weeks are the worst ones.
What these systems will not do
The line, drawn before you ask.
Every capability above has a limit, and the limits are the same wherever Lucent builds. They are worth reading before a conversation, not after one.
It opens the conversation. It does not close the sale.
The first reply is built from wording you approved, and it never presents itself as a person. It does not prospect, quote a final price, or give professional advice. It hands a live conversation to your team.
It sorts by your rules, not ours.
The questions and the priorities are yours. It does not score people, turn anyone away, or make an eligibility, credit, or health judgment. Anything the rules do not cover stops and goes to a person.
It works the calendar. It does not decide who comes first.
It books inside the availability rules you set and never moves or overbooks something a person has locked. Deciding who needs to be seen first stays with your team.
It reports the work. It does not do the work.
Everything it says outward comes from a status a person set. The judgment calls inside the job stay with the people doing the job.
It follows up. It does not chase.
It contacts people you already have a relationship with, a set number of times, and stops as soon as they reply. It is not bulk mail, it does not ask for public praise, and it does not discount, apply pressure, or invent a reason to make contact. Every contact is on the record.
It stops at the limit you set.
Approval authority stays with people. Anything above the threshold you define waits for a person: the system never approves on your behalf and never widens its own limits. It touches only the tools and fields you scope.
The systems underneath
How Lucent actually builds it.
The capabilities above are assembled into the systems Lucent already operates. A first build is usually one of these, scoped to a single workflow.
Start with the calls you cannot take and the estimates nobody answered.
The Operational Systems Audit looks at how the work actually moves through your operation, names the constraint that is costing the most, and specifies the system that closes it. It is a paid engagement, and the findings are yours whether or not a build follows.