Who we serve

Local SMBs

The phone rings while you are mid-job and there is a walk-in waiting at the counter. Whoever you pick, the other one learns they come second, and whatever you did not get to lands on your evening.

The part of the week that runs on memory.

The walk-in at the counter watches you answer the phone.

Most of what rings is the same handful of questions, all day.

The slot was held, nobody came, nobody paid.

The book is in the app, the diary, and someone's head.

The quote went quiet, and so did the regular who came monthly.

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 and the Messages

While you are with the person in front of you, nobody is free to pick up. The system takes what you cannot get to, and each one lands on the screen at the counter with the reply already sent and the time they asked for written down.

  • Reply to the call that rings out during service, with the times still open.
  • Answer the message left in the socials overnight, without it waiting for opening.
  • Answer the questions that ring all day: opening hours, parking, prices, walk-ins.

Nothing that came in while you were on the floor is sitting there unseen when you finally look.

Lucent capability: Inbound Response

Knowing What the Call Is

Every inquiry gets asked the same few things before it reaches anyone, so the routine booking, the one that eats a long slot, the price question and the supplier stop landing in the same pile. Sorting runs on your rules, and it judges nobody.

  • Ask what they want done, when they can come, and whether they are new.
  • Split routine bookings from the long slot and the one that needs you.
  • Send the price question a price, send the supplier to the back room.

The counter is left with the bookings, and everything else has already gone where it belongs.

Lucent capability: Qualification and Routing

Running the Book

Right now the book is in the app, the paper diary, and somebody's head, which is where the double booking comes from. Booking runs against one book, and when someone calls in sick and the whole day has to move, the messages that move it go out without the person covering the floor writing them.

  • Confirm the booking, remind before it, take the deposit if you take one.
  • Offer the cancelled Saturday back to whoever wanted Saturday and missed out.
  • Move the day's bookings when someone calls in sick, and tell everyone.

The book shows what is actually happening, and the slot someone gave up does not sit empty while Saturday turns people away.

Lucent capability: Scheduling and Reminders

Following Up on the Quote and the Regular

Some work is already yours and is only waiting on one more contact. The quote gets contacted again, the number of times you approved. The regular you have not seen since spring gets one honest message, and only if you approved that message. Nothing is discounted, nothing is pushed.

  • Contact the quote that went quiet, the number of times you approved.
  • Send the regular you have not seen a single message, if you approved it.
  • Stop the moment they reply, book, or ask to be left alone.

Work you already earned stops going quiet without anyone noticing it went quiet.

Lucent capability: Follow-Through on Open and Repeat Work

The Admin After Closing Up

The admin behind the day happens when the day makes it happen, instead of at ten at night when someone finally remembers. Takings and bookings get pushed through once, so nobody types them in twice. Nothing gets ordered until you say yes.

  • Write the appointment back into the book without anyone typing it twice.
  • Push the day's takings and bookings through to the accounts, once.
  • Draft the stock order when the shelf runs down, and hold it for you.

The admin behind closing up stops waiting for someone to remember it.

Lucent capability: Internal Admin Execution

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.

Cover the phone and the messages that come in while you are on the floor and after you have closed up, so each one is on the screen at the counter with the reply already sent.

Run the book: times offered against what is actually free, the booking confirmed, the reminder out before it, and the slot someone gave up offered back to whoever could not get in.

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.

Find the constraint that is actually costing you

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 have a counter, a book, and a phone that rings at the worst possible moment.

Your book lives in the app, the paper diary and somebody's head, and the three do not agree.

You hold slots for people who do not turn up, and you pay for the day anyway.

Your evening ends with admin that should have finished when the doors closed.

You know who has stopped coming in, and you have never had time to do anything about it.

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 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.

Start with the phone and the book.

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.