Call history search and reporting for sales reps

The moment a rep finishes a call and needs to verify what was said, find a contact they just spoke with, or prove how many calls they made that week, they hit a wall: the dialer's native history is unsearchable, unfiltered, and can't be exported without admin access or a manual count. This gap persists because dialer vendors are optimized around routing and uptime metrics — the people who buy the software are ops managers and IT, not the reps who live inside it daily. Reps don't have a seat at the procurement table, so their workflow frustrations never become a contractual requirement.

What's actually broken, per the complaints: you can't filter calls by time window, you can't search 'All Calls' by contact name or number, and you have to contact customer support just to find out whether a dropped call was a network issue on your end or the caller's. That last one alone wastes hours per month across a team.

Without this, reps either reconstruct their day from memory, ask a manager to pull a report, or give up on verifying contacts altogether — which means follow-up falls through. For a team of 20 reps each losing 20 minutes a day to this, that's real pipeline leakage, not just inconvenience. And it recurs daily, which is what makes it a business rather than a one-time annoyance.

What to build

Build a browser extension and lightweight web dashboard that connects to dialer APIs (starting with Aircall) and gives individual reps a searchable, filterable personal call log — by date range, contact name, number, outcome, and duration — with one-click access to the linked recording or transcript, exportable to CSV.

Where to start

Start specifically with Aircall users, where the 'cannot search All Calls' complaint is documented and widespread, and where the public API is mature enough to pull per-user call history without requiring admin credentials — giving you a tight, provable use case before expanding to other dialers.

The hard part

Dialer APIs expose call data at the account or team level, not scoped to a single rep's view, so building a truly personal log means handling OAuth authentication per user and filtering server-side data in real time — which gets expensive and fragile as call volume scales.

How it makes money

Per-seat monthly subscription, charged to the individual rep or expensed through a team plan — starting around $9-15/seat/month, with a free tier capped at 30-day history to drive organic adoption before a manager buys seats in bulk.