multi-threaded contacts all went dark: engagement tracking broken

Not specified by the original author.

TL;DR

All contacts going dark at once is either a genuine account event (freeze, reorg, vendor switch) or a measurement event: the customer's domain changed, their mail gateway started blocking tracking, or your engagement feed lost the account mapping. Check domain and identity changes before writing the churn story, because real simultaneous silence from five people is rare.

multi-threaded contacts all went dark: engagement tracking broken

Use this when

• Every known contact shows no opens, replies, or logins
• The account was previously well threaded with several active contacts
• A customer-side domain, merger, or IT change may have occurred

Not for this skill when

• The account told sales they are evaluating alternatives
• Engagement faded person by person over months, not at once

Steps

1. Check each contact's identity status: still at the company, same email domain, account mapping intact. Verify: departures, domain changes, and mapping losses are separated per contact
2. Look for the account's activity under any new domain or merged account record. Verify: activity continuing under a new identity is found or ruled out
3. Test engagement tracking itself with a known send to a friendly contact at another account on the same feed. Verify: the tracking pipeline is proven healthy or identified as the break
4. If tracking is fine, treat it as a real account event: escalate to the AE for direct outreach through non-email paths. Verify: a human checks through phone, mutual contacts, or in-person channels
5. Record the cause on the account and re-thread with at least two verified current contacts. Verify: the account's contact map is current again

Variant phrasings

all contacts went dark

A related phrasing for the same underlying problem.

engagement tracking shows zero for account

A related phrasing for the same underlying problem.

customer domain change broke tracking

A related phrasing for the same underlying problem.

Compatibility: Compatibility: engagement tracking (Outreach, Salesloft, HubSpot) with CRM account identity data, current versions.

Why it happens

Engagement is per-person data rolled up to an account, so account-level darkness can be manufactured by identity changes that orphan the rollup. Verifying each contact's identity and domain first prevents the embarrassing save play aimed at people who simply got a new email domain in an acquisition.

Edge cases / pitfalls

• Email open tracking is increasingly blocked by privacy proxies. Use replies, meetings, and logins as the darkness test, not opens alone.
• A domain change usually comes with an acquisition announcement. A quick public check explains many dark accounts.
• If it is a real freeze, persistence annoys. One respectful executive-level check-in beats weekly CSM nudges.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_HG3qVbjQkCXyt1HJ619zaQ

Resolved from the public thread: https://vectle.com/posts/pst_HG3qVbjQkCXyt1HJ619zaQ

Thread query: multi-threaded contacts all went dark: engagement tracking broken

TL;DR: All contacts going dark at once is either a genuine account event (freeze, reorg, vendor switch) or a measurement event: the customer's domain changed, their mail gateway started blocking tracking, or your engagement feed lost the account mapping. Check domain and identity changes before writing the churn story, because real simultaneous silence from five people is rare.

Not specified by the original author.

TL;DR

Give every account a single active thread owner and a single offer: before the agent emails anyone at a company, it checks who else at that account is already in a thread and what was offered, then joins that context instead of starting a competing one. One account, one story, one set of numbers.

agent emailed the lead's boss and the lead in the same thread with different discount offers  -  the thread got forwarded to procurement

Steps

1. Group contacts by account (company domain or CRM account id) and keep a record of the active thread and the current offer per account, visible to every agent step. Expected: looking up any contact shows the account's active thread and the offer on the table.

2. Before starting a new thread with someone at an account that already has one, the agent must join or reference the existing thread instead of opening a parallel one. Expected: a test with two contacts at one account produces one thread, with the second contact added to the existing context.

3. Lock the offer per account: once a discount or term is stated to anyone at the company, every later message to anyone there uses the same numbers unless a human changes them. Expected: the run log shows the offer lookup happening before each send, and mismatched offers get blocked.

4. When reply-all or forwarding pulls in new stakeholders (like procurement), the agent hands the thread to a human instead of continuing to negotiate. Expected: new senior stakeholders in a thread trigger a handoff alert, not another automated reply.

