Your voice menu routes callers to the right option. But the option still needs to actually reach a person — on a phone, in the app, or on a specific team member's device. The Ring block is what makes that happen. This article explains how ringing works in Romulus and how to configure it so calls land exactly where you want them.

A call that reaches the right menu option but rings the wrong phone — or no phone at all — is just as useless as a call with no routing. Getting your ring configuration right means callers actually reach a person, not a dead end.

When a call hits a Ring block, Romulus simultaneously (or sequentially, depending on your configuration) tries to connect the call to one or more destinations. A destination can be:

If nobody answers within a set time limit (which you control), the call can automatically move to the next step — like voicemail, another ring destination, or your AI agent.

The full step-by-step guide is here:

👉 How to Make Calls Ring on My Phone

Add a Ring block to your inbound rules, select who receives the call, set the ring duration, and define what happens if no one answers.

Set a ring timeout. Always define how long the Ring block waits before moving on. If you leave this open-ended, a caller might ring indefinitely with no answer. 20–30 seconds is a reasonable default for most businesses.

Define what happens if no one answers. After the ring timeout, the call needs somewhere to go. Connect it to voicemail, your AI agent, or another team member — never leave it dangling.

Team members need the app installed and logged in. A Ring block can only reach a team member who has the Romulus app running on their device. If they're logged out, calls won't reach them regardless of the inbound rule configuration.

Now that calls can ring the right people, the next step is handling the calls that don't get answered — with voicemail.