Asante Bot

Methodology

Where our numbers come from

We make specific claims on this site — about how many people use Asante, how fast you can launch it, and what recognition does to retention. Here's exactly how we measure each one, what we exclude, and when we last verified the number. No PR spin.

Active users

12,000+

As of Q2 2026

12,000+ people actually use Asante — not just install it and forget.

What it means. An active user is anyone who has sent, received, or reacted to a recognition message in the trailing 90 days, inside a Slack workspace where Asante is installed.

How we measure it. We pull the number from the same query our finance team uses during SOC 2 audits — distinct Slack user IDs with at least one recognition event in the rolling 90-day window. We always round down to the nearest thousand, never up.

What we don't count

  • Workspaces that installed Asante but never sent a recognition message.
  • Slack bots, service accounts, and workflow integrations that fire automated messages.
  • Trial workspaces that uninstalled before converting to a paid plan.

Countries

25+

As of Q2 2026

Teams in more than 25 countries run their recognition culture through Asante.

What it means. We count the distinct country listed in each paying workspace's billing record. A workspace with employees scattered across the globe still counts as one country — whichever country pays the invoice.

How we measure it. Pulled from our billing system (Stripe), de-duplicated, and cross-checked against our customer success accounts list. The count moves slowly — once a quarter we re-verify.

What we don't count

  • Trial workspaces and free-plan teams (they often span more countries, but we only count paid usage so the number stays defensible).
  • Customer subsidiaries billed under a single parent — they count as one country, not many.

Emoji points given

1M+

As of June 2026

Over 1 million Emoji points exchanged inside Slack to date.

What it means. A cumulative count of every recognition message processed by Asante since launch — every 🏆, 🌮, 🍕, ⭐, or whatever emoji your team has set as its recognition trigger.

How we measure it. Tallied from our recognition event log. Counts grew steadily from the first install in 2019 and now climbs by ~50,000 per month across all workspaces.

What we don't count

  • Test messages from our QA and integration sandboxes (we filter those out at the source).
  • Recognition messages that failed to post due to Slack rate limits or workspace permission errors.
  • Edits and deletions — once a recognition message is sent, it's counted, even if the user later removed it.

Average customer rating

4.8 / 5

As of June 2026

Asante averages 4.8 out of 5 across third-party review sites.

What it means. The weighted average of every rating left by a verified customer on the major B2B review platforms — Slack App Directory, G2, and our in-app NPS prompt.

How we measure it. We re-pull review data quarterly using each platform's public API or scraping fallback, weight each source by review volume, and round to one decimal place.

What we don't count

  • Internal employee accounts (anyone with an asante.com email).
  • Reviews older than 24 months — we drop them so the average reflects current product quality.
  • Anonymous reviews flagged by the platform as low-quality or removed.

Verify on the Slack App Directory

Median setup time

< 2 min

As of Q2 2026

Most admins go from 'never heard of Asante' to live recognition in under two minutes.

What it means. Median elapsed time from the click on 'Add to Slack' until the first recognition message is sent in a brand-new workspace. The 50th-percentile install, not an aspirational claim.

How we measure it. Computed from server-side install events. For every install in the trailing 90 days, we measure (first-recognition-sent timestamp) − (oauth-success timestamp). We report the median; the 90th percentile is about 8 minutes.

What we don't count

  • Installs that never produced a first recognition — those teams are tracked separately and follow-up emailed.
  • Customers migrating from a legacy bot that imports historical recognition data on day one (their setup is technically longer because of the migration step).

Lower turnover with active recognition

~30%

Teams with active recognition see roughly 30% lower voluntary turnover.

What it means. A conservative estimate of how much recognition culture reduces voluntary attrition — based on third-party research, not internal customer data.

How we measure it. Gallup's 2020–2023 engagement studies put the gap between highly-engaged and disengaged teams at 18–43% in voluntary turnover. We anchor our public number at 30% — the middle of that range — and avoid the higher end on purpose.

What we don't count

  • Industry effects (some industries see bigger reductions than others).
  • Causality claims — recognition correlates strongly with retention, but no single intervention causes a 30% drop on its own.
  • Involuntary turnover. We model voluntary quits only.

Plug your own numbers into the calculator

Transparency

What we don't measure

Three categories of data we deliberately don't track or publish — even when they'd flatter the numbers.

  • Message content

    We never store the body of a recognition message in plain text for analytics. AI Insights runs classification at write-time; the prose itself is hashed and discarded.

  • Cross-workspace identity

    If the same person uses Asante in two workspaces, we count them twice. We will not join identities across customer workspaces — even if we technically could.

  • Customer-level case studies in our averages

    One enthusiastic customer can skew an aggregate metric. We report medians, not means, wherever a single workspace could tilt the result.

Comparisons

When we compare Asante to competitors

The rules we follow before we name a name.

  1. 1 — Public pricing only. If a competitor doesn't publish prices, we don't guess. We compare list price to list price as of the same calendar quarter.
  2. 2 — Apples to apples on features. We compare the plan that includes the same feature set as the Asante plan we're benchmarking — not a heavily-stripped tier chosen to make us look cheap.
  3. 3 — We re-verify every quarter. Competitor pricing changes. Any comparison shown on our site carries the calendar quarter it was sourced from. If you spot a stale comparison, tell us and we'll fix it.

Questions

Methodology FAQ

The questions we get from analysts, journalists, and prospects evaluating Asante's claims.

Why publish a methodology page at all?
Because marketing metrics get misused. We'd rather show our work — the queries we run, the data we exclude, the dates we last verified — so anyone evaluating Asante can decide for themselves whether the numbers hold up. If a claim ever drifts from this page, that's a bug we want to fix.
How often do you update these numbers?
Quarterly. Every metric above carries an 'as of' date, and the page footer shows when the page itself was last reviewed top to bottom. If we change a definition mid-quarter, we note it in the changelog.
Do you ever count the same person twice across metrics?
Yes, and deliberately. A single Slack user can be one of the 12,000+ active users, sit in a workspace counted as one of the 25+ countries, and contribute to the 1M+ Emoji points total. Each metric measures something different — they don't add up to a single grand total.
Where does the turnover claim come from?
Gallup's engagement research, not our internal data. Internal customer outcomes vary too much by industry and team size for us to publish a single number honestly. The 30% figure is the middle of Gallup's 18–43% range, and we cite it as 'roughly' on purpose.
Will you share the raw data?
We can't share customer-level data — it's their data, not ours. But for analysts and journalists writing about employee recognition, we're happy to walk through the underlying queries on a call.
What if I notice a claim on your site that isn't covered here?
Email us — [email protected] or the contact form. If a metric appears anywhere on the marketing site, it should be defined here. Anything missing is an oversight we want to fix.

Page last reviewed top to bottom on . Spot something stale? Email us and we'll patch it.