Cloud PBX
Open for Ooma
Forward an Ooma Virtual Receptionist option, ring group, or after-hours rule to Open and the AI picks up — Ooma keeps owning your phone system.
- Setup time
- Under 15 minutes
- Auth
- PSTN forward
- Directions
- Inbound · Call transfer
- Pricing
- Included with Open
01 — Overview
Can I add an AI phone agent to Ooma Office?
Yes — via Virtual Receptionist forwarding to a number Open provides. Ooma keeps owning users, numbers, and the dashboard; AI takes the calls you opt-in to.
Ooma Office is a closed cloud PBX aimed at small business — there's no externally exposed SIP for third-party AI integration. The supported integration pattern is forwarding: in Ooma's Virtual Receptionist (Ooma's IVR), an option, a ring group, or an after-hours rule forwards specific calls to an external phone number that Open answers.
Practically, you provision an Open inbound number, then add it as a forwarding destination on the Virtual Receptionist option you want AI'd (e.g. 'Press 1 for support'). Only the calls hitting that branch take the detour — direct extension dialing, voicemail, and your other Virtual Receptionist options keep working as before.
What the AI does on the call: it greets, listens, reasons over your knowledge base and connected tools, and acts. When the AI needs a human, it warm-transfers back to a number that lands on your Ooma team — typically an extension or ring group — with the live transcript attached as a follow-up email or CRM note.
Ooma Office Manager keeps showing every leg Ooma handled. Open adds AI-side reasoning traces, transcripts, and outcome tags on its side.
Billing stays predictable. Ooma keeps invoicing your seats. Open charges per resolved conversation.
What stays the same on Ooma
Ooma users and dashboard
Seats, ring groups, and Office Manager don't change.
Numbers and Virtual Receptionist
Numbers stay on Ooma. Virtual Receptionist still owns routing.
Reporting
Ooma analytics continue for legs Ooma answered.
Voicemail and after-hours
Existing rules keep firing.
What's new with Open
A forwarding destination
Specific Virtual Receptionist options forward to an Open-provided number.
AI handles those legs
Open answers the forwarded leg and runs the conversation.
Transfers come back via PSTN
AI bridges to a number routing back to your Ooma team.
Pricing model
Open per resolved conversation. Ooma keeps invoicing legs it answers.
02 — Why this works
The native Ooma experience
Works with Ooma's closed model
No SIP gymnastics — uses Ooma's own Virtual Receptionist forwarding.
Per-option opt-in
Pick exactly which Virtual Receptionist options or after-hours rules get AI.
Set up by lunch
15-minute integration — no admin tickets, no SBC pairing.
Warm transfer back to your Ooma team
AI escalations come back into Ooma as regular inbound calls.
03 — Setup guide
Wire up Ooma in under 15 minutes
Two trunks — one inbound, one outbound. Both configurable from Settings → SIP in the Open dashboard.
- 1
Open Settings → Phone Numbers
Provision or attach an inbound number Open will own.
- 2
Pick the Virtual Receptionist option
Decide which option, ring group, or after-hours rule should forward to AI.
- 3
Add Open's number as a forwarding destination
In Ooma Office Manager: Virtual Receptionist → option → Forward to External Number → enter Open's inbound number.
- 4
Pass the caller-ID through
Enable Ooma caller-ID forwarding so Open sees the real caller.
- 5
Assign the number to an AI agent
In Channels → Phone → Agents, assign the Open inbound number to the AI agent.
- 6
Place a test call
Dial the Ooma number, take the AI path, and confirm Open picks up.
04 — Configuration
Settings → SIP, at a glance
A real inbound trunk for Ooma looks something like this. Yours are generated when you open Settings → SIP.
Forwarding rule · Ooma
Sample
- Inbound (Open)
- +1 (212) 555-0199Open-owned
- Ooma target
- Virtual Receptionist option
- Forward to
- +1 (212) 555-0199
- Pass caller-ID
- Yesenable on Ooma
- Plan
- Ooma Office / Pro / Pro Plus
05 — Security
Encrypted, audited, refundable
SIP over TLS for signaling, SRTP for media. Every call is logged with full reasoning traces. SOC 2 Type II, GDPR-aligned, HIPAA- and PCI-ready. Backed by the Open $2M Refund Guarantee.
06 — FAQ