Existing Customer vs. Suppression: Two Different Pipeline Controls

Who this governance guide is for

This guide is for tenant administrators, revenue operations, customer teams, and campaign owners who need to exclude companies correctly. It explains the SellersGPT operational distinction and only the minimum billing consequence necessary to apply it. It does not define lead prices, invoices, credits, disputes, or financial accounting; those belong to Module 05 and product documentation. It also does not determine legal obligations for every jurisdiction.

Contents

1 Ask two separate control questions 2 Define Existing Customer evidence and scope 3 Define Suppression reasons and scope 4 Use the two-control decision matrix 5 Apply precedence without deleting meaning 6 Propagate controls across the pipeline 7 Review, expire, or resolve a state safely 8 Illustrative example 9 Common mistakes 10 What this does not mean 11 Common questions 12 Sources and methodology

1. Ask two separate control questions

The controls answer different questions: 1 Existing Customer: Does verified evidence establish a commercial relationship that SellersGPT must exclude from prospect outreach and related lead billing under the declared scope? 2 Suppression: Is outreach blocked for this company/person/channel/purpose even though customer status is separate, absent, unknown, or irrelevant? One field cannot answer both without losing consequences. If a current customer is recorded only as suppressed, outreach stops but downstream systems may fail to recognize the billing block. If a non-customer with a company-stop request is mislabeled Existing Customer, outreach stops but the historical reason becomes false and commercial reporting is distorted. Use a four-state model: Existing Customer Suppression Outreach SellersGPT lead billing Required interpretation No No Eligible only if all other gates pass Governed by normal qualified-lead rules No control from these two states Yes No Blocked Blocked Relationship control No Yes Blocked Not blocked by Suppression itself Outreach-only control; other billing gates still apply Yes Yes Blocked Blocked Preserve both relationship and suppression reasons "Not blocked by Suppression itself" does not mean a charge automatically occurs. It means Suppression is not the billing control. Qualification and other Module 05/product rules remain separate.

2. Define Existing Customer evidence and scope

Existing Customer should be based on authorized first-party relationship evidence, such as an accepted customer master record, current contract/order/service record, verified tenant import, or authorized account-team confirmation. Define what existing means in tenant policy: current at what entity, product, business unit, and time? Required fields:

• legal/operating entity identifiers;

• parent, subsidiary, and site relationships where relevant;

• relationship type and in-scope product/service;

• authoritative source and record ID;

• effective start and, where appropriate, end/review date;

• account owner;

• confidence and unresolved identity issues;

• outreach block scope;

• billing block scope;

• change history. Entity scope matters. A global parent may be a customer while a separately operated subsidiary is not, or tenant policy may treat the family as one relationship. Do not guess. Write the identity-matching and relationship rule before execution. Existing Customer is not proof of satisfaction, renewal intent, cross-sell eligibility, or permission for marketing. It is a commercial relationship control. Separate customer communications, service, and account growth policies are outside this prospecting playbook.

3. Define Suppression reasons and scope

Suppression blocks outreach without asserting customer status. Common operational reasons include:

• explicit company-stop request;

• person or channel opt-out at the applicable scope;

• contractual or partner exclusion;

• territory or account-owner protection;

• data-quality or identity ambiguity;

• legal/compliance hold;

• active dispute or sensitive event;

• tenant manual exclusion;

• duplicate/campaign conflict;

• temporary timing or capacity hold;

• existing human conversation where prospecting should pause. Do not store only suppressed = true. Store reason, source evidence, scope dimensions, effective time, owner, permanence or review trigger, workflows affected, and resolution authority. The FTC CAN-SPAM guide and CRTC CASL FAQ describe covered commercial-message requirements in their jurisdictions. SellersGPT suppression can also enforce business policies that go beyond a particular legal minimum. A suppression record should preserve the actual reason rather than imply every exclusion has the same legal basis.

4. Use the two-control decision matrix

Apply the SellersGPT Customer-Suppression Decision Record: Field Existing Customer record Suppression record Core assertion Verified in-scope customer relationship Outreach prohibited/held at declared scope Evidence Authorized relationship source Request, policy, hold, identity, owner decision Outreach effect Block Block Billing effect Block None by this control alone Typical scope Entity/account/relationship/time Company/person/channel/purpose/campa ign/time Review owner Customer/account-data authority Control owner appropriate to reason Resolution Verified relationship change Authorized lift/expiry after condition resolved History Immutable prior state Immutable prior state Make the pipeline decision from both records. Do not ask which one "wins." If both are true, both consequences apply and both reasons remain visible.

5. Apply precedence without deleting meaning

Use consequence precedence:

• If Existing Customer is true, outreach is blocked and billing is blocked.

• If Suppression is true, outreach is blocked.

• If either is unknown and the uncertainty could cause prohibited outreach or incorrect commercial treatment, hold the affected path for review.

• If both are true, retain both; do not collapse them into Existing Customer. A company stop may create Suppression even when an Existing Customer relationship already blocks outreach. Keeping the stop request matters because customer status could later end while the request remains. Conversely, a temporary suppression might expire while Existing Customer continues to block both actions. The GAO Green Book includes principles related to quality information, control activities, responsibility, communication, and monitoring in federal internal control. It is not a CRM standard. The relevant lesson is that controls need defined objectives and reliable information; two controls with different objectives should not be represented by one ambiguous field.

