Deal Contacted and Activity Count Bridge

Explain why a deal has more sales activities than contact events. Preparation only, not an account action.

What to provide

Deal/activity IDs, activity types, association scope, both count exports and capture times.

How it works

1. Classify supplied activity types using the documented property definitions.
2. Keep notes and tasks in sales activities but out of times-contacted counts.
3. Deduplicate IDs within the supplied scope.
4. Return a count bridge without claiming each contact reached a buyer.

The output

deal | sales_activities | contact_events | notes_tasks | export_scope | gap

Worked fictional example

Fictional two calls, one email, three notes and two tasks yield 8 sales activities and 3 contact events in complete supplied scope. Three contact events do not prove three unique people.

Checks and limits

Keep source versions and original values. Unknowns stay unknown. Use qualified review for regulated, legal or hiring decisions. No live account compatibility test, send, share, schedule, ledger change or payment is authorized.

More sales workflows · How-to guides

Method: reviewed source. Demand lead: Oct12 live AIS Search Console: marketing Copilot37 impressions, Planable/Claude38, Planable/ChatGPT24, campaignbrief12, investoragent19, MuseIndia100. Social calendar/reporting topics follow parent-query leads; other professions follow documented workflow needs, not measured exact intent. Site impressions are not monthly volumes; exact topic volume is unmeasured. Checked October 12, 2026.