Integrations
Onyx Phone logs the call, the recording, and your notes. It does not store customers, quotes, or invoices. A generic API, by itself, is not what most shops ask for first.
When a call ends, send the caller’s number, the time, the line, the notes, and a link to the voicemail into Jobber, Housecall Pro, ServiceTitan, HubSpot, or Salesforce. One real connection is worth more than a public API with nobody on the other end. This is Custom. It is not built.
A phone menu, after-hours voicemail, or ringing only a cell. Those paths exist for lines we operate ourselves. They are not on the customer signup form, and the Twilio screens stay off your account. Ask for Custom if you need one of them.
Porting is included in every plan. You give us the carrier, account number, PIN, authorized name, and a recent bill, and we start the request with you. Until it completes, your carrier keeps the line. We do not forward live calls into another phone system, and we do not move your number to Quo, Dialpad, or Aircall.
A text when a call is missed needs US SMS, which waits on 10DLC. Ringing a locked iPhone needs VoIP push. Both are later. Neither is a reason to invent a CRM API first.
Shops ask for “ring us 7 to 5, voicemail after.” The desk can play a greeting and take voicemail when nobody answers. A clock that switches that for you is not built. It fits Custom.
An API is the right follow-on once a real job system is receiving finished calls. Building the API before that usually produces events nobody’s software reads.