Call logs & analytics
Integrations → Exotel → View Call Logs shows every call to your project’s numbers, with a summary strip above it.
Analytics
Four cards summarise the selected window — 7 Days, 30 Days or 90 Days, chosen top right. It defaults to 30 days.
| Card | What it shows |
|---|---|
| Total Calls | Every call in the window, whatever the outcome. |
| Success Rate | Share that reached Completed, with the completed count beneath. |
| Avg Duration | Mean conversation length across completed calls, with total minutes beneath. |
| Failed Calls | Calls that ended without a conversation. |
Below the cards, a Call Outcome Distribution bar splits the window into Completed, Failed and Other.
If analytics can’t load you’ll see a short notice in its place, and the table below is unaffected. The two are fetched separately on purpose.
Filters
Three controls, applied as you change them:
- Number — one of your numbers, or All numbers.
- From / To — an inclusive date range. Both ends are included in full, so
FromandToset to the same day gives you that whole day.
A Clear button appears once any filter is active. Changing a filter resets you to page one.
The table
Six columns: Time, Direction, From, To, Duration, Status. Twenty-five rows a page, newest first.
Phone numbers are shown in full — both the caller’s and your own.
Direction always reads Inbound. qRaptor doesn’t place outbound calls — an agent answers a number, it doesn’t dial one. The column and the page heading mention outbound because the underlying record has room for it, not because it happens.
Duration means conversation length
Duration is how long the agent and caller were actually connected, measured from the moment the agent picked up to the moment the call ended. It is not ring time, and it is not the provider’s billed duration.
A call that rang and was abandoned shows 0:00, because no conversation happened.
Statuses you’ll see
| Status | Meaning |
|---|---|
| Completed | The agent answered and the call ran to its end. |
| In Progress | Live right now. |
| Ringing | Connecting, or very recently abandoned before it was picked up. |
| No Answer | Nobody was ever connected — the caller hung up during ring. |
Busy, Failed and Cancelled exist in the system but you’re unlikely to see them. The provider doesn’t distinguish those outcomes from an ordinary completed flow, so qRaptor derives what it can and reports the rest as No Answer. Treat No Answer as “the caller gave up”, not as a technical fault.
A call may sit at Ringing for a few minutes before settling. A background job reconciles outcomes with the provider every ten minutes, so a very recent abandoned call can briefly still read Ringing.
One call in detail
Click any row to open the detail panel.
| Field | Notes |
|---|---|
| Call SID | The provider’s identifier. Quote it in a support request. |
| Direction | Always inbound — see the note below. |
| From / To | Caller and your number. |
| Status | As in the table. |
| Started | When the call arrived. |
| Answered | When the agent picked up. Absent if it never was. |
| Ended | When it finished. |
| Duration | Conversation length. |
| Execution | View run — opens the agent run this call triggered. |
View run is the useful one. It takes you to the same execution view as any other agent run, with the full trace: what the agent decided, which tools it called, what came back. When a caller reports a bad experience, that’s where the answer is.
A call has no Execution link when it never reached an agent — an abandoned call, or one blocked by an access mode. Some older calls also predate run linking.
No recordings
Calls are not recorded. Audio is bridged live between the caller and your agent’s voice pipeline and never stored, so there’s no recording to play back and no audio file to download.
What you get instead is the run — the reasoning, tool calls and results behind the conversation, which is usually what you actually wanted when you went looking for a recording.
Where else calls appear
Because a number is attached to an agent within a deployment, calls also show up in Deployments → Executions beside your other runs. Call Logs is the telephony-shaped view of the same activity; the deployment view is the agent-shaped one.
Common issues
- A call is missing entirely — it was probably blocked by Authorized Only. Rejected calls happen before a record is opened, so they leave no row.
- A call is stuck at Ringing — wait ten minutes for the reconciliation sweep. If it stays, the caller abandoned during ring and it’ll settle as No Answer.
- Duration reads 0:00 on a call that connected — the agent never picked up, so no conversation was measured. Check the run link, or the agent’s voice configuration.
- No Execution link — see the note above.
- Analytics is blank but the table has rows — analytics failed to load; the notice says so. The table is independent.
- 90 Days shows less than you expect — you may not have 90 days of history. The window is a filter, not a guarantee.