Manage exclusions and Do not contact

Keep audience exclusions, person and company restrictions, and relationships clear; recover from unknown checks without bypassing a stop.

Choose the right kind of exclusion#

Start with your business objective, then tell Kite which people or businesses would be unsuitable for it. You can refine this with Kite; you do not need a finished audience definition to begin.

Choose the control that matches your decision:

Your decision	Where it belongs
A business, territory or profile should be outside this mission’s audience	The mission brief and targeting exclusions
A person must not receive outreach	Settings → Do not contact → Never contact
Everyone at a specific company must be excluded from this workspace's outreach	A company-domain entry in Never contact, with the matching limits checked
Your team already manages the relationship	Settings → Do not contact → Handled by you

For example, a cleaning company might exclude buildings outside its service area in the mission brief. A facility contact who asks not to hear from you belongs in Never contact. A current referral partner whose relationship you manage belongs in Handled by you, with an accurate reason. If that partner also asks not to be contacted, respect that request; personal handling does not override it.

Changing the target market does not erase an opt-out, restart stopped outreach or restore consumed Reach. See Choose the right people and How Reach is counted.

Open the correct workspace#

Confirm the workspace name, then open Settings → Do not contact. The page separates three jobs:

Never contact records people who must not receive outreach.
Handled by you records relationships your team manages.
Stopped by KiteGTM shows recent checks that stopped work and the recorded reasons.

The lists show records visible to this workspace. Other restrictions can apply without appearing here. An empty list is not permission to contact someone, and a list that could not be read must remain unknown.

**Review the workspace lists**
Never contact shows the workspace scope, four records and reason filters; Jordan Patel, Avery Chen and Sam Rivera are visible.

Read why a person is on Never contact#

Read the person’s recorded address, number or LinkedIn identity, the reason and any supporting context. Do not match someone by name alone. Two people can have the same name, and a person can use more than one contact identity.

The They asked reason means the person’s request matters. When Read what they wrote is available, open it and read the recorded message before deciding what to do. Keep its wording and context intact; do not turn a vague response into a confirmed opt-out or permission to continue.

If a contact is labelled Contact on hold, an unresolved preference needs review. A possible complaint or opt-out is different from a confirmed registry entry. Do not try to clear that hold by removing a row from this list.

**Read the recorded request**
The expanded Jordan Patel row shows the request to be taken off the list, its conversation context and the matched words.

Add a person to Never contact#

Select Add on Never contact.
In Their address, number, LinkedIn profile or company domain, enter the actual person’s address, number or LinkedIn profile.
Choose the accurate Why: Already yours, You decided or They asked.
Add useful context in the optional note. Keep secrets and unnecessary private information out of it.
Check the person and reason before selecting Add them. This saves a do-not-contact entry; Cancel leaves without saving it.

The current account form applies the restriction across email, LinkedIn and texts when Kite matches the recorded identity. It does not offer a choice to block only one channel. A previously recorded channel label is not permission to try another route.

Record each known contact identity through the supported controls. An email-only entry does not prove that an unrelated LinkedIn profile or a new phone number can be recognised as the same person. Do not switch identities or channels to bypass someone’s request.

**Prepare a person restriction**
The Do not contact form contains riley@example.invalid, They asked, A note and known-identity all-channel guidance; Add them is available and has not been pressed.

Keep company exclusions in the brief#

A mission's targeting exclusions and a workspace's company restriction serve different purposes. Keep audience choices such as territory, business type or unsuitable profiles in the mission brief.

When you intend to stop outreach to a specific company across this workspace's campaigns, open Never contact → Add and enter its company domain. The form recognises a domain such as example.invalid, explains the match and offers Add the company. Choose the accurate reason and check the scope before saving. Cancel leaves without adding it.

The company entry matches people whose recorded email address or company website is at that domain. A person known only by a phone number or LinkedIn profile cannot be placed at that company from that identity alone; add known people whose records show neither company field separately. Do not infer that every employee was matched.

Use the company's own domain. A free-email provider, a page on a shared host or a hosted sub-site is not a company identity to block. Read any refusal rather than substituting an unrelated domain. Editing the mission audience does not remove a company restriction or a person's opt-out.

**Review a company-domain restriction**
The Do not contact form recognises example.invalid as a company, explains recorded email and website matching, and offers Add the company; nothing has been saved.

Record relationships your team handles#

Open Handled by you and select Add. Enter the person’s identity and complete Why they are yours with enough context for another teammate to understand the relationship. For example: “Current referral partner. Taylor manages this relationship.”

Add them records the relationship handling choice. Campaigns skip the matching person while your team manages the relationship. Their contact preferences still apply; this is not unconditional permission to write manually.

Keep an explicit opt-out in Never contact. Do not move it to Handled by you, change the reason or delete it simply to make the person available to a campaign.

**Read relationship handling**
Handled by you shows Casey Brooks and the referral-partner explanation. The guide keeps contact preferences separate from this relationship choice.

**Prepare a relationship record**
Somebody you handle yourself contains alex@example.invalid, Alex Kim and the relationship reason, with Cancel and Add them controls; nothing has been submitted.

Use the stopped-work log to find the source problem#

Open Stopped by KiteGTM. Read the address, recorded reason, campaign or verification context, and date. The view loads up to 500 recent checks from the last 30 days and shows recognised stop reasons; its shorter date filter narrows those loaded records. It is not a complete contactability audit.

