Building the list, and reading the numbers after
The two ends of a calling session. Choosing who goes in the queue before you start, and what the report tells you once the queue is empty.
Watch
What it does
What is on the screen
The queue is a saved filter
You build it from your contacts by narrowing on stage, tag or last contact date, so who gets called is a decision you can check.
Outcomes are logged per call
Answered, no answer, wrong number, booked. You mark it as you go and it attaches to the contact rather than a notepad.
The report counts the session
Calls made, calls connected, and how long you spent. Enough to know whether an hour of dialling was worth doing again.
How it works
Setting up and reading back
- Filter your contacts down to the ones worth a call today.
- Save it and load it as the queue.
- Work through it, marking the outcome as each call ends.
- Read the report afterwards: how many answered, and how many led anywhere.
Worth knowing
Worth knowing
- The report counts activity, and activity is easy to mistake for progress. Connected calls matter; dialled ones do not.
- A queue built on a stale filter rings people you spoke to yesterday. Rebuild it rather than reusing last week's.
- Outcomes only exist if somebody marks them. Skip that and the report is empty.
Related
Related
Power dialer
The dialling itself, and what changes about the gaps.
Contact management
The records the queue is built from.
Call tracking and recording
Recording and attribution on calls coming the other way.
Build and read one queue
Log in, build a queue of twenty, work it, and read the report before you build another.