Skip to main content
Once your line is live, the fastest way to know it’s working is to ring it yourself from another phone. The whole loop takes about five minutes and proves push notifications, voicemail recording, transcription, and auto-reply are firing end-to-end. If you don’t have a second phone handy, ask a colleague — the same test doubles as a chance to introduce them to Rivet.

​
Before you start

Two things should already be true:
  • The native app is installed on your phone and you’re signed in. Without the app, push notifications and the in-app incoming-call UI don’t have a destination. See Install the Rivet app.
  • The welcome screen has flipped your line to active. If you’re still seeing “Setting up your line …” wait the remaining 60-120 seconds — the line isn’t routable yet.
If both are true, your Rivet number is on the welcome screen and on your contact card; you can also find it any time under Settings → Phone.

​
The test loop

1

Pull your Rivet number

Welcome screen, Settings → Phone, or the practice line section in the inbox header — all three show the same +1 number.
2

From a different phone, dial it

The phone needs to be one not signed into your Rivet account. A colleague’s phone, your partner’s phone, your old line — anything that won’t be intercepted by the Rivet app routing to itself.
3

Expected: your phone rings via CallKit (iOS) or full-screen incoming-call UI (Android)

The OS treats it like a phone call from the system. The practice name shows as the caller (it’s actually the OTHER phone calling YOU, but the UI shape is “Rivet — incoming”).
4

Don't pick up. Let it go to voicemail

Your custom greeting plays if you’ve recorded one; otherwise the Rivet default greeting plays. Speak for 15-30 seconds on the caller side — long enough to test transcription.
5

Hang up. Expected, within 5-15 seconds:

  • A push notification lands on your Rivet phone — “New voicemail from the calling number”.
  • The inbox shows a new row with the voicemail at the top.
  • The transcription appears under the row within a few seconds of the recording finishing.
  • An auto-reply text is sent back to the calling number — check the calling phone’s SMS app to confirm.
6

Tap the inbox row → listen to the recording

Audio playback works; the transcription updates a few seconds after if it was still processing.
If all six expected outcomes fire, the line is working end-to-end.

​
What to do if a step doesn’t fire

Doesn’t happenLikely causeFix
Your phone doesn’t ringNotification permission offAllow notifications for Rivet in OS settings
Phone rings but no audio when you pick upMic permission off, or carrier audio routing quirkSettings → Apps → Rivet → Microphone; if the issue persists, see calls-not-coming-through
Voicemail recorded but no pushPush token not registered — re-open the Rivet app once after sign-inOpen the app, confirm the inbox loads, try again
Transcription stuck on “Transcribing…”Slow processing for very long messagesWait 60 seconds; if still stuck, the message is over 5 minutes — long messages process slower
No auto-reply textAuto-Reply switched off, or the caller number is a landlineSettings → Auto-Reply (master toggle); landlines can’t receive SMS — that’s expected

​
Why this matters

If your line ever stops working, this is the same loop you’ll run to diagnose it. Train your fingers on it now while there’s no pressure; the muscle memory carries over. A weekly run of this test (Monday morning takes 90 seconds) catches any silent breakage before a real client hits it.

Install the Rivet app

The native phone app is what rings.

How voicemail works

The full lifecycle of an incoming voicemail.

Auto-reply explained

What the caller sees within seconds of leaving a voicemail.

Calls not coming through

Push permission, Do Not Disturb, weak network at the call window.