Working it
The version of this that wrote straight into the CRM was removed on purpose.
It worked exactly as designed: discovered companies became accounts, people became contacts, and within a month nobody could tell which records came from a customer relationship and which came from a crawler.
The migration that took it out is named after the decision.
Three actions
Promote, say no with a reason, or come back to it.
Everything arrives untriaged. A person picks exactly one of three, and the three are mutually exclusive — each refusal naming what already happened and when.
Nine structured reasons for saying no rather than a free-text box: not a fit, wrong size, wrong industry, already a customer, a competitor, already in the pipeline, poor data, no interest, other. Which means the pattern in your rejections is readable a quarter later instead of being nine hundred sentences.
- A snooze is re-appliable while it is still in the queue —
And refused once a decision has been made. It comes back on its own rather than being lost.
- A snoozed row can never be promoted automatically —
The automatic path matches the active filter exactly, with the reason written down: a row somebody explicitly set aside must not come back through a side door.
- Promotion links the contacts, not just creates them —
The relationship between the person and the company is written too, so every screen that reads it sees the promotion rather than only the list that reads a shortcut.
- Names are split carefully —
Preferring the split that came with the data and falling back only for the part that is missing — because the naive version turns a two-word first name into a wrong one.
- There is no un-triage —
A decision is a decision. The refusal says so rather than pretending otherwise.
Automatic promotion
Off by default, and refusing before it considers anything else.
It can be switched on with a minimum priority and a minimum number of contacts. And the first thing it checks is not either of those — it is whether anybody at that company can actually be reached. No, unconditionally, if not.
The pass runs over the whole active queue rather than only that tick's new arrivals, so raising or lowering the threshold picks up what is already sitting there.
›Can a rep work this without administrator rights?
Today the shipped sales roles do not carry these permissions, so it needs a custom set. Worth raising during setup.
›Does a dismissal reach the discovery side?
No. The reasons are recorded and read by you; they do not travel back to change scoring. If you see that claimed elsewhere in our material, it is wrong.
›Is there a limit on how much comes back?
Yes — a run mirrors a bounded number of companies and the detail screen shows the top of that list. It is built to be worked, not browsed.