Demo
No calendar widget. Two ways to actually see it.
We do not have a sales team to book you into, and a polished demo video on someone else's data would tell you nothing about your own traffic. So: connect a real source on the trial, or ask for a walkthrough and we will go through it with your setup on screen.
Your calls, or your setup on screen.
Route one
Start the trial, connect a real source
14 days on Scale, no card. The point is to run your own calls through it, because the only question that matters is whether our numbers survive contact with your call platform.
- Create the workspace. Email and a password. No onboarding call, no scheduling step.
- Connect your source. Read-only API credentials. We never route calls, so nothing in your ring tree changes.
- Let a week of calls sync. Historical calls land first so you have something to argue with immediately.
- Check us against your platform. Open the revenue figure, drill to the raw rows, compare. If it does not reconcile, that is the bug report we most want.
- Read the dispute queue. Calls we think were wrongly disqualified, with the transcript excerpt and timestamp attached.
No card, no contract, no setup fee. Full export from day one.
Route two
Ask for a walkthrough
Send a note on the product route with your call platform, rough monthly volume and verticals. We will not promise a response time we cannot yet keep, and we are not going to pretend a calendar link exists. A walkthrough covers:
- Whether your data supports itAre calls recorded, are payouts populated, are publisher and target tags set. If the answer is no, you find out before the trial rather than on day nine.
- How we count revenue against your platformWhich field we treat as revenue, how duplicates are excluded, and why a small variance is expected rather than hidden.
- The dispute queue on real examplesWhat a recommendation looks like, what evidence gets attached, and what we would not contest.
- API and MCPIf you would rather not open a dashboard, we will show you the query path instead.
- Whether it pays for itselfYour volume, payout and dispute rate against the subscription. Sometimes the honest answer is not yet.
Connection status changes. Ringba and Search Console are in build, CSV, Sheets, Slack and CallRail are planned. The changelog is dated and is the honest answer to what is live on the day you read this.
What a connected workspace shows.
Below is a made-up example built to show the shape of the output. It is not a customer, not a screenshot, and not our own data. Read it for structure, not for numbers.
| Time | Publisher | Target | Dur | Payout | Label | Flag |
|---|---|---|---|---|---|---|
| 09:14 | pub-014 | Roofing desk A | 2:41 | $86.00 | Qualified. Storm damage, homeowner, insured | — |
| 09:31 | pub-022 | Roofing desk A | 0:52 | $0.00 | Sub-60. Caller asked for a competitor by name | — |
| 10:02 | pub-007 | Water damage B | 3:18 | $122.00 | Qualified. Burst pipe, standing water, carrier named | — |
| 10:19 | pub-022 | Roofing desk A | 1:44 | $0.00 | Returned as wrong state. Caller gives an in-state ZIP at 0:38 | Dispute recommended |
| 11:05 | pub-014 | Water damage B | 0:38 | $0.00 | Voicemail. No human on the line | — |
| 11:40 | pub-031 | Roofing desk A | 2:05 | $86.00 | Qualified. Same caller as a call 26 days earlier | Check duplicate window |
Every label is traceable
The wrong-state row points at 0:38 in the transcript because that is where the caller said the ZIP. Labels link to the span that produced them, so a disagreement is settled by reading, not by trusting.
Aggregates drill down
RPC by publisher, target, vertical and hour, each opening the call rows behind it. In the example above, pub-022 is carrying two unbilled calls out of two. At real volume that is the pattern you are looking for.
Recommendations, not decisions
The queue proposes. You approve or dismiss, and the dismissals matter as much as the approvals. We do not file disputes on your behalf and we do not take a cut of what comes back.
No customer logos here, because we have no customers.
We launched in 2026. A demo page would normally carry a logo bar, a testimonial and a recorded walkthrough of an anonymised account. All three would be invented, and this audience checks. What we have instead is a published methodology, a dated changelog, an export button on every tier, and a trial that runs on your own calls.