Download websites that use Ruby Receptionists

About Ruby Receptionists

The thing being detected here is not really software. Ruby sells live answering, which means trained people picking up calls and chats for businesses that would rather not staff a front desk. Software appears only at the edge of the arrangement, as a chat widget on the client website and as the routing that carries a message to the right person. A technology index picks up the widget and files the whole service under Widgets.

Which makes a detection unusually informative about the business rather than about the stack. A company paying for outsourced reception has customers who telephone, cares about catching a call it would otherwise miss, and is small enough not to employ a receptionist yet large enough to feel the loss. Law firms, clinics, contractors, agencies and property businesses fit that shape. Very few purely online businesses do.

For anyone selling into professional services, the shape is the whole point. The detected domains are not a technology segment. The detected domains are a behavioural segment, identified by an operational choice a company made about how it handles inbound contact, which qualifies a prospect far better than an industry code or a headcount band.

Ruby has been running the service since 2003 and sells it as Proprietary. Longevity of that order means a client base that turns over, so a widget present on a site today is evidence of a current relationship rather than a historical one. Measuring a hosted script instead of reading a published case study page is a real advantage in a market where the case studies never get taken down.

The count deserves candour. As of October 2026 the fingerprint stands at 1 in our index. Small business websites are a hard population for any crawl to cover completely, because the businesses are numerous, their domains are unremarkable, and the widget is frequently loaded through a script the page fetches later. A conversational widget that appears only after a delay, or only once a visitor interacts with the page, can be absent from the served HTML that detection reads.

So the export should be treated as a starting set rather than a client list. What the list does that a per-domain lookup cannot is hand you the population at once, with every domain's other technology attached, so an answering service widget can be crossed against content system, region, top level domain and the absence of ecommerce to isolate the segment you actually wanted. Checking one law firm website tells you about one law firm. A list built the same way at every refresh tells you who adopted, who dropped, and what else changed on the site when they did.