Good morning, Alex
Here is what your AI receptionist has handled today.
Live conversation activity
● MonitoringConsultation scheduled for tomorrow at 10:30 AM. Confirmation SMS queued.
Urgent service request routed to the on-call team with a concise summary.
Service information provided. Callback requested for this afternoon.
Receptionist status
Today's appointment schedule
| Time | Caller | Appointment | Assigned to | Status |
|---|---|---|---|---|
| 10:30 AM | Olivia Bennett | Initial consultation | Sarah | Confirmed |
| 11:15 AM | James Wilson | Service assessment | Michael | Confirmed |
| 1:00 PM | Priya Shah | Callback | Reception team | Awaiting |
Call & message inbox
Review caller intent, transcript, summary, outcome and next action.
Recent conversations
Select a conversation
Choose a call or message to inspect its summary and transcript.
Appointments
Manage bookings captured by your AI receptionist.
Upcoming appointments
| Date & time | Customer | Service | Team member | Source | Status | Actions |
|---|---|---|---|---|---|---|
| Today · 10:30 | Olivia Bennett | Initial consultation | Sarah | Phone AI | Confirmed | |
| Today · 11:15 | James Wilson | Service assessment | Michael | Phone AI | Confirmed | |
| Today · 1:00 | Priya Shah | Callback | Reception team | Web chat | Awaiting |
Call flows & routing
Simple defaults with powerful controls for exceptions and escalation.
Standard inbound flow
Welcome caller, identify business and establish how the AI can help.
Classify booking, new enquiry, existing customer, billing or urgent request.
Answer from approved knowledge, capture details, book or send a follow-up.
Transfer, request callback or route to the correct team with context.
Read back key details, send confirmation and record outcome.
Routing rules
Fallback and resilience
Apologise, capture caller name, number, urgency and reason; create a callback task and notify the duty contact.
Do not claim the booking succeeded. Capture a request, queue it and confirm only after reconciliation.
AI receptionist
Configure your virtual front desk without writing complex prompts.
Receptionist profile
Capabilities & boundaries
Escalation contacts
Try a sample conversation
Knowledge base
Give your receptionist accurate business information and keep it current.
Business information
Mon–Fri 8:30 AM–5:30 PM · Sat 9 AM–1 PM · Sunday closed.
Service catalogue, suburbs covered and out-of-area policy.
Approved price list and rules for estimates.
Cancellation, refunds, parking, preparation and payment methods.
Knowledge quality
Illustrative answer coverage score
Integrations
Guided connections, clear permissions and resilient synchronisation.
Integration principles
✓ Least-privilege permissions
✓ Connection health and expiry alerts
✓ Test connection before activation
✓ Duplicate prevention
✓ Audit trail of changes
✓ Manual fallback if provider is down
Analytics & quality
Measure outcomes, not just call volume.
Call outcomes
Quality signals
Customer-friendly usage interpretation
Voice credit equivalence is illustrative: other actions (SMS, chat, booking, summaries and workflows) also consume credits. Telephony provider costs, taxes and supported countries must be finalised before publication.
Provider-level usage is ultimately metered and enforced by the Operations Centre; these prototype calculations are not a contractual allowance.
Plan & usage
Understand your subscription, estimated voice minutes, credit usage and hard spending limits.
Usage this cycle
37% of included credits used
Illustrative credit weights
Final metering should be cost-based and server-authoritative, including telephony and model-provider costs.
Recent credit ledger
| Activity | Credits | Type |
|---|---|---|
| Inbound calls · 12 minutes | −96 | AI usage |
| Monthly plan allocation | +5,000 | Subscription |
| Appointment booking | −5 | AI usage |
Available plans
Business setup
A guided checklist with recommended defaults. Complete each step before activating live calls.
Launch readiness
7 of 10 setup steps completed (sample state)
Business name, contact details, timezone, address and service areas.
Standard hours, public holidays, temporary closures and after-hours policy.
Verify accuracy and add source material.
Transfer targets, duty roster and fallback contact.
Confirm scopes, calendars, duplicate prevention and sync rules.
Choose a number or configure forwarding with your carrier.
Confirm applicable laws, disclosures, retention, access and opt-out process.
Test noise, interruptions, accents, urgent requests, failed transfers and provider outages.
Verify the duty number and callback SLA.
Activation is blocked until all mandatory checks pass.
Help & AI guide
Get contextual help with setup, call handling, bookings, integrations and billing.
Ask the AI product guide
Quick-start guides
Business details, opening hours, services and team.
Knowledge sources, voice, boundaries and test scenarios.
Guided integrations, permissions and test connections.
Credit weights, usage alerts, limits and top-ups.
Platform owner
Configure commercial settings, usage weights and product packaging. Customer view never exposes these controls.
Subscription and credit pricing
| Plan | Monthly USD | Included credits | Max agents / locations | Save |
|---|
Global usage rate configuration
Commercial safeguards
Operations Centre integration
Provision agents, exchange commands and reconcile events across tenant boundaries.
Connection configuration
No credentials are collected in this prototype. Backend secrets and OAuth tokens belong exclusively in the production secrets manager.
GET /api/v1/agents/{agent_id}/config
POST /api/v1/events
POST /api/v1/commands/{command_id}/ack
Illustrative route names only. Align with the actual deployed Operations Centre OpenAPI definition before implementation.
Bidirectional event contract
Tenant-scoped, versioned and acknowledged. No cross-tenant agent exchange without an explicit authorisation policy.
Integration audit stream (simulated)
No simulated events yet.
Resilience & durable messaging
Keep customer calls available while control-plane connectivity is interrupted.
Incident simulator
Production continuity policy
Delivery safeguards
Security & privacy controls
Protect callers, customer accounts, recordings and administrative actions.
Customer configuration (demo only)
Mandatory production implementation
Role separation preview
Customer administrators manage their own receptionist. Ravensford platform administrators manage global pricing, entitlements and operational incidents. Production must enforce role permissions on every API; hiding navigation is not security.
Launch readiness
Demonstrate commercial readiness without confusing prototype interactions with integration evidence.