Home services / trades
Overflow and after-hours captured as jobs, not voicemail.
Problems we solve
Service businesses that live on inbound calls without a tenant OS typically hit:
- The van is on a job; two calls arrive; notes live on paper
- After-hours and lunch go to voicemail; the owner reconstructs the day at 10pm
- One shared office-PC password — you cannot fire one person
- Companies in one table with no row rule — the plumber sees the clinic
- Staff menus still expose Users or billing
- Live AI keys required just to evaluate the portal
- Buyers confuse a receptionist SaaS with an RTP turn engine
- The agent answers but the office still has no morning queue
One platform: Inbound ring → missed → ARI event to FastAPI → greet/classify/summarise → lead, booking or escalation → owner dashboard + staff callback list
Tenant OS (roles & isolation)
- Platform admin: every customer company, plans, usage, pause
- Tenant owner: calls, leads, bookings, billing, team
- Tenant staff: same daily queue — no Users menu, no platform screens
- JWT access/refresh; navigation from bootstrap so staff never see keys they cannot use
- Isolated evaluation workspaces (field service vs clinic) on one product
- Stripe-ready billing fields — live charge not claimed on the case page
Missed-call capture & adapters
- Leads, bookings and escalations a human can read in ten seconds
- Urgent work can alert on-call; bookings can land on calendar
- Asterisk ARI adapter to the PBX you already run
- Optional live AI + TTS providers; mock mode for evaluation
- Optional Google Calendar / WhatsApp-class alerts
- Usage, quota and plan recommendation summaries in the API
Platform architecture
flowchart TB Portal[Vue 3 owner staff platform admin] API[FastAPI JWT tenants billing] DB[(PostgreSQL)] AST[Asterisk ARI existing PBX] AI[AI and TTS adapters] Portal --> API API --> DB AST --> API API --> AI
Working-system video
Walkthrough of the live multi-tenant receptionist portal — tenant workspaces, agents, leads and platform admin. Not a slide deck; the recording is the product.
Open on YouTube → · Duration 5:54 · Dedicated demo page →
Portal screenshots (live product)
This product is a productized delivery of the engineering case study. Screenshots below are from the live portal host — product UI, not generated mockups.
- Growth Plumbing owner dashboard: inbound, captured jobs, escalated leak (evaluation seed)
- Platform overview: two active businesses, one flagged for attention
- Staff home looks like owner home — without Users
- City Clinic workspace has no plumbing jobs — isolation is the product
- This page is not the Asterisk RTP voice-AI engine case
Full case study with video and FAQ →
Configure this scope & send RFQ →
Built for
Clinics & salons
Follow-up appointments on a simple website, not a second PBX GUI.
Franchise / resellers
Platform admin over many shops without mixing data.
Owners who cannot sit by the phone
Morning list instead of reconstructing the day.
Integrated vs fragmented stack
| Traditional setup | This product direction |
|---|---|
| Talking voicemail, empty office queue | Classified lead/booking/escalation on the portal |
| Shared office password | Owner vs staff JWT; fire one person without locking everyone |
| Plumber sees clinic bookings | Tenant-scoped APIs and menus |
| Must have live OpenAI keys to demo | Mock adapters for evaluation |
Outcomes
No invented recovered-job percentages. What the system established: three roles, two isolated evaluation workspaces, staff cannot reach owner billing, calls written as work items. Exact recovered volume depends on your scripts and how fast people work the list.
Deployment & carriers
- Managed VPS — operate on your cloud account with runbooks.
- Your cloud — AWS/GCP/Azure; you own the account.
- On-premises — regulated or air-gapped cores (quote adjusted).
- BYOC / own SIP — your carrier contract or trunks on the PBX we deploy.
- Twilio / Telnyx / Sinch — CPaaS pass-through shown in the estimator (planning only).
Estimates are scope-based planning figures — not binding quotes. Taxes, carrier deposits, DIDs and third-party AI usage are scoped in discovery.
Related on UnifiedPBX.in
Frequently asked questions
Does the AI replace the PBX?
No. Asterisk (or your existing PBX) handles media; this product is the tenant OS and ARI adapter.
Is this the RTP voice-AI engine?
No. Asterisk voice AI (ExternalMedia RTP) is a different case. This is the receptionist SaaS portal.
Can we start after-hours only?
Yes. Narrow IVR replacement or overflow is a common first phase.
OpenAI vs local models?
Architecture can route providers; latency and residency drive the choice — scoped in discovery.
Multi-location isolation?
Yes. Tenant row rules; staff never see another shop.
Do we need live AI keys to evaluate?
No. Mock mode is documented for evaluation.
BYOC / Twilio?
Voice path is your PBX plus optional CPaaS in the estimator when live AI minutes are in scope.
Calendar / WhatsApp alerts?
Optional requirements in the quote builder.