Internal Call Intelligence
Track every call back to the asset that earned it.
This first build gives you the production foundation from the reviewed plan: asset and number attribution, PBX and worker ingestion contracts, and a dashboard that surfaces lead volume, missed calls, and pipeline health.
Readiness
What this starter already covers
The app is wired around the actual system boundaries from the plan: PBX call intake, async transcript and classification updates, and reporting keyed to stable tracking numbers.
Live Data
Supabase dashboard is connected
This page is reading assets, phone numbers, calls, classifications, and pending jobs directly from your hosted database.
PBX Intake
Ready for call events
As soon as your PBX posts a call tied to a known tracking number, it will land in the canonical calls table and appear here.
Worker Path
Transcription lane is waiting
Pending transcription and classification jobs will show up in the queue metric as soon as recordings start flowing in.
Attribution Registry
Assets and tracking numbers
| Asset | Type | Market | Tracking Number | Qualified Leads | Missed Rate |
|---|---|---|---|---|---|
| On-Kaul Auto Salvage | website | Milwaukee, WI | (414) 719-6558 | 0 | 0.0% |
Recent Calls
Pipeline visibility
These cards mirror the canonical lifecycle your PBX, worker, and classifier will populate.
No recent calls yet. Once the PBX posts events, they will appear here.
Build Sequence
Suggested next implementation steps
- Post a real PBX test event to confirm your DID mapping is correct.
- Turn on the PBX export agent to send finished calls automatically.
- Deploy the transcription worker so queued jobs can clear.
- Add auth and asset-scoped policies once your first live users are ready.
Operational Note
Architecture gate to clear early
Validate real caller-ID passthrough to employee cell phones before you lock in the forwarding provider. That is the one requirement most likely to force an architecture adjustment.