~950 ms
One team's dashboards said the agent was fast. Callers heard about 950 ms of delay on every turn.
Open source
any voice stack
Know what your callers actually hear.
Ring calls your voice agent over the real phone network every few minutes and alerts you when it is slow, silent or broken.
Probe recording · two channels
FAIL
greeting2,760 ms
response2,180 ms
Your dashboards are not your callers.
0 audio
A freelancer who fixes production agents keeps finding SIP trunks lost after a restart, and greetings that play before the audio is connected.
7 s
Another team's agent took 7 seconds to say hello: 7 seconds of silence at the start of every call.
Who it’s for
Any team with a voice agent answering real phone calls.
Vapi, Retell, LiveKit or Pipecat
Ring calls your number over the real phone network, so it works whatever runs behind it.
You cannot call every agent every morning
One probe per client agent, an alert when one is slow or silent, and a status page to show them.
The dashboards say it is fine
Measure what a caller actually hears, time to greeting and time to answer, from outside.
What it does
We call your agent like a customer would.
A real phone call from a Twilio number, on a schedule. It listens, asks one question and hangs up. Vapi, Retell, LiveKit, Pipecat or your own stack: if it has a number, it works.
We measure the recording, not your logs.
Greeting latency, response latency, dead air, talk-over, a silent agent, a clipped greeting. Optionally, a transcript checked against the phrases you expect.
You get one alert, not a hundred.
Slack when a probe starts failing, when the problem changes and when it recovers. A status page with p50/p95 latency and history.
Try it in two minutes, no accounts
Terminal: ring demo
# synthetic calls with known latencies, then the status page pip install macomore-ring ring demo ring analyze ring-demo/bookings-latest.wav greeting 2760 ms after answer, lasts 1820 ms response 1 2180 ms after our prompt ended result FAIL - [slow_response] agent answered after 2180 ms (limit 2000 ms) ring serve # http://127.0.0.1:8707 # then point it at your real agent (bring your Twilio account) ring watch --every 15m
Each probe is a real call: about a minute of phone time plus a minute of your agent's own time.
Pricing (provisional)
Open source
$0- Run it yourself
- Bring your Twilio account
- Slack alerts, status page
Hosted
$49/mo- 1 agent
- Probe every 15 min
- We run it for you
Team
$149/mo- 5 agents
- Probe every 15 min
Agency
$299/mo- 20 agents
- For agencies running many clients' agents
Each probe uses about 30 seconds of your agent and phone time: one probe every 15 minutes is about 2,880 probes per agent a month. Phone minutes are paid by the caller and are not included. The hosted plans are not live yet: join the waitlist.
Get early access to the hosted version
We only use your email to contact you about this. Privacy.