Recorded reason	Useful next step
On your do-not-contact list	Respect the restriction; do not remove it to retry outreach
Not an address	Check the source record or CSV mapping; a name is not an email address
Shared inbox	Review whether the intended recipient is an identifiable relevant person
Domain takes no mail, Throwaway address or Bounced last time	Check the original record and the recorded delivery problem before considering any further action

Correct a data problem in the record or import it came from. This log does not have a control to erase a stop, restore a recipient or replay a send. A missing or empty log does not establish that contact is allowed.

For a column or file problem, follow Import a contact list and check the result. Do not assume a new import repairs an opt-out or rolls back earlier changes.

**Read the bounded stopped-work log**
Stopped by KiteGTM shows three recent stop records with do-not-contact, shared-inbox and malformed-address reasons, plus the 30-day view bound.

Review removal without promising a restart#

Removal is a deliberate account change. For Never contact, Remove opens a review dialog. Read the identity and the reason before choosing anything.

When the person asked not to be contacted, the dialog preserves that request and warns that removing the workspace’s registry entry does not undo it. Keep the entry unless you have verified a wrong-person error or a later request from that person to hear from you. Do not infer either from a changed address, a new mission or a teammate’s assumption.

Removing an entry does not restart stopped work or guarantee that a campaign includes the person. Other workspace, global, provider, recipient-status or unresolved-preference restrictions can still apply. Removal does not close a separate review hold.

Handled by you also has a Remove action. Review the relationship and the person before using it; that action can immediately change the workspace’s entry. This tutorial demonstrates inspection and cancellation, without removing either type of record.

**Review removal without restarting work**
The removal dialog for Jordan Patel preserves the request not to be contacted, warns that removal does not restart stopped work and offers Leave them alone.

Recover from an unreadable result#

If the list or the person’s status could not be read, keep it unknown. Reload the page and confirm the intended workspace and your access. An incomplete response, a partial list or missing counts must not become “nobody is blocked.”

If saving or removing times out, do not repeatedly submit the action. Read the relevant current record through supported controls before deciding whether to try again. A toast, a prepared form or a missing row alone does not prove every restriction has changed.

If the problem remains, prepare the workspace, screen, timestamp and exact visible error for Get help with useful context. Share private identities only through an authorised support route; keep them out of public University citations.

Watch the controls#

Follow the workspace lists, person and company-domain forms, relationship handling, stopped-work log and removal review. Read the company match before deciding whether to add it. Use the written steps and transcript whenever they are easier to follow. The walkthrough stops at inspection or cancellation; it does not save an entry, remove a restriction or send a message.

64 sec · Captioned, no audio

Manage exclusions and Do not contact

Work with your agent#

Ask your agent to prepare a targeting and contact-restriction review. It can retrieve this public guide and, when separately connected and permitted, read supported account evidence. Public University retrieval cannot see your workspace’s contacts or restrictions.

Keep recorded facts, unclear identity matches, unresolved holds and proposed changes separate. A clear result from one check does not authorise outreach. Review any intended account action yourself in Kite.

Work with your agent

A clear task to copy

Help me prepare a Kite targeting and contact-restriction review without making account changes. Retrieve the current University guide Manage exclusions and Do not contact; cite its stable section URL and version. Public University tools cannot read my workspace. If separately connected and authorised, discover your current account tools, confirm the intended workspace and access, then use only relevant supported reads and IDs actually returned by those reads.

Separate mission audience exclusions, Never contact person and company-domain entries, Handled by you relationships and recent stopped-work checks. Use recorded addresses, phone numbers and LinkedIn identities rather than name matching. For a company-domain restriction, use the company's own domain and preserve the recorded-email or company-website match limits. People with neither field need their own person entries. Do not invent a channel-specific exception or infer every employee was matched. A result for one identity does not prove that an unrelated identity belongs to the same person or is unrestricted. Respect the person’s request across channels.

If dnc.list or dnc.check is supported and permitted, preserve its scope, counts, pagination and evidence. Missing, malformed, partial, capped, timed-out, unavailable or indeterminate responses stay unknown. A missing row or an empty customer list is not permission to contact someone; other restrictions may apply. A possible complaint or opt-out hold needs review and is not a confirmed opt-out or a registry entry removable by dnc.remove. The stopped-work view is bounded to recent recognised checks, not every possible stop or actual send attempt.

Return a proposed audience-exclusion brief, identity and reason checks, current facts with timestamps, unresolved matches or preference holds, and the specific in-app review steps. Preserve private quotes in authorised context only; do not publish contact identities or account evidence in University citations. Do not call dnc.add, dnc.remove, upload, enrollment, approval, hold-resolution, retry, restart or send tools. Do not erase an opt-out, shift it to personal handling, substitute an identity/channel, change permissions or start work. Removing a workspace entry does not close separate holds, restore recipients or restart stopped outreach. I will separately decide and perform any intended account action in Kite.

This prepares guidance. Use the controls in your Kite workspace for account changes and starting work.

Before you move on#

Your objective excludes unsuitable audiences, known person restrictions are recorded under the correct identities, relationship handling is explained, and unreadable or unresolved results remain explicit. An Introduction still requires willingness to talk and your required criteria; an eligible contact is not an Introduction.

Your readiness check

0 of 6 checked

I confirmed the intended workspace and my accessI separated audience exclusions from person and company restrictionsI checked recorded identities and the accurate reasonI documented relationships my team manages without overriding opt-outsI kept unreadable results and unresolved holds explicitI understand that removing an entry does not restart stopped workThese checks stay in this browser. These are your notes; Kite’s actual account state and start checks decide readiness.