Sales agent cold start: fix territory data before go-live

By KYN AI Advisory Team — AI implementation specialists, Singapore

A sales agent set up for a new rep inherits whatever the CRM says about territory, and territory data is usually stale. Accounts are owned by people who left, split across carve-ups that were never closed, or listed twice. The agent then contacts dead accounts and duplicates a colleague's outreach, faster than a person would. Fix ownership as master data before go-live, test against real history, and make the agent flag conflicts instead of resolving them.

What is the cold-start problem?

When a rep joins or a territory changes, accounts are reassigned. The agent for that rep starts with a list: these accounts are yours. If the list is wrong, every action the agent takes is wrong from day one.

A person with a bad list notices. They call an account and hear "we spoke last month with your colleague." An agent does not hear that. It sends the email.

Where does territory data go stale?

• Owner fields. The owner is a person who left the company. Accounts sit unassigned or default to a manager.
• Carve-up logic. Territories split by region, size or industry. The rules live in a slide or someone's head, and the CRM holds a partial copy.
• Orphaned accounts. Records with no owner and no recent activity, which nobody claims.
• Duplicates. The same company under two names, owned by two reps.
• Closed-lost and churned accounts still marked as active prospects.

Why does an agent amplify the damage?

Speed and volume. A rep with a bad list wastes a day. An agent with the same list contacts hundreds of accounts before anyone checks. It also writes to the CRM, so the error spreads into the record that the next report reads.

What do the symptoms look like?

• Two reps, or a rep and the agent, contact the same account within a week.
• Outreach goes to accounts marked churned or closed.
• Quota disputes: both people claim credit for the same deal, and the log cannot show who acted first.
• Reply rates fall on a territory that looked large on paper.

How do you reset before go-live?

Treat ownership as master data

1. Export every account in the territory with owner, last activity date and stage.
2. Remove or reassign accounts whose owner has left.
3. Merge duplicates by domain, registration number or phone.
4. Write the carve-up rule down in one sentence per segment, and apply it to the data.
5. Name one person who owns the territory definition.

Audit against real history

Do not test on a sandbox copy. A copy hides the mess you are trying to find. Instead:

1. Take the real records read-only.
2. Run the agent in draft mode, with nothing sent.
3. Have the new rep review the first batch of drafts and mark each as right, wrong account or wrong timing.
4. Trace every wrong one to a data cause and fix the cause, not the draft.
5. Re-run until the error rate is one you accept.

How do you prevent recurrence?

• Flag over auto-resolve. If two owners claim an account, the agent stops and raises it. It does not pick.
• Cooling rule. No contact with an account that had activity from another owner recently without approval.
• Approval for new contacts. First-touch messages wait for a named person.
• Monthly hygiene list. Accounts with no owner, no activity for six months or a departed owner.
• Log every action with the actor. When a dispute arises, the log answers it.

What does a territory audit find in practice?

Illustrative example. The figures are made up to show the method. Run the same counts on your own export.

A distributor hands a new rep a territory of 1,200 accounts. Before the agent is switched on, the sales operations lead exports the list with owner, last activity date and stage, then runs six checks.

| Check | Result in the example | Action | |---|---|---| | Owner has left the company | 140 accounts | Reassign or return to a pool | | No owner field filled | 85 accounts | Assign by the carve-up rule | | Last activity older than 18 months | 310 accounts | Move to a dormant list; exclude from outreach | | Duplicate company records | 60 pairs | Merge by domain or registration number | | Marked churned or closed-lost but stage still "prospect" | 45 accounts | Correct stage; suppress | | Claimed by two owners | 30 accounts | Escalate to the territory owner for a decision |

After the clean-up, roughly 600 accounts remain as live targets for the agent. The rest are not lost. They are parked until someone has a reason to contact them. A rep who starts with 600 verified accounts will out-perform one who starts with 1,200 unverified ones, because every message lands on someone who should receive it.

The numbers matter less than the habit. Count each category before go-live and after, and keep the counts.

Which fields must be correct before the agent reads them?

An agent that writes outreach or schedules follow-ups depends on a short list of fields. Treat each as master data with an owner.

| Field | Why the agent needs it | Common fault | |---|---|---| | Account owner | Decides who may contact the account | Departed employee; manager default | | Territory or segment | Decides which carve-up rule applies | Free text; several spellings | | Stage | Decides which message type is allowed | Not updated after meetings | | Last activity date and actor | Triggers the cooling rule | Missing for activity outside the CRM | | Primary contact | Decides who receives the message | Left the client; role changed | | Do-not-contact flag | Stops outreach | Held in a different system | | Parent or group | Avoids two reps contacting one group | Subsidiaries listed as separate accounts |

Add validation at the point of entry for the fields that fail most often. A required field with a pick-list prevents the free-text spelling problem.

How should the carve-up be written?

A carve-up that lives on a slide will not survive contact with an agent. Write it as rules the data can test.

1. By geography. A postal prefix, a country or a city maps to a territory.
2. By size. An employee count or revenue band maps to a segment.
3. By industry. A standard industry code maps to a specialist.
4. By named account. A short list overrides the three rules above.
5. By precedence. When rules conflict, the order is named account, then industry, then size, then geography.

Test the rules on the export. Count accounts that match no rule and accounts that match two. Both counts should reach zero, or each leftover should have a person's name next to it.

