Call detail records
Your PBX already knows.
It just won’t tell you.
Callnsight syncs every call your PBX records — numbers, extensions, talk time, audio — and makes them searchable by any part of a number, in your own timezone.
6 of 6 calls
| Started | From | To | Talk |
|---|---|---|---|
| Jun 24·22:25 | 101 | (213) 555-0168 | 0:45 |
| Jun 24·21:14 | (310) 555-0142 | 101 | 1:10 |
| Jun 24·16:03 | 102 | (415) 555-0132 | 3:20 |
| Jun 23·09:51 | (626) 555-0184 | 100 | abandoned |
| Jun 22·14:12 | 103 | (720) 555-0168 | 0:15 |
| Jun 22·11:40 | (855) 555-0119 | 101 | 2:04 |
A PBX stores a call as 2026-06-25 05:25:59 UTC, an extension, and a raw string of digits. Nobody remembers the whole number, nobody works in UTC, and nobody wants to reconcile another CSV export.
What you get
- Call records
- Filter by connection, direction, extension, caller ID or date range. Export exactly the rows you filtered, not the whole table.
- Recordings
- Play back in the browser and scrub without downloading the file first. Downloading is a permission you grant, not a link you share.
- Reports
- Call volume and talk time by day, split by direction, with an abandoned rate. The days are your days: buckets follow your timezone, not the server’s.
- Usage
- Calls, recordings and storage per account, sampled hourly. Retention is a policy you set, and it prunes what it promises to prune.
An assistant that answers questions about your own calls in plain language is in early access, enabled per account. Transcription and call analysis are not built yet.
How it works
Once
Connect your PBX
Point Callnsight at your Vodia PBX and test the connection. Credentials are encrypted before they touch the database.
Every 15 minutes
Calls arrive on their own
Records and recordings sync on a schedule, re-scanning a six-hour window so nothing slips through a gap. The first run backfills your history.
Whenever you need it
Find the call
Search a fragment of a number, open the recording, or export the month. No exports to reconcile, no vendor UI to fight.
Built in
- Tenancy
- Every query is scoped to your account at the database layer
- Credentials
- PBX and storage secrets encrypted at rest, never sent to the browser
- Audit
- Sensitive changes logged with an actor, an account and redacted values
- Sign-in
- Two-factor authentication; Google sign-in optional
- Recordings
- Stored on your own S3 or SFTP provider