How to Replace a Contact Without Resetting Account Learning

Who this playbook is for

This playbook is for B2B teams that have a still-eligible company but an invalid, unreachable, inappropriate, or explicitly skipped contact. It is useful for manufacturing and industrial sales where titles vary, employees move, and a purchase function may sit at a site, regional office, parent company, contractor, or channel partner. It does not authorize contact discovery, override an unsubscribe or company stop, or assume a replacement person has the same role or views as the predecessor.

Contents

1 Separate account continuity from person change 2 Use the replacement-trigger matrix 3 Close the old path at the correct scope 4 Define the role gap before finding a person 5 Transfer the account-learning continuity packet 6 Protect round and contact-pool limits 7 Verify the replacement before use 8 Illustrative example 9 Common mistakes 10 What this does not mean 11 Common questions 12 Sources and methodology

1. Separate account continuity from person change

An account record describes the company-level history: why the organization qualified, which application was tested, what messages and evidence it received, what responses occurred, what the team learned, and which controls apply. A contact record describes a person or reachable endpoint: identity evidence, current company relationship, functional-role hypothesis, channel, status, and person-level requests. When a contact changes, preserve this distinction: Keep at account/round level Re-evaluate for the new contact ICP version and application scope Current employment or company association Prior company exposure and round number Functional role in this purchase Claims, proof, and offers already used Relevance of the next message Company-level stop and customer states Person and channel eligibility Human interactions and commitments Identity and address confidence Unresolved account questions Appropriate contact purpose A new person must not inherit another person's sentiment, authority, consent, objections, or private remarks as facts. At the same time, the company must not be treated as untouched. This two-sided rule prevents both lost learning and inappropriate personal inference.

2. Use the replacement-trigger matrix

SellersGPT recognizes defined replacement triggers. The matrix below explains their operational meaning; it is a SellersGPT editorial tool, not a legal classification. Trigger Old path action Replacement review Learning to preserve Wrong or invalid contact Mark role/path invalid Yes, if company remains eligible Why the role/path failed Hard bounce Stop the address Yes Delivery code and affected endpoint Contact unreachable Close governed channel after defined checks Yes Attempts and channel evidence Manual skip Record authorized reason Yes, if scope remains eligible Operator rationale Trigger Old path action Replacement review Learning to preserve Authorized workflow skip Record workflow decision and reason Yes, subject to controls Decision evidence, not internal mechanics Follow-up proves mismatch Stop current purpose for that contact Yes Exact mismatch evidence Configured timeout Trigger review, not automatic send Maybe Window and prior exposure Left company Mark permanently ineligible for new rounds Yes Departure evidence and date Retired Mark permanently ineligible for new rounds Yes Retirement evidence and date Unsubscribe Apply requested stop scope Only if company-level rules still permit Exact request; never route around it Company stop Stop company outreach No Exact stop request and scope Non-response by itself is not listed as proof that a person is wrong. The product's timeout can trigger a replacement review, but the reviewer still needs a role and usefulness rationale. Otherwise, contact rotation turns silence into a machine for expanding account pressure.

3. Close the old path at the correct scope

Delivery signals require precise scope. RFC 3463 defines enhanced mail-system status codes, including permanent and persistent transient conditions. RFC 5321 defines SMTP behavior. These technical standards help interpret a delivery response; they do not determine whether a person is employed, whether another address is appropriate, or whether another channel may be used. Use separate fields:

• person status;

• company association status;

• email-address status;

• channel status;

• purpose/campaign eligibility;

• company outreach status. A permanent failure for one mailbox is an address-level fact. A plain-language response stating "I retired last year" is evidence about the person's company relationship. "Do not contact our company again" may be company-level. Preserve the source text and apply the broadest scope clearly requested; escalate ambiguous cases rather than deliberately interpreting them narrowly. The FTC CAN-SPAM guide and CRTC CASL FAQ describe applicable commercial-message requirements in their jurisdictions. Replacement logic must not be used to evade opt-out or consent requirements. A new person record does not erase a company-level request, and a new address for the same person does not erase a person-level stop.

4. Define the role gap before finding a person

Replace a function, not a title string. Write a role-gap statement with: 1 decision scope - company/site, application, purchase situation, date; 2 functional contribution needed - user, technical evaluator, operational owner, procurement coordinator, etc.; 3 evidence from the failed contact path; 4 evidence that the role likely exists; 5 acceptable identity confidence; 6 prohibited assumptions; 7 next useful action if a person is verified. For example, "replace Operations Manager" is weak. "Find the function responsible for seal maintenance on packaging line 4; prior contact confirmed corporate procurement does not own site maintenance" is bounded and usable. The replacement might be a maintenance planner, reliability engineer, contractor, or still unknown. Role Before Title principles from Module 03 remain relevant.

5. Transfer the account-learning continuity packet

The Account-Learning Continuity Packet is the central tool in this playbook: Packet section Required content Account basis Active ICP version, application, geography/site, confidence Round state Current round, window, opening/expiry, owner Prior exposure Dates, channels, contacts, claims, evidence, asks Observable outcomes Delivered, bounced, replied, referred, stopped, unknown Replacement trigger Exact category, source, timestamp, reviewer Role gap Function sought and evidence basis Shared controls Existing Customer, Suppression, company stop, campaign pause Bounded personal facts Only what is necessary; no transferred sentiment assumptions Next action Useful purpose, owner, due date, decision gate Review history Changes and approvals without overwriting prior states Data minimization matters. The NIST Privacy Framework provides a voluntary framework for managing privacy risk, and the Office of the Privacy Commissioner of Canada's PIPEDA fair information principles cover accountability, purpose, limiting collection, accuracy, safeguards, openness, access, and recourse. These sources do not prescribe a sales CRM schema. They support the underlying discipline of purpose-bound, accurate, controlled information.