6. Propagate controls across the pipeline

Both controls must reach all relevant paths:

• account research/admission;

• contact sourcing and replacement;

• outreach scheduling and sending;

• round progression;

• qualification review;

• active-lead routing;

• billing eligibility checks;

• imports, deduplication, and ICP migrations;

• reporting and audit. Use stable entity identifiers and reconcile parent/site records. A domain-only match can create false positives and false negatives. Record the evidence and confidence behind the match, and hold ambiguous cases. The NIST Privacy Framework and Office of the Privacy Commissioner of Canada's PIPEDA fair information principles address privacy risk and personal-information practices in their respective scopes. They do not prescribe customer suppression architecture. They support purpose limitation, accuracy, accountability, safeguards, and appropriate lifecycle controls for the information used to enforce decisions.

7. Review, expire, or resolve a state safely

Existing Customer changes only when authorized relationship evidence changes. Suppression changes only under the resolution path attached to its reason. Neither clears because:

• a new ICP activates;

• a campaign is duplicated;

• a new contact is found;

• an employee changes;

• a set period passes without a configured expiry;

• a list is re-imported;

• the company engages through another channel. Use an append-only transition: Transition field Requirement Prior state Value, scope, evidence, effective time Proposed state Value and consequence Trigger Relationship change, expiry condition, corrected identity, authorized lift Evidence Source record and date Authority Person/role allowed to approve Impact check Workflows, active leads, billing eligibility, reports Effective at Timestamp Review Second check where required The NIST Cybersecurity Framework 2.0 is a cybersecurity-risk framework, not a GTM control system. Its governance and improvement concepts provide a limited analogy for maintaining policy, roles, oversight, and change history.

8. Illustrative example

Illustrative example - fictional. Fictional supplier Vale Bearings imports six companies into a prospective-account review:

• Company A is a verified current customer, not separately suppressed.

• Company B is not a customer but has a company-stop request.

• Company C is both a current customer and has a company-stop request.

• Company D has neither state.

• Company E has an ambiguous parent-company match.

• Company F has a temporary territory suppression. The correct outputs are: A blocks outreach and billing; B blocks outreach but Suppression alone does not determine billing; C blocks both and retains both reasons; D proceeds only to other eligibility gates; E holds for identity review; F blocks outreach until authorized resolution/expiry. Nine pipeline workflows must acknowledge the controls. Eight acknowledge; a legacy import path does not. control propagation coverage = 8 / 9 = 88.9% No outreach or billing-sensitive processing proceeds for affected records until the ninth path is controlled. After remediation, coverage becomes 9 / 9 = 100%. This measures control propagation, not customer value, qualification, or revenue.

9. Common mistakes

• Using one vague do-not-contact flag for both states.

• Marking a company Existing Customer merely because someone recognizes the name.

• Treating Suppression as a billing block or as automatic charge permission.

• Deleting suppression when customer status is added.

• Clearing either state during an ICP migration.

• Matching entities by email domain alone without ambiguity handling.

• Applying company status to every affiliate without a declared identity rule.

• Reporting high propagation coverage while one execution path remains uncontrolled.

10. What this does not mean

This guide does not define accounting, invoices, refunds, disputes, lead pricing, or customer revenue. It does not say suppression has no commercial importance; it says its direct SellersGPT consequence is outreach blocking, while other systems apply their own gates. It does not make Existing Customer a marketing-consent status. It does not require perpetual retention of unnecessary data. It requires sufficient, accurate, governed evidence to enforce the product decision.

11. Common questions

If a company is an existing customer, do we also need suppression? Only when a separate outreach-stop reason exists and should survive independently. Existing Customer already blocks outreach and billing, but retaining an explicit company-stop or policy reason can matter if customer status later changes. Does Suppression mean a lead can be billed? No. Suppression simply does not create the billing block that Existing Customer creates. Qualification and all other billing controls remain separate. Can customer status be limited to one subsidiary or product? Yes, if tenant policy and authoritative evidence define that scope. Record the entity and relationship boundaries; hold ambiguous parent/subsidiary matches. Can a new ICP remove these controls? No. ICP change affects targeting logic. It does not resolve customer relationships, opt-outs, company stops, or other suppression reasons.

12. Sources and methodology

The sources inform internal-control quality, privacy/accountability, communication constraints, and governed change in their stated domains. They do not define SellersGPT states. The Existing Customer and Suppression consequences, matrix, decision record, and propagation rule are SellersGPT product rules or editorial tools. 1 U.S. Government Accountability Office, Standards for Internal Control in the Federal Government (Green Book). https://www.gao.gov/greenbook. Accessed August 25, 2026. 2 National Institute of Standards and Technology, Privacy Framework. https://www.nist.gov/privacy-framework. Accessed August 25, 2026. 3 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. 4 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. 5 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. 6 National Institute of Standards and Technology, Cybersecurity Framework 2.0. https://www.nist.gov/cyberframework. Accessed August 25, 2026.