Measuring impact
What Rendel did for your users this month, counted, and what that is worth, estimated from your own numbers or cited averages.
Analytics opens on Value: what Rendel did for your users this month, and what that is likely worth. Months are UTC calendar months, compared with the same days of the month before. The previous page is the Operations tab, with its 7, 30 and 90-day windows.
The page keeps two bands apart. What happened is counted. What it's worth is an estimate, and always says so.
What happened (counted)
- Tasks done: actions that succeeded and are marked completes a task. By default that is every
writeanddestructiveaction; change it per action in Settings → Value, where an action can also be marked opens a flow or a goal. - Resolved: conversations that closed after Rendel answered from your knowledge or your actions, or completed a task, with no handoff to a person, no request left unmet, no thumbs-down and no failed action left unfixed. Answers from the model alone count as unverified, and small talk is left out. Beside the rate: how many came back within 48 hours, and whether your app lists contact channels.
- Goals reached, adoption (devices that started a conversation, out of those that ran the SDK on a live key), screens opened, the grounded share of answers, and ratings, with the response rate beside them.
Each figure follows a versioned rule, and the charts mark when a rule changes.
What it's worth (estimated)
- Support contacts avoided = resolved conversations × the share that would otherwise have reached your support team.
- Support cost avoided = those contacts × your cost per assisted contact.
- Staff hours: the same contacts in hours, shown for scale and never added to the total, because the cost per contact already counts that time.
- App cost: your plan's fee and the usage you were charged, split across your apps by their share of usage. Pilot and test keys cost nothing.
- Value for cost: support cost avoided against app cost. There is none when cost is zero or the two are in different currencies; then they stand side by side.
Every worth figure is marked estimated, and while any of the four inputs is still a default, a banner says how many are not yours yet.
Your inputs
Settings → Value holds the industry, the currency (USD, EUR or TRY) and four inputs. Owners and admins can change them, and every change is in the audit log.
| Input | Default | Where it comes from |
|---|---|---|
| Cost per assisted contact | $8.01 | Gartner's figure for live channels (phone, chat, email), the same for every industry |
| Staff cost per hour | $45.65, or €33.5 | US Bureau of Labor Statistics (private industry); Eurostat (EU whole economy) |
| Minutes per contact | Set yours | No primary source we could confirm |
| Share of resolved conversations that would have reached support | 20% | Rendel's starting point, not an industry figure. Set it low on purpose, and the first to replace with yours |
Each default is labelled with its source on the page. A default we could not confirm against its primary publication is not shown; the input reads Set yours instead, as do the Turkish lira inputs for now.
Sharing it
- Share links: off for each organization until an owner turns them on in Settings → Value. An owner makes one with Share this month on the Value tab (live key only). The link (
/r/…) shows that month as it was, with its inputs and their sources, and no conversation text or names. It expires after 90 days, can be revoked at any time, and prints to PDF. - Monthly email: on the 3rd, to owners, for live apps, with the month's measured figures.
How to read it
The counted figures are what happened. The estimates are only as good as the inputs: replace the defaults with your own numbers before you quote the value to anyone, and quote it as an estimate.