6. Protect round and contact-pool limits

SellersGPT's default maximum is five contacts per company. This is a ceiling on qualified-lead/contact handling for the defined company scope, not a goal. Replacement should not silently create a sixth active candidate while the old record remains counted as eligible. Maintain three counts:

• historical contacts: everyone ever recorded for the company;

• currently eligible pool: verified contacts currently allowed for this purpose;

• contact capacity consumed: records counted under the configured company maximum. Closing a permanently invalid address may free an eligible slot under approved product rules, but history must remain. A person marked left or retired stays in history with a permanent no-reentry flag. The next person remains part of the same round unless a separate round transition is explicitly approved. Replacement cannot restart the follow-up window, erase company exposure, or reset the round count merely because a row changed.

7. Verify the replacement before use

Before the new contact becomes eligible, test:

• company association is current enough for the decision;

• source and evidence date are recorded;

• functional role is confirmed, inferred, or unknown rather than presented as certainty;

• address/channel validity is checked without making unsupported identity claims;

• company and campaign controls are clear;

• prior human interaction does not require tenant takeover;

• proposed message is differentiated and useful;

• owner has reviewed any ambiguity. Never use an inferred title match to claim authority. If the evidence only supports that a person works in maintenance, say so. It may justify a carefully bounded relevance check, not a statement that they approve suppliers.

8. Illustrative example

Illustrative example - fictional. Solstice Drives is in round two with fictional Ridgeway Milling. Its eligible pool contains three contacts against the default maximum of five. One address returns a permanent mailbox failure, one contact remains eligible with no response, and one replies: "I moved to another company; plant reliability owns this." The reply is human interaction and therefore pauses ordinary company automation for review. The first record becomes address_hard_bounce; the endpoint is stopped. The second remains eligible. The third becomes left_company, permanently barred from later rounds. The referral is recorded as a role clue, not a named-person authorization. The continuity packet contains eight required control groups. Seven are complete; the team has not yet verified whether a company-level suppression exists in another campaign. continuity completeness = 7 / 8 = 87.5% Because suppression is a hard control, 87.5% is not enough to proceed. After the shared check returns clear, the team verifies a reliability planner and adds that person to the current eligible pool. Historical count becomes four; currently eligible count remains two. The round number and expiry do not reset. The new message acknowledges only the relevant application and does not repeat the former employee's personal statement.

9. Common mistakes

• Deleting the old contact and losing the trigger evidence.

• Restarting round and window counters after replacement.

• Treating one hard bounce as proof that the entire company is unreachable.

• Using an unsubscribe as a reason to find another person immediately.

• Copying predecessor sentiment or assumed authority onto the new person.

• Searching for the same title without defining the missing function.

• Failing to propagate company-level controls.

• Reintroducing a left or retired person during later data refresh.

10. What this does not mean

Contact replacement is not a tactic for maximizing the number of people contacted. It does not authorize enrichment, data collection, or messaging in every market. It does not prove that a referred function is interested, has authority, or should be approached. It does not make a company "new." It preserves a governed option to continue only when the company, purpose, contact, channel, round, and controls remain eligible.

11. Common questions

Does a hard bounce always justify a new contact? No. It stops the affected address. Replacement still depends on company eligibility, role need, pool limits, and a useful next action. What happens when a person has left or retired? Record the evidence and date, stop the person's SellersGPT outreach eligibility, and keep a permanent no-reentry state for future rounds. Do not delete history. Can a timeout automatically replace someone? A configured timeout can trigger review. The reviewer should still confirm that the contact is unusable or mismatched and that a replacement serves a defined role gap. Should the new contact receive the same message? Not automatically. Reuse verified account facts, but adapt the purpose and evidence to the new contact's actual or hypothesized function. Preserve prior exposure so the company is not treated as untouched.

12. Sources and methodology

Technical and regulatory sources establish delivery, communication, and data-governance constraints. They do not prescribe SellersGPT replacement decisions. The replacement matrix, permanent left/retired rule, five-contact default, continuity packet, counts, and completeness gate are SellersGPT product rules or editorial tools as labeled. 1 Internet Engineering Task Force, RFC 3463: Enhanced Mail System Status Codes. https://www.rfc-editor.org/rfc/rfc3463. Accessed August 25, 2026. 2 Internet Engineering Task Force, RFC 5321: Simple Mail Transfer Protocol. https://www.rfc-editor.org/rfc/rfc5321. Accessed August 25, 2026. 3 U.S. Federal Trade Commission, CAN-SPAM Act: A Compliance Guide for Business. https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business. Accessed August 25, 2026. 4 Canadian Radio-television and Telecommunications Commission, Frequently Asked Questions about Canada's Anti-Spam Legislation. https://crtc.gc.ca/eng/com500/faq500.htm. Accessed August 25, 2026. 5 National Institute of Standards and Technology, Privacy Framework. https://www.nist.gov/privacy-framework. Accessed August 25, 2026. 6 Office of the Privacy Commissioner of Canada, PIPEDA Fair Information Principles. https://www.pr iv.gc.ca/en/privacy-topics/privacy-laws-in-canada/the-personal-information-protection-and-electronic-do cuments-act-pipeda/p_principle/. Accessed August 25, 2026.