Quick answer
RingCentral's AI receptionist sits inside a full UCaaS platform, priced per seat from roughly £150 to £500+ per month with US-led support, sensible only if you already use their unified communications stack. For most UK service businesses, a custom-built AI receptionist (the kind ORYX builds) is the better fit: trained on your actual call patterns, FAQ, and qualification rules, with UK-based setup, CRM integration, and a £200/month usage-based entry point. No seat licences, no platform lock-in, no per-minute meter, just a focused answering agent tuned to your business.
What is the RingCentral AI receptionist and how does it actually work?
RingCentral's AI receptionist is a feature inside its Unified Communications as a Service (UCaaS) platform, not a standalone product. You buy a RingCentral business phone plan, which bundles calling, messaging, video, and contact-centre tools, and the AI receptionist layer sits on top of that stack. The AI itself runs through RingCX, RingCentral's contact-centre product.
RingCentral describes RingCX as "an AI-first contact centre that's easy to use, quick to deploy and offers great value" on its UK product page. In practice, the AI greets inbound callers, asks scripted intake questions, routes calls based on intent, and handles a defined set of FAQs before escalating to a human agent (if you have human agents on the platform).
The architecture matters because RingCentral provisions everything per user. The UK pricing page states "Pricing shown per user per month, billed annually". Each licensed user gets a seat, even if only one person actually needs the AI receptionist. The AI is not metered by usage; it is bundled with the seat licences you already pay for.
What you get is breadth. You get a single platform for telephony, video, messaging, contact centre, and AI-assisted call handling. What you do not get is a receptionist tuned to your specific business. The AI works from generic intent classifiers and templated intake flows, not from your booking calendar, your service price list, or the qualification questions a senior salesperson would actually ask.
For a multi-site enterprise running RingCentral company-wide, this is fine. For a UK plumbing firm, dental practice, or law firm with one number and a clear set of FAQs, it is heavier than the job requires, and the per-seat licensing punishes small headcounts.
How does a custom-built AI receptionist differ from RingCentral's?
A custom-built AI receptionist is purpose-trained on one business's call data, not configured from a platform-wide template. Where RingCentral gives you a generic intake bot inside a UCaaS suite, a custom build is a focused single-purpose agent that knows your services, your prices, your booking rules, and your escalation paths from day one.
The training process is the difference. ORYX builds start with a discovery phase: real call recordings, the FAQ list your team answers daily, the qualification questions that separate a genuine lead from a tyre-kicker, and the after-hours rules that decide what counts as urgent. Those inputs get baked into the agent so it answers questions the way a senior team member would, not the way a templated intake script would.
CRM integration follows the same logic. A custom build connects to whatever you already use (HubSpot, Pipedrive, Salesforce, Jobber, ServiceTitan) and writes a structured lead record after each call, with the qualification answers captured as named fields. RingCentral integrates with CRMs at the platform level, but the data captured is whatever the generic flow asked, not the fields your sales process actually needs.
The strategic case for the focused approach is large. Gartner forecasts that "by 2026, conversational AI deployments within contact centres will reduce agent labour costs by $80 billion" globally. That saving only materialises when the AI actually handles the call rather than punting straight to a human; that, in turn, only happens when the AI has been trained on your specific call patterns rather than a generic template.
Setup time is longer than flipping a platform toggle: a custom build typically runs 2 to 3 weeks of training, supervised pilots, and CRM wiring. The payoff is an agent that converts inbound calls into qualified bookings, not a feature buried inside a phone system.
How do the costs compare: RingCentral seat pricing vs ORYX usage-based £200/month
RingCentral costs £150 to £500+ per month once contact-centre licensing is layered on, billed per seat; a custom-built ORYX AI receptionist starts at £200 per month on usage-based billing, with no seat fees. The pricing models are structurally different, which matters more than the headline numbers. RingCentral's UK pricing page confirms "Pricing shown per user per month, billed annually". The published phone plans run roughly £15 to £40 per user per month for the core tiers, and the contact-centre tier with RingCX-level AI sits considerably higher. For a small UK service business with 5 to 10 internal users plus the AI receptionist feature, the total annual commitment lands at the upper end of that range.
A custom-built AI receptionist starts at £200 per month with usage-based billing. There are no seat licences, because the AI is the receptionist, not a feature distributed across staff seats. You pay for the agent and the call volume it handles, not for every person in the business who has a phone.
Two other options are worth naming, both in compare-and-win terms. Smith.ai bills per minute, with US pricing from around $255 per month for 100 minutes and per-minute charges beyond that; for a UK service business with unpredictable call volume, the per-minute meter creates billing anxiety, and the ORYX build has no per-minute meter. Moneypenny runs a UK-based human-led model with AI assist; the human element pushes monthly costs higher and adds queue time during peak hours, where a custom AI answers instantly on every call.
The in-house alternative is more expensive again. A full-time UK receptionist salary sits around £24,000 to £28,000 per year (roughly £2,000 to £2,300 per month) before employer NI, pension, holiday cover, and training, which is around ten times the £200/month entry point for a custom AI receptionist, and that one person only covers a single shift.
The cost of doing nothing is also real. BT Business research finds that "85% of people who can't reach a business on the first call won't call back". At an average UK service-business job value of £200 to £2,000, a £200/month custom receptionist pays for itself with a single recovered missed call per week.
Which option fits UK service businesses best for compliance and support?
UK GDPR governs every inbound call your AI receptionist handles, regardless of which vendor you pick. The ICO states that "personal data shall be processed lawfully, fairly and in a transparent manner in relation to the data subject". Callers must be told the call is being handled by an AI, what data is captured, and how it is stored.
The legal split is also clear. The ICO defines that "a controller determines the purposes and means of processing personal data. A processor is responsible for processing personal data on behalf of a controller". Your business is the controller. Your AI receptionist vendor is the processor. The data processing agreement between you must reflect that, and the call data must sit in jurisdictions you can defend under UK law.
Ofcom regulates the telephony layer. As the regulator describes its remit: "We are the UK's communications regulator. We regulate the TV, radio and video-on-demand sectors, fixed line telecoms, mobiles, postal services, plus the airwaves over which wireless devices operate." Any AI receptionist deployed on a UK number must respect Ofcom rules on call routing, recording disclosure, and number portability. Regulated sectors add another layer: FCA-supervised firms have specific call-handling and record-keeping duties, and BSI standards apply where information security is in scope.
This is where vendor location starts to matter. RingCentral is a US-headquartered platform with US-led support; data processing arrangements are workable but require careful contract review against UK GDPR. A UK-built custom receptionist sits on UK or EU infrastructure by default, with a data processing agreement written against UK GDPR rather than ported from a US template, and with support hours that match UK business hours.
The addressable picture is large: the Department for Business and Trade reports that "there were 5.5 million private sector businesses in the UK at the start of 2024", with small businesses accounting for 99.2% of them. Most of that population is the natural buyer for a UK-tuned, UK-supported AI receptionist rather than an enterprise UCaaS subscription.
When does RingCentral genuinely win, and when should you go custom?
RingCentral wins when you are already a RingCentral customer. If the business runs on its UCaaS stack across multiple sites, with a dedicated IT team managing the platform, adding the AI receptionist as another module is the path of least resistance. Multi-site enterprises with 50+ seats, regulated contact centres that need workforce management alongside AI, and businesses with existing RingCX deployments should stay on RingCentral.
A custom build wins everywhere else. For UK service businesses with one main number, a defined service catalogue, and a clear set of qualification questions, a focused build outperforms a platform feature on three dimensions: it answers in your voice, it captures the data your sales process needs, and it costs less than the platform minimum.
Speed of answer matters as well. Salesforce-aligned customer research finds that "60% of customers will hang up after being on hold for one minute". Both RingCentral AI and a custom build can answer instantly; the question is whether the answer is useful. A generic intake bot that asks "press 1 for sales" loses callers faster than a tuned agent that says "I can book your boiler service now, what postcode are you in?".
The scale of the underlying market backs the custom case. The Department for Business and Trade reports that "total employment in SMEs was 16.6 million (61% of the total), with a turnover of £2.8 trillion (53% of the total)". Most of those inbound calls are to small UK service businesses that do not need a 50-feature unified communications platform. They need an answering agent that books work.
If the decision comes down to "do we already use RingCentral?", answer that first. If the answer is no, a custom build is the cheaper, faster, more focused option.
Book a 20-minute discovery call to see how a custom AI receptionist would handle your specific call patterns. ORYX maps your top inbound questions, your qualification rules, and your CRM setup, then quotes a fixed monthly figure starting at £200 with no seat licences and no per-minute meter. See the AI receptionist service page for the full build process and recent UK client examples.
Book a 20-minute discovery call to see how a custom AI receptionist would handle your specific call patterns. ORYX maps your top inbound questions, your qualification rules, and your CRM setup, then quotes a fixed monthly figure starting at £200 with no seat licences and no per-minute meter. See the AI receptionist service page at /services/ai-receptionists for the full build process and recent UK client examples.
Frequently Asked Questions
Is RingCentral's AI receptionist available as a standalone product in the UK?
No. RingCentral sells its AI receptionist capability inside its wider UCaaS and contact-centre platform, with per-seat pricing rather than as a standalone receptionist add-on. The RingCX product that powers the AI layer is positioned as an AI-first contact centre, not a single-purpose answering agent. UK service businesses that want a standalone receptionist typically need a custom build (which prices from £200/month on usage-based billing with no seat licences) rather than a per-seat platform subscription.
How long does it take to set up a custom AI receptionist compared with RingCentral?
A custom build typically runs 2 to 3 weeks: discovery, training on your call patterns and FAQs, CRM integration, and a supervised pilot before go-live. RingCentral activates faster as a platform toggle, but only once you have migrated to or are already running their UCaaS stack and provisioned per-seat licences for every user. Net setup time is similar once platform migration is included, and the custom build delivers an agent tuned to your business rather than a generic intake template.
Is a custom-built AI receptionist GDPR-compliant for UK businesses?
Yes, when built correctly. The business acts as data controller and the vendor as data processor, following the ICO's published definitions. Call data sits on UK or EU infrastructure with a UK GDPR-aligned data processing agreement, and callers are told that an AI is handling the call to satisfy the lawfulness, fairness, and transparency principle. ORYX builds default to this setup; for FCA-regulated sectors, the agent also captures the call records required by sector rules.
Can a custom AI receptionist integrate with my existing CRM and phone number?
Yes. A custom build connects to your existing CRM (HubSpot, Pipedrive, Salesforce, Jobber, ServiceTitan, and similar) and routes through your existing UK number via SIP or call-forwarding rules. You do not need to migrate to a new phone system or move onto a UCaaS platform. The receptionist sits in front of your current setup and writes structured lead records back into the CRM after each call, with the qualification answers captured as named fields rather than free-text notes.
Want to see how this works for your business?
Learn more