Winning the deal is the easy part. Then delivery starts, and so does the chasing. The signed form that hasn't come back. The logo files you asked for twice. The project stuck in "Waiting on client" for three weeks while everyone assumes someone else sent the reminder.
Our Service agent exists to take that chasing off your team. It works the delivery and service pipelines in HubSpot the way our Sales agent works the sales pipeline: it watches, notices what's due, and drafts the next step for a person to approve. Here's what it does, and what it needs underneath it to do the job well.
The Service agent's patch starts the moment a deal is won. In a well set up HubSpot, that win creates or moves a record into a delivery pipeline, still associated to the same contact, company and deal. Depending on the business, that record might be a project, an onboarding ticket, or a record on HubSpot's Services object, which suits businesses that deliver ongoing services rather than one-off products. We explained how the Services and Listings objects shape this in giving agents the right shape of data.
The hand-off from sales matters. Because our Sales agent and the Service agent read the same records, nothing gets retyped. What was promised in the proposal, who the main contact is, and what the start date is all sit on the record the Service agent opens on day one.
Most onboarding is a checklist that someone has to remember to work through. The agent reads the checklist from the pipeline itself. Each stage has a written definition and a short list of what must happen there. For an illustrative onboarding pipeline:
Nothing on that list is clever. The value is that it happens every time, for every client, without depending on anyone's memory.
Delivery pipelines drift. A project sits in "In build" long after it's moved to review, because updating the stage is nobody's favourite job. That drift makes reporting useless and leaves the team guessing where things stand.
The Service agent checks each record against its stage's exit rule. If the review meeting has been logged and the client has signed off, it proposes moving the record to the next stage. If a record has been in one stage much longer than usual, it flags it to the owner with what it can see: the last activity, the last client reply, and what seems to be missing.
While the agent is new, a person approves each stage move. That keeps the pipeline honest without handing control of it to software on day one.
Chasing is where most delivery time quietly disappears. The agent drafts reminders that are specific, short and polite. Not "just following up", but "we still need your signed authority form and the two photos of the site. Here's the upload link." It spaces them sensibly, changes the wording each time, and stops the moment the item arrives.
When a chase has gone unanswered a set number of times, it doesn't keep emailing. It hands the job to a person with a suggested next step, such as a phone call. We went deeper on this pattern in the document-chasing agent, which shows how it works for professional services firms.
If clients have a portal, the same requests can appear there as a checklist, so they can see what's outstanding without waiting for an email. That's one reason we often pair the Service agent with a client portal.
At some point, a delivery question becomes a support question. The project is live and the client asks how to change a setting, or something isn't working. That's the Support agent's patch, not the Service agent's.
The hand-off works because of associations. The Service agent creates a ticket associated to the contact, the company and the project or service record. The Support agent opens that ticket and already knows what was delivered, when it went live, and what was promised. The client doesn't have to explain their history again, and nobody has to forward a long email thread.
This is the core reason we build agents on HubSpot. The pipelines, objects and associations give each agent a structured map, and hand-offs become a matter of passing a record, not re-explaining a situation. If you want the basics of that structure, our plain-English guide to pipelines, objects and associations covers it.
Like every agent on our team, the Service agent starts in draft mode. People approve, agents act. An agent earns more freedom once 95% of its work has been approved unchanged for two weeks, and even then it's task by task. Routine input reminders might go automatic, while anything touching scope, invoices or contract terms stays with a person.
That approval step only works if someone actually reviews the queue each day, which is why we build the approval queue before the agent. Then, each month, the agent gets a scorecard: what it did, what it saved, what it cost and the net return.
If your team spends more time chasing than delivering, let's look at your delivery pipeline together. Start with Build my solution and we'll map the first job for a Service agent, or book an AI Readiness Audit to check your HubSpot is ready for one.