How to Put an AI Sales Team on Your HubSpot Leads

To put an AI sales team on your HubSpot leads, save a static segment of the contacts nobody is working, export it, and import the file into AI Sales Console, the AI Sales Brain: six specialized AI agents directed by one learning Brain. By default, Sage researches the imported contacts first, and then Mia starts email outreach to the contacts you confirm you have a lawful basis to email. Calls are a separate matter, because Alex phones only contacts whose agreement to be called is on record, and an import does not add that record. A new account is live in 72 hours.

Which HubSpot contacts belong in the segment

HubSpot now calls lists segments, and you build one from the CRM menu under Segments. Pick a static segment for the handover to AI Sales Console: it captures the matching contacts at the moment you save it, so the file you import and the people being worked remain one fixed group. Filters worth stacking:

• Lifecycle stage of Subscriber or Lead, which keeps customers and contacts already tied to a deal out.
• Contact owner is unknown, or Last contacted is unknown or more than several months ago, so the handover skips people a rep is actively talking to.
• Currently in sequence is none of True, with empty values included, which leaves out anyone a rep has enrolled in a HubSpot sequence.
• Nobody marked Unsubscribed from all email.
• No associated deal that is still open.

Exporting the segment and importing the file

Hover over the segment, click More, choose Export, and tick the properties to include; HubSpot emails you the file. The columns that matter are First Name, Last Name, Email, Phone Number, Company Name, and Job Title. AI Sales Console accepts CSV and XLSX files, detects common column names like these, and shows each match for you to confirm. Leave internal fields such as Contact owner out of the export, since a column that reads like a name can be suggested for the wrong slot. Other columns it does not recognize are kept as custom data for personalization, and a contact whose email already exists in your workspace is not added twice. Before importing, you confirm that you have a lawful basis to email every contact in the file, and that confirmation is stored with each new lead the import creates. Import is the step that starts outreach, so the segment you saved is the decision you are signing off on, and contacts on your do-not-contact list or held for identity review are skipped until cleared.

What the six agents do with an imported segment

Inside AI Sales Console, the six agents are Sage on research, Alex on voice calls, Mia on email, Zara on SMS, Nova on analytics, and Jade on coaching. Single-agent AI SDRs automate one channel; the AI Sales Brain coordinates six agents across voice, email, and SMS with shared learning. It learns from every call and gets sharper every week. On an imported HubSpot segment, the file supplies names, titles, and companies, Sage adds what research turns up about each company, and Mia's first email waits until that research is in. Alex needs something a spreadsheet cannot supply, a recorded agreement to be called, so plan an imported segment as email-led.

Keeping HubSpot sequences and the agents apart

Once a static HubSpot segment is imported into AI Sales Console, keep it in HubSpot as the exclusion list for your own automation. Add it as a suppression segment on contact-based workflows that send email or enroll contacts in sequences, unenroll anyone who slipped into a sequence anyway (emails already sent stay sent), and add an is-not-member-of-segment filter to the active segments your reps prospect from. If you run HubSpot's Prospecting Agent, keep these contacts out of its plays too, and unenroll any that land in one. HubSpot will not stop a rep from enrolling one of these contacts in a sequence by hand, so tell the team the segment is off-limits. Work done on an imported file is logged in AI Sales Console, not on the HubSpot timeline, so agree before the import who updates Lifecycle stage and Lead status in HubSpot when a contact replies or books a meeting.

What handing over a segment costs

The Team plan runs $1,999 a month, includes the whole six-agent roster with no per-seat fees, and covers 250 leads worked a month. On a HubSpot segment imported into AI Sales Console, that work is Sage's research and Mia's email, it starts for every contact in the file at import, and leads past the monthly 250 are billed as extras, so size the segment to the month. The first 30 days run on your own pipeline, with no card, and the first paid month carries a 30-day money-back guarantee. A salaried SDR, the usual alternative, costs $11,200-12,800 a month fully loaded (on-target earnings of $80,000 or more per The Bridge Group 2025, plus U.S. Bureau of Labor Statistics employer-cost factors, tools, and management).

When the work should stay inside HubSpot

An imported HubSpot segment is worked inside AI Sales Console rather than HubSpot, so its emails and the replies they draw do not appear on the contact timeline your reps read. If your managers coach from that timeline, or your reporting depends on every touch being logged there automatically, keep that outreach in HubSpot's own sequences, which run from the same contact records. A team that wants AI writing those emails without leaving HubSpot can also look at HubSpot's Prospecting Agent, which researches accounts and generates personalized email outreach inside the CRM. Staying put also makes sense when your filters leave far fewer than 250 contacts and few new ones arrive, since a rep can work a short list alone. And no software wins a complex, high-trust close. Humans do that. The AI is for the repetitive top-of-funnel volume that dies waiting for someone to reach the bottom of the segment.

The bottom line

Handing HubSpot leads to agents comes down to the filters you save in one static segment, because that list decides who gets researched and emailed and who stays with your reps. For $1,999 a month and 250 leads worked, the contacts nobody had time for get Sage's research, and Mia emails the ones that clear identity and do-not-contact checks. What the agents do with each contact then shows up in the console your team logs into.