AI agents for GTM and RevOps · Part 9 of 13

Lead routing and CRM updates

Who owns a contact before the AI SDR’s first message, which CRM fields the agent may change, and what the rep receives when a prospect replies with interest.

Aakash William
· 5 min read

The short version

Decide who owns each contact before the AI SDR writes to it, with rules in a fixed order: the owner it already has, a customer’s account manager, the territory, then a rotation. Choose whose inbox it sends from, since the reply goes back there. Let the agent record its own work in the CRM, set an owner or a stage only where a rule allows it, and leave the rest to people. When a prospect replies with interest, its sequence ends and the owner gets one card with everything on it. Three steps:

  1. Choose the owner before the first message
  2. Decide which fields the agent may write
  3. Hand an interested reply to its owner

Step 1Choose the owner before the first message

Write the routing as rules in a fixed order, where the first rule that fits decides, and run it before the AI SDR’s first message. Here is the order at Example Software, an invented company whose two SDRs and one AI SDR write to finance teams.

IN THIS ORDER: THE FIRST RULE THAT FITS DECIDES 1 Has an owner2 A customer3 A territory4 Anyone else The contact or itscompany has one Its company is acustomer An SDR coversits region Rules 1 to 3don’t fit That ownerkeeps it Its accountmanager The SDR forthat region A rotation betweenthe two SDRs nonono Owner set. Then the AI SDR writes, from the owner’s inbox

In this order: the first rule that fits decides

1 Has an owner

The contact or its company has one → that owner keeps it

↓ no

2 A customer

Its company is a customer → its account manager

↓ no

3 A territory

An SDR covers its region → the SDR for that region

↓ no

4 Anyone else

Rules 1 to 3 don’t fit → a rotation between the two SDRs

Owner set

Then the AI SDR writes, from the owner’s inbox.

Example Software’s routing order, as an example. The first rule that fits names the owner before the AI SDR writes a word.

Then choose whose inbox the agent sends from, since the reply goes back there: from the owner’s, it reaches the person who will answer; from the agent’s own, every reply has to be passed on. Whether the agent may write to a customer at all is a contact rule (part 8); this order only names the owner.

In HubSpot, turn on “Assign company owner to contact by default” (in the settings, under Objects, then Contacts), so a contact takes its primary company’s owner, as in rule 1. For rule 4, use a workflow’s “Rotate record to owner” action, which shares contacts equally between the users you pick, among paid sales and service seats, and leave its option to overwrite an existing owner off. If no one is eligible, it assigns no owner, so let the agent write only to contacts that have one. If you use HubSpot’s prospecting agent, set its email sender to “Send from contact owner”, with a fallback sender for owners without a connected inbox.

One more setting assigns owners without any rule. With “Assign unowned contacts to email sender” on, as it is by default, “users who send or receive a one-to-one email logged to the activity timeline of an unassigned contact will be automatically assigned as the contact owner.”

HubSpot, “Assign ownership of records”

So if the AI SDR’s emails are logged in HubSpot as one person’s one-to-one emails, that person becomes the owner of every unowned contact it writes to, whatever your rules say. Writing only to contacts with an owner settles it; you can also turn the setting off in your contact settings.

Step 2Decide which fields the agent may write

The agent should record its own work and leave people’s decisions alone. Sort the fields into three groups, and keep the list in the agent’s tool, so it sends the CRM nothing else. The keys it holds are in part 6.

THE AGENT WRITESPEOPLE ONLY WITHIN A RULE A note on each message it sentThe date it last wroteThe reply’s class An owner, where none is setLifecycle stage, up to LeadA task for the contact’s owner An owner already setA deal’s stageLifecycle stage past Lead

The agent writes

A note on each message it sentThe date it last wroteThe reply’s class

Within a rule

An owner, where none is setLifecycle stage, up to LeadA task for the contact’s owner

People only

An owner already setA deal’s stageLifecycle stage past Lead
Which CRM fields the AI SDR may change, as an example. It records its own work, sets an owner or a stage only where a rule allows it, and leaves the rest to people.

Then check what it changed. In HubSpot, open a contact, click Actions, then View property history: each value shows its date and its source. A person’s edit lists their name, a connected app appears as “Integration”, and a custom agent’s change shows the agent’s name and who created it. Each week, export the owner property’s history (HubSpot offers it across all records) and look into any change your routing didn’t make. Plan to undo by hand: “The restore action is not available on every row. It only appears when the source is a CRM UI edit, import, or workflow.”

Step 3Hand an interested reply to its owner

When a prospect replies with interest, end the AI SDR’s sequence and let the owner take over. Send the hand-over to the person who decides, as in support part 9: here, the contact’s owner. Give them one card, so the prospect explains nothing twice.

Hand-over to SDR 2, the contact’s owner reply classed: interested THE THREADWHY THIS CONTACTDATA SOURCEOWNERTHE AI SDR WHAT IT PROMISED 3 messages, 6 to 15 October, and the reply of 16 October, in full Finance director at a 300-person logistics firm, new in the role Email and title from Clay, found on 2 October SDR 2, by rule 3 (territory), set before the first message Its sequence ended on the reply. The next message is the rep’s A 20-minute call. Nothing else

Hand-over to SDR 2, the contact’s owner

interested
The thread
3 messages, 6 to 15 October, and the reply of 16 October, in full.
Why this contact
Finance director at a 300-person logistics firm, new in the role.
Data source
Email and title from Clay, found on 2 October.
What it promised
A 20-minute call. Nothing else.
Owner
SDR 2, by rule 3 (territory), set before the first message.
The AI SDR
Its sequence ended on the reply. The next message is the rep’s.
The card the owner gets when a prospect replies with interest, as an example. The rep answers in the same thread, knowing what was promised and why this person was chosen.

Why this contact and where its data came from both come from the record (part 13), and the reply’s class from part 7. What it promised should be nothing beyond the offer you wrote for it (part 5). HubSpot’s help page for its prospecting agent doesn’t say what the agent does when a contact replies, so build the hand-over yourself: its workflows can take a record out of a play. If the prospect books a meeting with another rep, HubSpot keeps the owner: “the existing owner won’t be replaced.”

Next in this series

Part 10: testing an AI SDR before it emails anyone. See all 13 parts.

Where Himmel fits

Your agent’s tool asks Himmel before it sets an owner or a lifecycle stage, against the routing and field rules your head of sales confirmed in plain words. Every answer is kept with its facts and the rules’ version, and the check’s ID goes on the agent’s note, so you can show later why a contact went to SDR 2.

Sources

  1. HubSpot, “Assign ownership of records”, read on 21 October 2026.
  2. HubSpot, “Sync ownership between contacts and companies”, read on 21 October 2026.
  3. HubSpot, “Assign and rotate record owners using workflows”, read on 21 October 2026.
  4. HubSpot, “Set up and use the prospecting agent”, read on 21 October 2026.
  5. HubSpot, “View a record’s property history”, read on 21 October 2026.
  6. HubSpot, “HubSpot’s change sources”, read on 21 October 2026.

Why we write these guides