Trackers help you monitor what comes up across meetings: topics, keywords, themes, competitors, product feedback, objections, risks, or moments a user manually marks as important.
A tracker creates captures: meeting-level snippets with counts, timing context, and optional capture output instructions. Those captures become a focused corpus that agents can analyze later.
When to use trackers
Use trackers when you want to answer questions like:
- Which meetings mentioned a competitor?
- Where are buyers asking about a particular feature?
- How often do security, pricing, implementation, or legal review come up?
- Which calls should a product marketer or product manager review?
- Which calls did reps manually mark as containing a notable objection, win theme, or risk?
Trackers are different from scorecards. A scorecard evaluates how well a meeting was run. A tracker detects that a topic appeared. Trackers are also different from frameworks, which maintain a structured deal-level view over time.
Tracker types
| Type | Use it for | Best examples |
|---|---|---|
| Keyword tracker | Exact words or phrases that should be detected reliably. | Competitor names, product names, compliance acronyms, pricing terms, specific integrations. |
| Concept tracker | Ideas that can be expressed in many different ways. | Security concerns, budget pressure, implementation risk, expansion intent, product feedback, buyer confusion. |
| Manual tracker | Moments a user should intentionally tag from a meeting session. | Manager review, notable objection, strong discovery moment, product team follow-up, customer story candidate. |
Keyword trackers
Keyword trackers are best when the exact wording matters. Use them for proper nouns, product names, short phrases, acronyms, or terminology that is unlikely to be paraphrased.
Example setup:
- Name: Competitor names mentioned
- Type: Keyword tracker
- Keywords: AcmePOS, NovaPay, StoreGrid
- Use case: Find meetings where specific competitors were named.
Concept trackers
Concept trackers are best when people may describe the same idea in different words. Instead of only matching exact phrases, Bigmind uses examples and descriptions to detect the underlying topic.
Example setup:
- Name: Implementation risk
- Type: Concept tracker
- Description: Captures moments where a buyer expresses concern about rollout effort, migration complexity, internal resources, training, or time to go live.
- Example conversations: “We do not have an admin who can manage the rollout”, “Migration would be hard before our busy season”, “Training every location is a concern”.
Capture output instructions
For concept trackers, you can tell Bigmind how each capture should be formatted. This is useful when you want the capture itself to include structured evidence that an agent can later summarize.
Example capture output instructions:
Use concise markdown.
- **Theme:**
- **Impact:**
- **Urgency:**
- **Evidence:**Keep capture output instructions focused on the single meeting capture. Do not ask the tracker to produce an aggregate report, grouped table, or trend analysis. Do that later in chat using the tracked meetings as the source corpus.
Manual trackers
Manual trackers are for human judgment. They do not run automatically. A user adds a manual tracker from a meeting session when they decide a call should be associated with that tracker.
Example setup:
- Name: Product team review
- Type: Manual tracker
- Use case: Reps or managers manually mark calls that product managers should review.
Scope and permissions
Trackers can be scoped so captures only come from the right meetings:
- Mentioned by: choose whether the topic can be mentioned by anyone, only internal participants, or only external participants.
- Limit to meetings from: restrict the tracker to meetings owned by selected users or teams.
- Access control: users only see tracked meetings they have permission to access.
Apply trackers to previous meetings
For keyword and concept trackers, you can analyze previous meetings over a bounded date range. This is useful when you create a new tracker and want to backfill recent calls.
Manual trackers are not applied automatically. They are added by users from the meeting session.
What trackers unlock
Once a tracker has captures, you can ask an agent to analyze the tracked meetings. Examples:
- “Summarize the most common objections in meetings tracked by Implementation risk.”
- “Find product feedback patterns from meetings tracked by Feature requests.”
- “Create a table of competitor mentions from meetings tracked by Competitor names mentioned, with source meetings and snippets.”
- “Compare this month’s security concern captures against last month.”
The tracker narrows the corpus. The agent does the aggregation, grouping, and reporting.
Best practices
- Choose keyword when exact wording matters. Use concept when the same idea can be phrased many ways.
- Keep concept examples realistic. Add examples that sound like real customer language.
- Use capture output instructions for structured snippets. Markdown bullets are often easiest to scan.
- Scope trackers carefully. Meeting owner and speaker filters prevent noisy captures.
- Do reporting in chat. Trackers create evidence; agents summarize and group it.
See how trackers fit with other coaching concepts: Concepts.