Call Log
The Call Log workspace records and tracks calls linked to your leads and deals, with status, duration, recording, transcript, and AI follow-up.
The call log workspace records, tracks, and manages calls linked to your leads and deals. Each log is workspace-specific and shows status, duration, participants, and related notes and tasks.
Make a call
- Open a Lead or Deal record.
- Click Make a call below the name, or use Log a call when logging manually. Calls require a phone number. You will be prompted if it is missing.
Refer to the Twilio integration to understand where and how to make calls.
After the call, check the Calls tab on the lead or deal to review the activity. When a recording is available, you can play it from the call entry there. The same recording, transcript, and AI summary are also available from the Call Logs list. Open any entry to play the recording and review details.
Call Logs
The Call Logs list shows every call across your workspace. Use it to filter by status, type, telephony medium, team, duration, or caller, and to open details, recording, transcript, and linked tasks.
Beyond the list, Power Dialer History provides session-level analytics: processed, pick-up, and contacted counts, call duration, and per-call disposition, deal linking, and recordings.
For deeper detail on a call, open the call entry to see status, type, participants, recording and transcript, AI summary and suggested disposition, and linked notes and tasks.
Call Metrics & Outcome Matrix
When dialing leads, Pixelwand CRM differentiates between objective Telephony Pick-ups and confirmed Sales Contacts:
- Pick-up: The call was answered by the recipient or their voicemail and produced talk time (
status == 'Completed' and duration > 0). - Contacted: A human conversation took place. Requires the call to be a Pick-up and the agent to select a disposition marked with
is_contacted(e.g. Connected, Not Interested, Follow-up Required). - Average Call Duration: Derived strictly as
Total Talk Time / Pick-ups, ensuring talk time per connected call remains mathematically consistent.
Outcome Summary Matrix
| Scenario | Telephony Status & Duration | Agent Disposition | Pick-ups | Contacted | Talk Time | Processed |
|---|---|---|---|---|---|---|
| Normal Conversation | Completed, 45s | "Connected" (is_contacted: 1) | 1 | 1 | +45s | +1 |
| Spoke, but rejected | Completed, 20s | "Not Interested" (is_contacted: 1) | 1 | 1 | +20s | +1 |
| Follow-up Requested | Completed, 65s | "Follow-up Required" (is_contacted: 1) | 1 | 1 | +65s | +1 |
| Voicemail / Answering machine | Completed, 18s | "Left Voicemail" (is_contacted: 0) | 1 | 0 | +18s | +1 |
| No Answer / Rang out | No Answer, 0s | "Call Back Later" (is_contacted: 0) | 0 | 0 | 0s | +1 |
| Busy line, agent clicked Connected | Busy, 0s | "Connected" (is_contacted: 1) | 0 | 0 (blocked) | 0s | +1 |
If a call was not answered (
No AnswerorBusy), any requested tasks and lead status updates still save, but the attempt is blocked from counting as a "Contacted" conversation to prevent false performance metrics.