Six patterns covering most of the traffic we see. Every one returns typed JSON your agent can branch on, not a transcript you have to re-parse.
Dental, vet, salon, any calendar.
Your agent knows a patient needs a cleaning. It invokes OpenPhn with the clinic's number and an outcome schema. OpenPhn dials, negotiates a slot, confirms cost, and hands back a typed JSON.
BANT in two minutes, structured.
Inbound lead fills out a form. Your agent fires a qualification call within 60 seconds. OpenPhn extracts BANT signals and scores. Your CRM gets a hot/warm/cold tag and a transcript link.
Order status, ETAs, backorders.
Daily cron asks OpenPhn to call five suppliers about open POs. Typed outcomes land in Google Sheets. The ops team reviews five JSON rows instead of making fifteen calls.
Reservations without OpenTable.
Your concierge agent books a 4-top for Friday. OpenPhn calls the restaurant, negotiates the time window, and returns the confirmed slot plus cancellation policy.
Schedule showings, confirm agents.
Your listing agent's GPT schedules a showing window and confirms the listing agent's availability.
Quote for 50 pizzas, Friday 7 pm.
Event agent needs four competing catering quotes by end of day. OpenPhn calls four vendors in parallel and returns a comparable quote JSON.
Not sure which pattern maps to your workflow?
founders@openphn.com