Inquiries land all day from the portals, the sign, and the listing page, and you are standing in someone's kitchen with a lockbox in your hand and your phone face down. By the time you call back, the duplicates and the names that were never real have eaten the morning, and the ones that were real are out looking at someone else's listing on Saturday.
Portal inquiries sit unanswered while you are standing in a property.
You pay twice for portal leads already sitting in your database.
Your March buyer bought in September, and the sold sign told you.
The seller wants a call every Friday and the listing is stale.
Under contract, a date passes and nobody had it written down.
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.
Answering the Inquiries That Land While You Are Out
Every inquiry becomes a record when it lands, from a portal, the listing page, a sign call, or an open house sign-in sheet, and gets a reply with a clear next step. New inquiries are checked against the pipeline first, so a name you already own and are now paying for again is flagged before anyone works it.
Log every portal inquiry against the property it asked about, on arrival.
Reply with a next step while you are inside a property showing it.
Check each new inquiry against the pipeline and past clients before anyone works it.
Every inquiry gets a record and a reply, including the ones that land while you are out.
Lucent capability: Inbound Response
Sorting Inquiries and Respecting the Rotation
Each inquiry is asked the same few questions, starting with the one that gates everything: are they already working with someone. It sorts on the rules you set, and who owns the lead is one of those rules. It answers about the property and nothing else. Anything about the neighborhood, the schools, or who lives on the street goes to a person.
Ask every inquiry whether they are already working with someone, and which property.
Route buyer inquiries by your rotation, property questions to whoever holds that listing.
Separate a seller asking what their home is worth from a buyer asking about a listing.
Whoever is up gets a sorted inquiry with the answers attached, and nobody in the office argues about who it belonged to.
Lucent capability: Qualification and Routing
Getting Showings Booked, Confirmed, and Access Sorted
Booking a showing is not just the calendar. It is the lockbox code, the seller who wants notice, and the occupant who has to be told before anyone opens the door, and that gets handled with the booking rather than discovered on the doorstep.
Offer showing times against the real calendar of whoever covers that property.
Confirm access before the showing: lockbox code, notice to the seller or occupant.
Offer a cancelled showing time to the other inquiries on that property.
Showings get booked and confirmed, with access sorted, without anyone chasing the calendar by phone.
Lucent capability: Scheduling and Reminders
Keeping Sellers Told and Deals on Their Dates
Once a property is under contract the dates start running: the inspection, the appraisal, the loan approval, the contingency nobody wrote down. Each one that lands, or fails to land, is recorded and the update goes out from it. It reports what came back. It does not decide whether an appraisal or a loan is acceptable.
Chase feedback from whoever showed the property and pass it to the seller.
Record the inspection, the appraisal, and the loan approval as each comes back.
Pull traffic and feedback into the seller call on a listing that is not moving.
Sellers stop calling to ask what is happening, and no date runs out with nobody watching it.
Lucent capability: Delivery Coordination
Working the Database That Is Not Ready Yet
Most of your pipeline is not moving this month. A buyer waiting out a lease, a seller waiting for spring, a past client sitting in a house they will eventually outgrow. Each holds a next contact date and a real reason to hear from you when it arrives.
Hold a next contact date on a buyer waiting out a lease.
Contact the seller who said spring, when spring comes, with a reason to talk.
Check back in with past clients and referrals long after the closing.
Nobody in your database goes quiet just because their timing was not this month.
Lucent capability: Follow-Through on Open and Repeat Work
Seeing the Pipeline Without Asking Anyone
Open inquiries, the showings booked this week, the listings with nothing on them, the offers still waiting on an answer, and the dates running on everything under contract, in one place. What has stalled is shown rather than buried.
Show every open inquiry and every showing booked this week.
Surface listings with no showing on them and no contact made.
Flag every offer waiting on an answer and every deadline coming up.
You can see where every listing and every deal actually stands without asking anyone.
Lucent capability: Operational Visibility
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.
Every portal and listing-page inquiry answered on arrival, checked against your database for duplicates, asked whether they are already working with someone, and handed to whoever is up in the rotation.
Showings offered and confirmed against the real calendar with access sorted at the same time, and a next contact date held on every buyer who saw a property and booked nothing after it.
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 take more inquiries than anyone can call back on the day they land.
You pay for portal leads and cannot tell the real ones from the noise.
Most of your database is not buying or selling this month.
Booking a showing means sorting access, not just finding a time.
You are the one your seller calls when a deal under contract goes quiet.
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 reports what happened. It does not predict.
It shows what the systems actually recorded, and surfaces what has stalled. It does not replace your CRM or job software, it does not forecast, and it publishes no number that was not measured. Deciding what to do about a stall stays yours.
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 inquiries that landed while you were out.
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.