Skip to main content
Insights roll every recorded meeting and captured lead into a picture of what your team is actually encountering in the field. It answers questions that are hard to get from a CRM: what objections keep coming up, which accounts have gone quiet, and who follows through on what they promised.
Insights are built from recorded meetings. A team that captures leads but never records conversations will see activity counts and little else. The richer views — topics, objections, sentiment — need transcripts to work from.

Reading the team's activity, then the meeting intelligence behind it

The Team Insights screen showing headline counts for leads, views, downloaded contacts, and active members, above a per-member activity table.

The top row is the whole team at a glance

The headline numbers

Leads and connections are counted separately. A lead is someone your team captured — through the capture form or the card scanner. A connection is a link between two Tap users who connected in the app. They used to share a count, which inflated both the totals and the acceptance rate; each connection is now counted once per relationship, and captured leads have their own number.Figures for periods before September 2026 were produced the old way, so a long comparison range can show a step change that is a counting fix rather than a drop in activity.
Below them, Members Activity breaks the same figures down per person and adds notes written, last mobile session, and last dashboard session — the fastest way to spot someone who has quietly stopped using the app. See Member activity. You can filter by department or member, and export the result. A separate Meeting intelligence tab covers what was said, rather than how much activity happened. If your company tracks a sales framework, it also shows which items your team finds out on new leads and which each rep skips most.

Notes

Two widgets read what your reps write and record on leads:
  • Notes — how many notes were written this month, and how many need attention. Each flagged note carries a reason: Unanswered (a note promised something and nothing has been logged since), Risk (several notes on one account say the deal is in trouble), or Competitor (a competitor is being named — see Competitors). See all lists every flagged note, and each flag opens the notes behind it.
  • Note themes — what the notes are about, grouped by meaning rather than keyword. Each bar is coloured by how the notes read: positive, neutral, or negative. Themes appear once there are enough notes in the period.
“Nothing flagged right now” is the normal state for a healthy team. See Notes for the notes themselves.

Lead quality

These cards show how your team answered the lead qualifiers:
  • Buying Role — how many decision makers you met, and the split across influencers, end users, gatekeepers, and leads marked not relevant.
  • New vs Current Business — how many leads are new, existing, or returning. If your company renamed the Relationship question or changed its answers, the card uses your name and your answers.
  • Your questions — if your company has added its own questions, pick one to see how leads answered it: “64% answered Yes”. For a multiple-choice question, a lead can count towards more than one answer.
Each card says how many leads were qualified out of the total. Leads where the rep skipped the question are counted as skipped, and leads captured before the question existed are counted as never asked. A question that was switched off when a lead was captured isn’t counted as skipped for that lead.

Field coverage

At the bottom of the default tab, a heat map of the areas your team recorded meetings in, beside a ranked list. Hover an area for its meetings, reps, and average lead score; click it to zoom in and filter the page to it. Only meetings recorded with location on are placed, and the header tells you the ratio so you know how much of the picture you’re looking at. Sales Intelligence and up, or Enterprise on older plans. See Field coverage.

Who can see insights

Team Insights is for your company’s admins.
Some sections also depend on your plan. On Cards and Lead Capture, Notes, Note themes, Competitors, Field coverage, and the Meeting intelligence tab aren’t shown — they start at Sales Intelligence. See Plans and limits.

Choosing a period

Every view is scoped to a date range, and each headline number is compared against the equivalent preceding period, so you see direction rather than just magnitude.
Compare like with like. A week containing a major conference against a quiet week tells you nothing except that conferences exist. For event-driven teams, compare this event to the last one rather than this month to last month.

What’s in each view

Members

Activity per person — leads captured, notes written, and when each member last used Tap.

Topics and objections

What conversations are actually about, and what’s standing in the way.

Action completion

Who closes the loop on what they promised, and who doesn’t.

Profile activity

Which profiles are being viewed and tapped — useful for judging whether a template change helped.

Notes

What your reps are writing and recording on leads, how many need attention, and the themes running through them.

Competitors

Which rivals your leads bring up, and whether they’re coming up more often than they used to.

Field coverage

Which areas your team actually covers, and which they never reach. Sales Intelligence and up.
The profile activity view showing views and taps per member profile.

Profile activity — which cards are actually being seen

Headline numbers

The overview leads with meeting volume over time, your most recent meetings, and the accounts appearing most often in conversations. Two views deserve particular attention:
  • Sentiment trends — how the tone of conversations is moving. A steady decline usually shows up here before it shows up in your pipeline.
  • At-risk accounts — accounts whose conversations have turned negative or gone quiet. This is the list worth reading every week.

Reading insights well

More meetings isn’t automatically better. Read volume alongside sentiment and follow-up completion — a rep doing half the meetings and closing every loop may be outperforming one doing twice as many badly.
A recurring objection is either a real product gap or a positioning failure. Either way it’s fixable, and it’s cheaper to fix once centrally than to let thirty reps improvise around it.
A topic appearing in three conversations is noise. Wait for enough volume before restructuring your pitch around a pattern.
Territories and events differ enormously. Someone working a quiet regional show can’t match someone at a flagship conference, and treating that as performance breeds gaming rather than improvement.