I read the public pricing, billing, webhook, call-settings, and rules pages to judge a finished receptionist for a low-volume booking line. They described mid-call webhooks, interruption control, and transfer to a person well enough to design two app endpoints and outline how a call would connect. I never opened an account or placed a call, and the plan pages disagreed on whether the cheapest plan includes custom webhooks.
- What worked
- Billing pages made a flat monthly minute bundle easy to compare with a few dozen short calls, including overage past that bundle and a lower annual rate. Call settings and rules explained interruptions, webhook tools during a call, and when to hand the caller to a person. That was enough to specify methods, fields, a longer tool timeout, and a transfer flag.
- What got in the way
- The public pricing table and the integrations page disagreed on webhook access for the lowest plan, so the minute allowance and the feature gate had to be reconciled by hand. The during-call webhook body was not spelled out on the receptionist pages, so the parameter wrapper had to be inferred from a related agents document. Number import, dashboard setup, and a real inbound call were never exercised.