A Growing Business With No Support Team

Our client is a family-run manufacturer of an outdoor building product. It sells directly to homeowners, and distributors have started to take an interest too. By spring 2026, demand had grown faster than the business’s ability to answer it. Customer questions came in by email, through Facebook, and through website forms, and all of them landed with the same few family members who were also running sales, quoting, inventory, production, and shipping.

None of those conversations lived in one place. A customer got an answer only if someone noticed the message, found time to reply, and later remembered to follow up. Once volume picked up, that chain broke often enough to matter. Emails and Facebook messages went unanswered, quote requests sat longer than they should have, and a backlog built up across channels nobody had time to check.

The owners weren’t looking for a way to work longer hours. The brief was a system that could absorb more demand without forcing the family to pick between answering customers and having time outside the business.

Approach: An Agent Is Only as Useful as the Inbox Behind It

The client brought us in to implement HubSpot CRM and Marketing Hub, and HubSpot’s Customer Agent was part of the scope from the start. The agent drew most of the attention, but it could only work in channels HubSpot could see. An AI agent sitting on top of scattered inboxes would have answered questions in more places that nobody was watching.

So a large part of the work went into building the customer service setup the agent would depend on. We configured HubSpot’s Help Desk and a shared inbox, connected email and Facebook conversations to it, and set up website forms that fed the same view. Then we mapped how an inquiry should move once it arrived, from routing to follow-up to quoting, so that a quote request had a visible status rather than a home in someone’s sent folder.

The harder question was where the agent’s job should end. Our client had no interest in taking the family out of customer service. What they wanted was to stop personally answering every repetitive question, so the agent got the information it needed to handle those well, and conversations that needed a person were left for the family.

What We Built

HubSpot Help Desk now anchors the system. Email, Facebook conversations, and website form submissions arrive in a single shared inbox, conversation routing sends each one to the right person, and workflow automation creates the follow-up tasks the team used to track in their heads. Quote requests follow a defined process in HubSpot, so the family can see which are open and which have been answered.

Customer Agent works on top of that foundation, answering common customer questions and closing out conversations that don’t need a person. We also pointed it at the backlog. Conversations that had been sitting unanswered before launch went to the agent alongside new ones, which meant customers who had been waiting got a reply instead of being written off.

The engagement grew from there into expanded ongoing support. We worked through the client’s shipping and tracking processes, including an evaluation of their Pirate Ship workflow, and migrated their website onto HubSpot so forms and conversations run on the same platform as the CRM.

Results: 1,601 Conversations Resolved by Customer Agent

Over the four-month-plus reporting window in HubSpot, Customer Agent resolved more than half of the conversations it handled. Those conversations used to depend on someone in the family noticing a message, finding time to reply, and remembering to follow up. A separate resolutions-over-time report covering May through September records 1,550 AI resolutions, including weeks of 140 and 182.

Growth used to mean more manual work for the people running the company. With the agent covering a meaningful share of inbound questions while the family is packing orders, getting shipments out, or enjoying quality time, new demand no longer lands entirely on them, and the conversations that do need a person show up in one inbox where they can’t get lost. They kept up with demand without hiring a support team, using a system that lets their current team handle far more than it could before.

Before You Deploy Customer Agent on a Small Team

Four things from this project carry over to almost any small team:

• Consolidate your inboxes first: The agent only covers channels connected to HubSpot, so scattered inboxes mean it answers questions in places nobody is watching.
• Treat its knowledge like a product page: Its answers are only as good as the material you give it, so it deserves the same care.
• Set handoff rules before launch, then revisit them: Decide which conversations belong to a person, and adjust once real conversations start coming in.
• Include your backlog: The agent can work through old conversations as easily as new ones, so customers who have been waiting get a reply.

Running Customer Service With a Small Team?

This project shows what Customer Agent can do when the inbox, routing, and handoff rules underneath it are built first. If your team is answering the same questions across too many channels and losing track of the ones that matter, let’s talk about what that system could look like for your business.