Sales agents now have names. Write the handoff before one books a meeting

For years, “AI for sales” meant a writing assistant inside the inbox. The seller still decided who to contact, what to say and when to hand a deal on. This month, Salesforce and HubSpot both included agents that prospect on their own in their launches.

That changes a question most revenue teams have never had to write down: where does the agent’s work stop, and where does a person’s begin?

What shipped

On September 11, Salesforce announced a set of named agents. Two of them are aimed at pipeline:

• Piper, generally available now, “works across websites and inboxes to engage, qualify, and convert inbound leads.”
• Hunter, in pilot with general availability planned for November, works a pipeline from research to outreach and collaborates with sellers over weeks.

Salesforce says Hunter built 60% of the sales pipeline at one customer, Perk. That is a company-reported figure about a single customer, and it measures pipeline created, not revenue closed.

A few days later, HubSpot’s Fall 2026 Spotlight described an updated prospecting agent that can monitor more than 40 buying signals, assemble a buying group and draft personalized outreach.

The vendors differ in the details. The direction is the same: finding and opening new deals is becoming a product you switch on.

Why the handoff is now the hard part

When a person books a meeting, everyone knows who to ask about it. When an agent books one, the seller who shows up may know less about the account than the software that brought it in. If nobody has decided what the agent passes along, the first call starts from zero, and the buyer notices.

There is also a forecasting problem. An agent that works around the clock can fill the top of the funnel with a lot of activity. Activity is not pipeline. If agent-sourced opportunities enter the CRM on the same terms as seller-sourced ones, your coverage ratio goes up while the quality underneath it is unknown.

Vantage Point’s review of both conferences puts the advice plainly: “Pick one workflow and baseline one number.” That is the right size for a first handoff.

A handoff contract, in eight lines

Before an inbound or outbound agent touches live pipeline, write one page that answers these. If a line is blank, the agent is not ready.

1. Lane. Which accounts, segments or inbound sources the agent may work, and which it must leave alone (named accounts, open deals, current customers).
2. Forbidden promises. What it must never say: pricing, discounts, delivery dates, contract terms, anything legal or security-related.
3. Qualification bar. The exact criteria a lead must meet before the agent may hand it on. Use the same words your sellers use.
4. The package. What travels with the handoff: why this account, which signal triggered contact, what was said, and what the buyer asked.
5. The receiver. A named person or queue, with a response time.
6. The way back. How a seller rejects a handoff, with a reason code, so the agent’s bar can be adjusted.
7. Pipeline status. Whether an agent-booked meeting counts as pipeline on booking, on acceptance by a seller, or only after a first call.
8. Source tag. A field that marks every opportunity as agent-sourced or human-sourced, and never gets overwritten.

Line 7 is the one teams skip. Decide it before launch, or your forecast will decide it for you.

A decision rule for the forecast

A simple rule keeps the number honest while you learn:

An agent-sourced opportunity enters forecast pipeline only after a seller has accepted it. Until the accepted rate and the conversion from accepted to qualified have been measured over a full quarter, report agent-sourced pipeline on its own line.

This is not a verdict on agents. It is the same thing you would do with a new lead source or a new hire: measure it separately until you know what it is worth.

What we would measure

Keep it to four numbers, tracked side by side for agent-sourced and human-sourced deals:

• Acceptance rate by sellers, with reason codes for rejections.
• Conversion from accepted meeting to qualified opportunity.
• Win rate and cycle length, once enough deals close.
• Complaints, unsubscribes and replies asking to stop, per hundred contacts.

The last one matters because an outbound agent sends on your domain. Its mistakes land on your sender reputation, not the vendor’s.

What to do this week

• Pick one agent use: inbound qualification or outbound research, not both.
• Write the eight-line contract and have one seller and one RevOps person sign off on it.
• Add the source tag field to opportunities before any agent writes to the CRM.
• Take a baseline of your current acceptance and conversion rates, so there is something to compare against.
• Put agent-sourced pipeline on its own line in the next forecast review, even if it is zero.

The agents will keep getting better, and the vendors will keep adding names. The handoff is yours to write, and it is easiest to write before the first meeting gets booked.