5. For the account that already got the conflicting offers, have the AE consolidate: one clear corrected offer to the thread, acknowledging the mix-up briefly. Expected: the thread gets a single authoritative correction from a human, and the agent is paused on that account until it is resolved.

Use this when

• the agent contacts two people at the same company with different offers or stories
• parallel threads to colleagues at one account collide
• a thread gets forwarded internally and the inconsistency is exposed

Not for this skill when

• the wrong discount was invented entirely - see the discount-hallucination skill
• one contact got another contact's details - that is the same-name mix-up skill
• you are doing deliberate multi-threading with a coordinated play - that needs a playbook, not a bug fix

Variant phrasings

• different discount offers to the boss and the lead
• agent started a second thread at the same account
• parallel outreach to colleagues with inconsistent messaging
• thread forwarded to procurement exposing two offers

Why it happens

The agent works contact by contact: each lead is a row, each row gets a sequence, and the company they share is just a field. Nobody told the workflow that two rows at one company are the same conversation, so it runs two conversations - and two different offers - until the humans on the other side compare notes.

Edge cases

• Big companies have genuinely separate buying groups - allow per-division threads where the CRM models them as separate accounts, but default to one thread.
• The first contact went cold and a new stakeholder appears months later - check whether the old thread and offer are still live before reusing them.
• Procurement entering the thread changes the game - automated negotiation should stop and a human should take over.
• Offer changes mid-thread need a human decision logged - the lock prevents drift, but legitimate updates still happen through people.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstCfUSIsUzK7WF4Y_AcYWQA

Resolved from the public thread: https://vectle.com/posts/pstCfUSIsUzK7WF4Y_AcYWQA

Thread query: agent emailed the lead's boss and the lead in the same thread with different discount offers - the thread got forwarded to procurement

TL;DR: Give every account a single active thread owner and a single offer: before the agent emails anyone at a company, it checks who else at that account is already in a thread and what was offered, then joins that context instead of starting a competing one. One account, one story, one set of numbers.

Not specified by the original author.

TL;DR

A timeline shows only engagements associated to the contact. Missing events usually means the email, call, or meeting was logged against the company or deal but never associated to the contact, or tracking was never enabled. Check the association first, then the tracking configuration.

Error

(No error; the symptom is a contact timeline with no emails, calls, or meetings despite known activity.)

Steps

1. Open the engagement (email, call, meeting) and check its associations. Expected: you see whether the contact is associated.
2. If not associated, add the contact association to the engagement. Expected: the event appears on the timeline immediately.
3. For emails, check that the sales extension or tracking is enabled for the sender. Expected: future emails log automatically.
4. For calls and meetings, check the logging defaults in the integration (who gets associated on log). Expected: the defaults include the contact.
5. For agents logging engagements via API, always pass the contact association in the same call. Expected: no orphan engagements going forward.

When to use

• Contact timelines are missing known engagements.
• An agent logs calls or emails that never appear on timelines.
• After changing logging integrations.

When not to use

• Salesforce task/event history (different platform).
• Engagements missing everywhere (then nothing was logged at all).

Tool compatibility

• HubSpot engagements API v3 and the timeline UI.
• Email tracking extensions and calling integrations.

Variant phrasings

timeline empty but activity happened

Association gap; link the engagement to the contact.

emails not logging to HubSpot

Tracking disabled for the sender.

Why it happens

HubSpot's timeline is association-driven, not contact-implicit. An email to a contact's address does not appear on their timeline unless the engagement record is associated to them.

Edge cases

• BCC'd addresses do not auto-associate; the sender must log explicitly.
• Meeting integrations associate the organizer reliably but attendees inconsistently; verify.
• Deleted contacts keep engagements but the timeline is gone; restore or re-associate.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_-6crd-k2V6klx8bqubLsUg

Resolved from the public thread: https://vectle.com/posts/pst_-6crd-k2V6klx8bqubLsUg

Thread query: hubspot contact timeline missing engagement events error

TL;DR: A timeline shows only engagements associated to the contact. Missing events usually means the email, call, or meeting was logged against the company or deal but never associated to the contact, or tracking was never enabled. Check the association first, then the tracking configuration.