Answer routine questions
Share approved information about hours, location, services and booking policies. Keep that information current rather than asking the assistant to guess.
Solutions / AI receptionist
Give callers a useful first answer, even when your team is busy. We build an AI receptionist around your opening hours, services and handover rules, so enquiries reach the right place.

When you are serving a table, helping a patient or working on site, answering every call is difficult. A missed enquiry can leave a customer unsure what to do next. Answering in a rush can also mean losing the details your team needs.
An AI receptionist gives routine enquiries a consistent starting point. It can explain agreed information, collect the reason for a call and pass a clear summary to your team. You decide what it may handle and where a person needs to take over.
We start with the questions callers actually ask, your opening hours and your existing process. Together we define the information the assistant can use, the details to collect and the situations it must hand over.
We agree how calls should reach the assistant and where summaries should go. Booking or CRM connections depend on the systems you use and the access they provide. We confirm those connections before promising a particular workflow.
Try realistic calls with your team, including unclear requests, unavailable appointments and out-of-hours enquiries. Review the wording and handover behaviour before launch. Start with a defined scope, then refine it from the calls you review.
Choose the parts that solve a real problem for your team.
Share approved information about hours, location, services and booking policies. Keep that information current rather than asking the assistant to guess.
Collect a callback number, the reason for calling and the details your team needs. Route a concise summary into an agreed inbox or workflow.
Where an integration supports it, check availability or help create a booking. Otherwise, record a request for your team to confirm; do not present it as a confirmed appointment.
Use agreed routing rules for calls that need a person. If nobody is available, explain the next step and capture a callback request without promising an immediate response.
Help with opening hours, directions, table enquiries and order questions. Agree how dietary or allergy questions reach a trained member of staff, rather than relying on an improvised answer.
Support appointment administration and general service enquiries. Define clear boundaries around sensitive information and clinical questions; the receptionist workflow should route those questions to the appropriate team.
Capture the job type, location and callback details while your team is on site. Define which enquiries need prompt attention and what happens when the office is closed.

Proof / Cora at NUR
NUR Indian Restaurant brings its website, ordering and Cora meal assistance into one customer experience. The supplied screen shows Cora as an entry point on the restaurant’s mobile site.
That is relevant product work behind this service. It does not establish phone-call volumes, booking results or a particular telephony setup. Your receptionist’s call handling and integrations would be scoped and demonstrated for your business.
Cost depends on call usage, the workflow and the connections you need. We scope the setup and ongoing service before quoting. Ask us to separate setup, usage, integrations and support so you can compare the full commitment. There is no fixed price claimed in this preview.
We agree a schedule after checking your phone arrangement, business information and integrations. A focused enquiry workflow has fewer dependencies than a booking system with several calendars. Your team also needs time to review wording and test handovers before callers use it.
The voice and conversation style should be tested with the language your customers use. Listen to a demonstration, interrupt it and try an unclear request. We aim for clear, natural exchanges, while making the assistant’s role understandable and keeping a route to a person.
We define urgent-call rules with you before launch, including transfer attempts and what to say if nobody answers. An AI receptionist is not an emergency service. The workflow should never leave callers believing that a callback request guarantees an immediate response.
Before launch, agree what data is collected, who can access it and how long it is kept. If recording or transcription is enabled, include an appropriate caller notice and review the processing arrangements. Your business should approve the privacy wording and responsibilities; compliance is not something a voice feature alone can guarantee.
Tell us which calls interrupt your day and what a helpful response should look like. We’ll use that to shape a practical first scope.