How it works
From a spreadsheet to a finished calling block.
The whole loop, as it runs today. Nothing on this page is a mock-up.
- Import your list
Upload a CSV. Map the columns once, the dialler normalises every UK number, flags duplicates, and tells you what it skipped and why.
- Start a session
Pick a list and press start. Callbacks that are due today are pinned to the top, in the order you promised them.
- Dial from the browser
Headset on. D dials, H hangs up, M mutes. The call runs through the browser, with the carrier reporting every step back to the log.
- Save the outcome with one key
1 to 9 and 0, with a second key for the kind where it matters. Enter saves. The follow-up is created for you: a callback at the time you chose, a cool-off for not interested, a block for do not call.
- The next contact dials itself
After you save, the list moves on and the next call starts after a short countdown. Esc cancels it. Twenty-five dials without touching the mouse is the design target, and it's how I use it.
- Everything lands in the call log
Who, when, how long it rang, how long you talked, the outcome, the note, and the recording. Filter by outcome, list, or day. Export the filter as a CSV.
Recording starts when the prospect answers, not when you dial, so the file is the conversation and nothing else.
Settings you control
- Caller ID from your own numbers.
- Recording on or off.
- How long the dialler waits before it dials the next contact.
- How long it lets an unanswered call ring before giving up.
- Your own names for the outcome keys.
- A do not call list you can paste or upload.
What comes next
Not built yet, in this order: transcripts, voicemail drop, more numbers with health tracking, HubSpot sync, then call summaries and coaching, then sequences across call, email, and LinkedIn.
Each one ships when it works on my own calls first.