The call
An engineer is already occupied
This invented example follows Jonah Vale's call to Cedar Loop IT. The caller wants to resume an existing support conversation.
IT support and managed service providers
Support callers want someone to understand what is stopping their work, while new prospects still need a first conversation. Your receptionist records the caller's account, follows your urgent-call choices and leaves clear requests for the team without presenting a message as a resolved ticket.
IT support and managed service providers can use Ringar AI to take support reports while engineers are occupied and book permitted discovery calls in a connected calendar or the built-in diary. It records the caller's account using configured questions and follows the owner's urgent-call choices. Ticket references supplied by callers stay with their messages, giving the support team a clear starting point for follow-up.
For MSPs and IT support businesses where engineers also cover the phone. It helps with existing clients reporting problems or chasing a conversation, and prospective clients asking about support. Reception captures the request while engineers retain the technical work and service-desk decisions.
Engineers concentrating on an issue can be interrupted by each new report. An unanswered line leaves callers unsure whether their own problem has been heard, which can prompt more calls.
The caller may already have a reference and simply need to speak to someone. Without that context, the return conversation begins by reconstructing the enquiry rather than finding the existing work.
Someone may say 'nothing works' when describing their own experience. Turning that account into a diagnosis too early can mislead the next person handling it.
A prospective client asking about an introductory meeting has little connection to today's outage. If their enquiry disappears into the same missed-call list, the team can lose the chance to arrange a proper conversation.
A caller's available window helps the team plan. Repeating it as an agreed engineering response creates an expectation before an engineer has accepted the work.
If reception says an issue has entered the service desk when it has only saved a call, staff may assume a workflow has happened that still needs attention. Clear outcomes prevent that administrative gap.
Use your business name and supplied information about support hours and services. The receptionist can answer administrative questions while keeping a prospect's enquiry available for a later sales conversation.
Choose the contact details and support questions. A caller's description and ticket reference can be captured in a message, with a requested callback window for the engineers.
Define what counts as an emergency for your business. Select a transfer, an urgent callback or booking-related options where set up. The action follows your configuration rather than a technical diagnosis.
It holds the caller and rings the transfer number for up to 20 seconds. Your introduction includes their first name and reason. Press 1 to accept or 2 to decline; after one declined or unanswered attempt, it takes a message.
With a connected calendar or the built-in diary, prospects can book the discovery appointments you make available. You can switch on booking texts and reminders for UK mobiles; recipients cannot reply.
A written transcript of every call and its outcome appear in the dashboard. Email details for bookings, messages and callbacks follow your settings, giving the team a record to use alongside its service desk.
| Plan | Monthly price | Included minutes | Effective pence per minute |
|---|---|---|---|
| Entry | £60 | 500 | 12p |
| Lite | £90 | 900 | 10p |
| Pro | £320 | 4,000 | 8p |
| Enterprise | Let's talk | Volume that does not fit a plan | By agreement |
Prices exclude VAT. Additional phone numbers: £5/month each.
Minute top-ups: Entry 12p per minute, Lite 10p per minute, Pro 8p per minute. Buy 300 to 10,000 minutes in steps of 100.
Entry is £60 a month for 500 minutes (12p per included minute), Lite is £90 for 900 minutes (10p), and Pro is £320 for 4,000 minutes (8p). The allowance covers time spent taking support reports and new-client enquiries. Short ticket chasers and longer descriptions use the same pool of minutes; the effective rates assume that allowance is used.
A person employed for working hours can own reception and other coordination tasks. A monthly minute plan buys incoming call handling, leaving engineers the requests to act on. Compare it with the reception work you need covered, rather than counting it as extra engineering capacity.
For per-call pricing, clarify whether each user reporting the same outage is a chargeable call and how brief ticket chasers count. A minute plan instead uses the duration of those conversations. Your actual mix of reports and enquiries determines the comparison, without assuming either method is cheaper.
Google Calendar, Microsoft 365 / Outlook Calendar, Apple iCloud Calendar and Cal.com are supported, or use the built-in diary. Keep bookable introductory appointments aligned with the sales team's availability.
The API reads your calls, callbacks and bookings. Configure webhooks to send completed-call outcomes to n8n, Zapier, Make or your own endpoint. Native CRM and named service-desk, job, practice or case-management integrations are not available; downstream ticket handling requires separate work.
Forward calls from the existing number using your provider's instructions. Available all-call, busy and unanswered options and charges vary. Choose how reception fits around the support line your team still answers.
Partners add SIP numbers, with the phone connection arranged with us and the carrier during onboarding. Carrier details and a test precede activation. Establish support for your existing system rather than assuming compatibility.
Try reports from different people and inspect each record. The receptionist should preserve what each caller says rather than assert a common diagnosis.
Ask for progress on an existing issue. A useful callback request keeps the caller's reference and question together.
Define the situations and route in setup, then try an unanswered transfer. The engineers need a clear account of what happened on the call.
Make only permitted introductory appointments available. A support request can remain a message for the team.
Ask who will build and maintain the workflow into your service desk. A call event is an input to that process, not a native ticket integration.
Say what your team answers all day and we will get back to you.
Each one is answered, and each ends with something your team can act on.
Example calls. A booking is made where a calendar is connected.
Calls this week
Enter your website. Ringar learns your IT support provider and becomes a receptionist that knows it.
No account needed.Your browser will ask to use the microphone.
An example call to Cedar Loop IT, to the note your team receives.
The call
This invented example follows Jonah Vale's call to Cedar Loop IT. The caller wants to resume an existing support conversation.
The record
The write-up keeps ticket 418 with Jonah's request. It is a call record for the team, separate from the service desk.
The next step
The team can look up the support record before returning the call. The requested time is captured without changing the ticket or booking engineering work.
Not seeing your question? Ask us directly on a demo.
The best fit records the caller's account and follows your escalation choices without pretending to fix the fault. Test a caller reporting an outage and another chasing a ticket. Ringar AI captures support messages and can book permitted discovery appointments.
Entry is £60 a month for 500 minutes (12p per included minute), Lite is £90 for 900 minutes (10p), and Pro is £320 for 4,000 minutes (8p). Choose from total support-line minutes, including repeat outage calls and prospective client conversations.
Yes, it takes support messages and callback requests using the questions you configure. It can also book permitted appointments in a connected calendar or the built-in diary; native ticket creation is not available.
Yes, an outage report can follow the urgent-call handling you configure. You define what counts and choose a transfer, urgent callback or a booking option with the relevant setup.
Supported calendars are Google Calendar, Microsoft 365 / Outlook Calendar, Apple iCloud Calendar and Cal.com, with a built-in diary also available. Those connections support appointment booking rather than access to your service desk.
Yes, with a transfer number configured, it holds the caller while ringing you for up to 20 seconds. You hear their first name and reason, then press 1 to accept or 2 to decline. It tries once; a declined or unanswered transfer returns to the receptionist for a message.
It records the support request for your team or tries a transfer where configured. The saved callback includes the caller's details, their account of the problem and when they can speak.
No, there is no native service-desk or CRM integration. The API and configured call-outcome webhooks can support a separately built workflow.
No, it takes the request for your engineers. It does not diagnose the fault, read live ticket progress or estimate a restoration time.
It provides administrative reception in English only, with no clinical, legal, financial or other professional advice. It is not an emergency service and cannot promise someone will pick up or meet a response deadline.
Related reading
Twenty minutes, a real example from your business, and an honest answer about whether it would help.