Customer hub
Keep customer requests out of sticky notes, texts, and memory
Give every customer request one place to live. See who’s handling it, what the customer needs, and what’s due next without digging through texts and notes.
Justin CollierFounder, Arcadia Websites3 min readGive every open request a name, a clear next step, and someone to handle it. When a customer calls back, your team can pick up where the conversation left off.
You’re loading up after a yard cleanup when Morgan calls for an estimate. You write down the number and tell them you’ll check back tomorrow. A few hours later Morgan calls your office to add a detail about the job. The person who answers has no idea you already spoke.
A shared customer hub gives your team one place to look when Morgan calls back. Open Morgan’s request and you can see what they need, what you promised, and who’s doing the next thing. Morgan can add that detail without explaining the whole job again.
Give each request one home
Morgan wants a cleanup estimate. Save their name, a way to get back to them, and a sentence about the work. Put the callback on the same request with a name and a due date. Now the person in the office can say, “Sam has your request and will call you Tuesday morning,” because that’s what the team agreed to do.
If Morgan calls back about the cleanup, add the update to that request. If they ask about a separate job, give it its own record under the same customer. That makes it easy to see which promise belongs to which job.
Follow Morgan’s request.
Yard cleanup estimate
- Customer
- Morgan Lee · 205-555-0147
- Status
- New request
- Assigned to
- Sam
Morgan asked for a yard cleanup estimate. Use the number on the request to call back.
Call Tuesday morning to arrange a walkthrough.
Make the next step obvious
“Open” only tells you there’s work left. “Call Tuesday to arrange a walkthrough” tells you what to do. When Sam books the walkthrough, change the status to Visit booked and write down what comes next. After sending the estimate, put it under Estimate sent and set a date to check in.
Pick the steps you already use, then decide who moves a request along. If you work alone, the name stays yours. The due date is what keeps the callback from getting buried under everything else you did that day.
Start with the requests that slip through
The customer hub is included with the shared platform and care for Arcadia Websites’ AI and automation tools. I start by looking at the channel that causes you the most trouble. If that’s the website, a connected intake form can put the answers in the hub. If it’s calls you miss on a job, the AI receptionist can collect the details you’ve agreed on for a callback.
If a customer texts your personal phone or catches you in a driveway, add the request yourself. Give your team the same quick habit for anything that arrives outside the connected channels. We’ll run a few sample requests through the setup together and check that each lands with the right person.
Use the list to start your day
Look at what’s due before you head out. Sam can see Morgan’s callback alongside the walkthroughs and estimates already waiting. If someone is out, hand their requests to a named person so customers still hear back.
After a week, open a few requests and see whether you can tell what happened and what’s due next without calling a coworker or searching your phone. That’s the difference I want the hub to make.
Sources & a little context
These are practical setup recommendations. The scenarios are mockups, not recordings of customer calls or measured results. Features depend on your selected services and supported connections.
Shows how a request can keep its stage, owner, notes, and follow-up tasks together.
Explains how tasks can carry an assignee and a due date.
YOUR BUSINESS, YOUR SETUP
Set up your customer hub
I’ll recommend what to automate first, then handle the setup and ongoing care. I put the scope and price in writing up front.
See pricing for these tools Or ask me a question