Field notes
The calls nobody answered are your best data
If your CRM only knows about recorded calls, it only sees the conversations and misses most of the effort behind them. NerdCRM logs every dial from MicroSIP's call list, including the ones nobody picked up, so you can see answer rates per person and spot list problems early.
Most call tracking starts with the recording. Someone picks up, the call is recorded, the file lands in the CRM, and that becomes “a call”. It is a reasonable place to start, because a recording is the part you can listen to.
But think about what a phone-heavy sales day actually looks like. A KAM dials ten numbers to get two conversations. If only recorded calls reach the CRM, you see the two conversations and none of the eight attempts. The rep who dialled a hundred times to reach fifteen people looks the same as the rep who dialled twenty times to reach fifteen. The effort, and most of what it tells you, has gone missing.
Every dial, not just the recorded ones
NerdCRM’s recorder agent already runs on Windows next to MicroSIP to upload recordings. It also reads MicroSIP’s own call history and sends every entry to the CRM: outgoing calls, incoming calls, and the ones nobody picked up. It checks the call list every 45 seconds by default.
Each dial is stored with its time, direction, number, the name MicroSIP shows for it, the talk time MicroSIP logged, and an outcome:
- Answered: talk time was logged, in either direction.
- Not received: an outgoing call with no talk time. The other end never picked up.
- Missed: an incoming call with no talk time. The KAM didn’t pick up.
The number is matched against your contacts as it comes in, so a dial to a known contact shows their name and links to their record. Unknown numbers show the number and MicroSIP’s display name.
All of this appears in Recordings → Call Log. You can filter by owner, by outcome (Not received, Answered, Missed (incoming)) and by date range. Admins and owners can see the Call Log for the whole team.
The per-owner summary
Above the list sits Dials by user, a summary of outgoing calls for the selected range. For each person it shows Total dials, Answered, Not received and Answer rate. Incoming calls are left out on purpose, so the numbers describe the effort each person put in, not how often the phone happened to ring.
That one table answers questions a recording list can’t:
- Who is dialling, and how much? Volume is a proxy for effort, not a target. Still, it is the first thing a manager wants to know and the hardest to get from recordings alone.
- Whose answer rate is out of line? If one person’s rate is far below the team’s, the cause is usually not the person. It is more often the list they were given, the time of day they call, or a number customers have started to ignore.
- Is the list going stale? A rising share of Not received across the whole team, over a few weeks, is often the earliest sign a lead source is drying up. You see it before pipeline numbers move.
Attempts per contact
The other useful habit is looking at how many tries it takes to reach someone. NerdCRM doesn’t calculate this for you yet, but the Call Log makes it easy to check. Filter to one rep and Not received, then look for the same contact or number coming up again and again.
Two patterns are worth watching for. A contact dialled five times with no answer is costing time that might be better spent elsewhere, so try a WhatsApp message or email instead, or let them go. A contact who was reached on the second attempt is a reminder that one unanswered call is not a dead lead. Both patterns make good coaching conversations, and both stay hidden if your CRM only knows about calls that connected.
For a single person’s day, the Daily Timeline puts these same dials alongside their recordings and CRM activities. Unanswered calls are drawn hollow, so a morning of attempts that didn’t connect is easy to spot.
Safe to re-send
Dial data is only useful if you can trust the counts. Each dial is stored with a fingerprint of the exact MicroSIP log line it came from, and the server refuses to store the same entry twice for the same person. If an agent re-sends its call list after a restart or a reinstall, the repeats are skipped and nothing needs cleaning up.
Two limits are worth knowing. MicroSIP’s call history must stay switched on, since that list is what the agent reads. And there is no backfill: history starts from the day the agent with call-log support is installed.
Getting it running
The dial log comes with call recording, part of the $4 per user plan. The free plan includes 100 recordings to try it, and recordings are kept for 45 days. The setup guide covers installing the agent next to MicroSIP, and the call recording page explains the rest. To look around first, the live demo has a sample workspace ready.
Frequently asked questions
Where do unanswered calls come from?
The NerdCRM recorder agent reads MicroSIP's built-in call history on the KAM's Windows PC and sends every entry to the CRM, answered or not. MicroSIP's call history has to stay enabled for this to work.
How does NerdCRM decide a call's outcome?
From the direction and the talk time MicroSIP logged. An outgoing call with talk time is Answered, and one with none is Not received. An incoming call with talk time is Answered, and one with none is Missed.
What if the agent sends the same call twice?
Nothing happens. Each dial carries a fingerprint of the original MicroSIP log entry, and the server skips any it has already stored. A reinstall or a re-send will not create duplicate rows.
Does it import calls made before the agent was installed?
No. History starts when the agent with call-log support is installed. It only reads the entries in MicroSIP's current call list, and MicroSIP limits how many it keeps.
See it in action
A read-only demo with phone-heavy sales data, ready in one click. No signup required.
More from blog
What a KAM's day actually looks like — one timeline, not three reports
NerdCRM's Daily Activity Timeline puts one person's dials, call recordings and CRM activities on a single chronological day view. Here is how it merges duplicates, why it never guesses a call length, and how a manager can use it for 1:1s without micromanaging.
Transcribing Bangla-English sales calls: what makes them hard and what we do about it
Sales calls in Bangladesh switch between Bangla and English mid-sentence, on a phone line, with brand names no dictionary knows. Here is how NerdCRM's call analysis handles mixed-language calls, from language hints and speaker separation to summaries in English or Bangla.
AI Call Analysis: every recorded call scored, every lead given a next step
NerdCRM now transcribes recorded sales calls in Bangla and English, scores each one on six signals, and turns the latest conversation into a clear recommendation on the contact and the deal: qualified, nurture, needs another call or disqualified.