A relocation firm where the owner was still the switchboard, screening every move by hand
Built an intake assistant that listens to incoming calls and emails, collects the basics of each move request, and proposes time slots, then holds everything for the owner to approve or decline before a single date or crew is committed. Nothing books itself.
Every move request still landed on one person. The owner answered the calls, read the emails, asked the same opening questions every time, what is moving, from where to where, how much, what date, and then weighed each one against the rest of the week: this client is urgent, that one is a complicated job with stairs and parking, this date is already heavy. Booking was a judgment call, and the judgment lived in the owner's head.
That was fine at one location. With a second branch opening and more crews to schedule, it stopped scaling. The owner could not keep being the switchboard for the whole company and also run the agendas for everyone else. The fear was the obvious fix: a system that just books appointments on its own, drops the wrong crew on the wrong day, and commits to jobs nobody vetted.
We built the assistant around a hard line the owner drew: it gathers and proposes, a person decides. Incoming calls and emails are captured and turned into a structured request, the same opening questions asked every time, the same fields filled in the same place, so two people reading it later see the same thing.
From the request the assistant proposes a few candidate time slots that fit the existing schedule, then stops. Each request sits in an approval queue with the details laid out: scope of the move, urgency, the constraints that make a job easy or hard. The owner approves, adjusts, or declines, and only then does the client get a confirmation. The triage judgment stays with the person who has it. The retyping, the repeated questions, and the back-and-forth come off their plate.
The owner stopped being the bottleneck for every inbound request. The repetitive part, taking down the same details and floating possible dates, runs on its own, and what reaches a human is a clean request ready for a yes or no. That freed roughly ten hours a week, the time that used to go to fielding and transcribing calls.
Because every request is captured the same way, the second branch could be brought on without the owner personally manning its phone. Staff see the same structured intake and the same queue, so a request can be handled by whoever is free, while the call on which job goes where still belongs to the person making it.
“I do not want a thing that books people in on its own. The deciding is the part I am good at. I want the asking and the typing taken off me so I can do the deciding.”
Have a mess like this?
Tell us where time and money are leaking. We’ll map the fastest high-ROI win, usually a Pilot that pays for itself.