Keep the rules in one table in the database with an effective date. When the carve-up changes, add a row. Do not overwrite the old one, so that you can answer "who owned this account in March?"

What does a draft-only week look like?

Plan the first week of a new rep's agent day by day.

| Day | Activity | Output | |---|---|---| | 1 | Final data checks; agent account created with read access and a staging table for drafts | Sign-off from the territory owner | | 2 | Agent drafts for 50 accounts; nothing sent | Drafts in a review queue | | 3 | The rep grades each draft as right, wrong account or wrong timing | A list of errors with causes | | 4 | Fix causes in the data or rules; re-run the same 50 | A lower error count | | 5 | Approve a small live batch; every message waits for the rep | First sends, logged with the actor |

Repeat the grading with a fresh sample of 50 each week for the first month. Increase volume only when the wrong-account count stays at an agreed level, and set that level before you start.

How should the agent behave when two people claim an account?

The agent must not choose. A short matrix helps.

| Conflict | Agent action | Who decides | |---|---|---| | Two owners listed | Stop; raise to the territory owner | Territory owner | | Another rep logged activity in the last 30 days | Hold; show the other rep's last touch | New rep, after a check with the other | | Parent and subsidiary owned by different reps | Hold; show both records | Territory owner | | Owner has left and no replacement is named | Hold; add to the hygiene list | Sales manager | | Account in a named-account override | Follow the override, log it | Rule owner |

The 30-day window is an example. Set it from your own sales cycle.

Every hold lands in a queue with the reason and the data the agent saw. A person clears the queue daily during the first month.

What edge cases come up?

• Mid-quarter reassignment. Credit rules decide whether the old or new owner earns on deals in progress. Write the rule first, then reflect it in the data. The agent should pause on any account with an open deal until the rule is applied.
• Shared and partner-sourced accounts. Add a field for the source and the credit split. Without it, the agent cannot tell a partner-sourced introduction from a cold account.
• Multi-country groups. One group may sit in two territories. Name a lead owner and give the other a read-only role.
• Rep leaves. Freeze the agent for that rep on the departure date, move the accounts to a pool and unfreeze only after reassignment.
• Acquired accounts. Imported lists bring their own duplicates. Run the merge check before the import goes live.

What access should the agent have?

The territory problem is also an access problem. The agent should see only the accounts that its rep owns.

• Give each rep's agent a restricted account in the cloud provider's identity service, not the rep's login.
• Use row-level security in the database so that the agent's queries return only that rep's accounts.
• Allow read access to the account list and write access only to a drafts table.
• Log every read and every draft with the agent's account name and the rep it serves.

If the territory changes, the access changes with it, in one place. A mistake in the data then cannot spread beyond the rows the agent is allowed to see.

How do you report on territory health?

Use a short monthly list, with counts and a person assigned to each category.

• Accounts with no owner.
• Accounts whose owner has left.
• Accounts with no activity for six months.
• Accounts with two claimants.
• Accounts contacted by two actors within 30 days.
• Agent drafts rejected as wrong account, and the top three causes.

The last two lines show whether the controls work. If wrong-account rejections do not fall month on month, the problem is in the rules or in the data entry, and the fix belongs upstream of the agent.

How do you settle a quota dispute with the log?

Disputes about credit usually come from not knowing who acted first. The audit log answers it if it records three things for every outreach step: the actor (a named rep or a named agent), the account and the time. When two people claim the same deal, pull the first logged touch and the last logged touch by each actor, and compare them with the credit rule written for the territory.

This turns a debate into a lookup. It also changes behaviour, because reps know that contact is recorded and that the agent will hold when another owner has acted recently. Write the credit rule before the first dispute, publish it to the team and apply it the same way every time.

What belongs on the go-live checklist?

1. Ownership export reviewed; departed owners reassigned.
2. Duplicates merged; parent and group fields filled.
3. Carve-up rules written, tested and dated.
4. Do-not-contact list loaded and checked against the account list.
5. Agent account created with read access and a drafts table only.
6. Row-level security tested with a query that should return nothing.
7. Draft-only week completed, with graded results kept.
8. Approver named for first-touch messages, with a back-up.
9. Hygiene report scheduled for the first of each month.
10. Territory owner named and told that the conflict queue is theirs.

Sign the list. If any line is open, the agent stays in draft mode.

Add it to the onboarding checklist

For every new rep or territory change: audit ownership, run a draft-only week, approve the first batch, then release. Treat it as part of onboarding, not a clean-up project after the first complaint.

Where KYN fits

KYN builds sales agents that run in the client's own cloud account, with agents on their own restricted accounts and every action logged with the actor. Outbound messages wait for a named person. The first 14 days are a review of your stack, including the CRM fields an agent would read, and a full build ships in under 90 days. See sales systems and infrastructure. For the related handoff design, read when an AI sales agent should escalate.

Frequently asked questions

How long does a territory data audit take?

For a few thousand accounts, a few working days: export, deduplicate, reassign and review. The time sits in deciding ownership rules, not in the export.

Should the agent be allowed to reassign accounts?

No. Reassignment changes who earns credit and who is accountable. The agent can propose a change and a named person approves it.

What if the CRM history is too poor to trust?

Start with a smaller scope: the accounts with recent verified activity. Expand the list as the data is cleaned, and keep draft-only mode until the error rate is acceptable.

Checked 30 October 2026.

Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.

Start Building →