TaskWhole for recruiters
Sourcing is a volume problem with a memory problem attached. The candidates you contacted last week are the ones you forget to chase this week, and those are the ones who would have replied.
What goes wrong
- The same candidate gets two different approaches from two people on the desk.
- Follow-ups happen when someone remembers, which is not a system.
- Nobody can say which opening line is producing replies and which is being ignored.
- One mailbox carries the whole desk until it starts landing in spam.
Tasks a recruiter keeps
How it fits the week
A dozen roles open, each with its own list, each list going stale at a different rate.
Split the sending across mailboxes
Assign several mailboxes to a template and each send picks one at random. Volume spreads without anyone tracking it, and each has its own daily cap.
Work the thread, not the inbox
Sent shows every conversation with its reply state and what is due next. Marking a reply stops the rest of the sequence immediately.
Send from the profile page
The extension finds the address on the page you are reading, fills the variables from the text you highlight, and sends.
Compare openings honestly
Reply rate per opening template, over thirty or ninety days, next to how many follow-ups it took.
A sequence that fits
Every gap counted from the first message. Nothing sends on its own.
| Message | When | What it says |
|---|---|---|
| Approach | day 0 | The role, the reason it is them, and one question. |
| Nudge | day 3 | Two lines and the same question. |
| Keep warm | day 10 | Not this one, then. Ask what would be. |
Questions
Can a team share this?
Does it import from a spreadsheet?
What stops a mailbox burning out?
Other use cases
Start with one task
The whole working product is free. Reports and the extension are $5 a month, and only if you want them.