Count missed Gravitel calls without opening the PBX console

The agent calls the Gravitel REST API and starts with the structure of the PBX: employees with extensions, departments, numbers, personal caller IDs and the account balance. Then comes call history for the period you need — how many calls were answered, how many were missed and from which numbers — and next to it sit the dialing campaign queues, so both live conversations and the people the robot has not reached yet are visible.

A call in a cloud PBX never goes out «from the system»: it is started from the extension of a specific employee, and the PBX first raises their line and only then connects the customer. So the outcome is not known at launch — the agent checks the call status as a separate step. Missed calls are likewise counted from the history for the period rather than from an on-screen counter: only the history shows who called back and who did not.

On the write side the agent dials a customer from an employee extension, sends an SMS straight from the chat, sets or clears a personal caller ID for an employee and manages calls inside a dialing campaign — launching a robot call and dropping from the queue everyone who no longer needs one. A substituted caller ID is taken from the numbers of your own PBX. By default the agent works read-only, and before a call or an SMS it names the number and the text.

The key travels in the header of every request, the connector has no separate login of its own, and the scope available equals the scope of the PBX itself: the employees, numbers and call history of the organization the key was issued for. History over a long period is fetched page by page rather than in one request, and the rate is kept inside the limit. If there is no data for the period, the agent says so directly instead of showing an empty table.