The category
A phone system, not a contact centre.
The difference is not company size and it is not vocabulary. A contact centre is organised around a workforce: people whose whole day is the queue, and a plan for how many of them are on it at four in the afternoon. A phone system is organised around the number: it rings, and something has to decide who picks it up.
Ringfully is the second kind, for the case where one number is answered by more than one team. Sales, support and billing behind a single published line, hours that differ between them, and the person who answers has other work to do the rest of the day. Everything below follows from that, including the parts this product deliberately leaves out.
What it buys is one path through a call that you can read end to end. A number is bound to a flow. The flow decides everything, including whether you are open. It hands the call to a named queue. Somebody answers, in a browser tab or in the Windows desktop application, and the call is written down behind them.
Drawn the way the editor draws it, with the editor’s own block names. Publishing freezes a version, and a call already in progress finishes on the one it started with.
The four parts
Four ways in.
One page each, in roughly the order a call meets them. Every specific on them traces to a file, which is also why none of them lists a feature twice under two names.
Flows
Call flows
The visual editor behind every inbound number: 28 block types, 3 kinds of flow, 6 templates to start from. Your opening hours live in here, which is why a caller at nine in the evening never reaches a queue at all.
Queues
Queues and routing
Sales, Support and Billing are queues you name and give rules to: a priority, and a skill an agent has to have. Who gets offered a waiting call follows from which queues they are in and what they are set up to handle, and the caller hears whatever you decided they should hear meanwhile.
Calls
Calls, transfers and recording
Every answered call is bridged into a conference the moment somebody picks up. That is why hold, a blind transfer, a consult transfer where you stay on to introduce the caller, merging all three of you and dropping one participant are one mechanism rather than four bolted together.
Access
Access and roles
34 permissions in 7 groups: calls, contacts, messaging, voicemail, people, the organization itself, emergency calling. Three system roles that cannot be edited, and roles of your own written from the same list.
Read this first
What happens during one call.
The four pages above are the parts. That one is the thread: a single call from the ring to the record that closes behind it, in the order the decisions are actually made. The order is the part that is hard to convey any other way: your hours are checked inside the flow, before a task exists, so a caller at nine in the evening hears your closed message instead of waiting in a queue nobody is watching until it times out.
It is the better page to start with if you are still deciding whether the shape of this fits the problem you have.
What it does not do.
There are two ways for a person to answer a call, and that is the whole list: a softphone in a web browser, and a Windows desktop application. They have the same controls because underneath they are the same call engine. There is nothing to install on a phone, and there is no Mac build.
People sign in with an address and a password kept here. There is nothing to wire into whatever your company already uses for logins, so an account on Ringfully is one you create and remove on Ringfully.
What a flow can do mid-call is reach your systems: an outbound request into an address of yours, made while the caller is still on the line, through a per-organization allowlist that refuses by default. Nothing leaves here for a host an administrator has not put on that list by hand.
And there is no form that turns into a working phone system. Numbers, hours and routing are set up with you before anybody uses them, because a business-hours rule pointing the wrong way sends every caller to voicemail and no signup screen would have caught it.
Each of those is asked often enough to have its own answer on the questions page, in the same plain terms. If one of them is a hard requirement, say which in the first email and I will tell you whether to wait for us or go elsewhere.