You send the list you are about to work. We run the checks automatically, row by row, a person approves the finished check, and it comes back. That is a full check. Every row ends Ready, Stopped or Protected. You are not asked to operate anything and there is nothing to set up.
A CRM export in your own columns. A full check takes the whole file, up to 5,000 rows; the free check takes up to 300 rows you choose. Nobody has checked which email addresses still accept mail, which mobile numbers are still live, or who has moved on since it was built.
Whether each email address accepts mail, whether each mobile number is live, whether the person is still in the role and organisation on your row, and which rows are the same contact twice. The checking your team would have to do by hand.
We check whether a number is live. We do not screen numbers against the Telephone Preference Service (TPS) or the Corporate Telephone Preference Service (CTPS): whether a number may be called for marketing is not something this full check establishes.
The working file in the shape it arrived, and behind it the evidence for every row we acted on, each with the date we checked it. Row by row, a Row Passport records what was checked and what came back.
The list you did not build goes out as yours, and every row in it has a reason and a date behind it.
We show what the evidence supports. You decide. Disagreements are shown, not guessed.
Your headers survive in your order. Your own columns are passed through untouched. Empty cells stay empty where nothing was found. Nobody at your end has to put the file back together.
your file is read as a file, column by column, and mapped once. That mapping becomes part of your baseline, so the next list you send is read the same way.
For each contact we could check, we tell you what we found for each way of reaching them, and the date we checked it. An address that accepts mail, an address that does not, a professional profile we could find or could not. Where we can read it, the person's own headline and how long they appear to have been in the role.
the mailbox check is a live check against the receiving mail server, not a guess from a pattern. The role check reads what the person publishes about themselves and quotes it back to you as the evidence.
What it is not: a ranking, a grade or a score in the files. There is no column telling you who to contact first. The evidence and the date are the display, and the judgement stays yours.
A row we stop as a duplicate of another row in your file goes into the stopped rows with its reason, and the contact is listed once, on the other row. Nothing is merged in your CRM or your own systems.
Every row we stopped sits in a second file with one line of reasoning against it and the date we checked it. It is the part of the full check you can compare against your own knowledge of your own data, one row at a time. If you disagree with a stopped row, put it back.
Some rows raise a question before your full check comes back.
The Decision Brief records the rows placed by a person's review of a possible change of role or organisation, what we decided on each and the evidence for it. Each one shows what arrived, what we found, what we decided and where the row is now. Rows decided by a fixed rule, such as an address at a catch-all domain, are not in it: the rule is on each row in the update file.
Nothing here needs an answer: your files already reflect every decision. If you disagree with a decision on a row in your stopped rows, you can put that row back in your own list.
Every change and every removal is recorded with the reason and the date, in the changelog delivered with your files.
Before we touch a file we agree the terms and take one short written instruction from you: who you are instructing us on behalf of, that you are authorised to do so, what is in the file, what you are asking us to do, and anything in it we must never touch. On the call we agree the other two: where the finished list is going, and how you want the evidence. How we handle data is on our security page.
Your columns, in your column order, carrying the rows that nothing stopped.
2,075 of 2,400 rows in your working file.
The rows placed by a person's review of a possible change of role or organisation, with what we decided on each and why.
Nothing here needs an answer: your files already reflect every decision.
58 rows: 30 in your working file, 28 in your stopped rows.
One card per row: the finding it carries, the evidence behind it, and the date we checked.
One row for every row you sent: the outcome, the reason, the dates and what each channel established, keyed on your own record ID.
2,400 rows, one for every row in your file, each with its outcome and the date it was established.
Every row we stopped or kept aside on your protected list, with the reason and the date. Put any of them back if you disagree. It is your list.
325 in your stopped rows, each carrying the reason: 303 marked STOPPED, 22 marked PROTECTED.
Every change, every removal, and every difference we found and left in place. The reason and the date checked.
444 entries, each carrying the reason and the date we checked it.
The addresses kept out of the send, in the shape your sending tool loads.
+The private review link: one page carrying the counts, the categories, the dates and every file by name.
The free check runs the email, phone and identity checks on up to 300 rows you choose.
An example full check. The organisations and people in it are invented and the figures are illustrative, not measured.
Tell us which organisations are your own clients , which are competitors and which you are in a deal with, and those rows are kept aside on your instruction, with the reason, out of the list you are about to work.
Where the check finds a new employer for someone, the match runs again against it, so somebody who has moved into an organisation on your protected list, a client or a competitor, is caught even when the row you sent named a different employer.
When a row arrives with no LinkedIn URL, we go looking with the first name, the surname, the role on your row and the work email domain. What comes back is checked against the name, employer and role you sent us. A strong match is written into your file. A middling one is held back for a person to look at, and if nobody can stand it up it is dropped. A weak one is dropped and the rejection is recorded against that row. The cell stays empty rather than carrying a link we cannot back.
A contact you sent us in an earlier list, inside a freshness window, is recognised, and our earlier check is reused rather than run again.
Where the evidence establishes that the person found is not the person on your row, the row is stopped: it leaves your working file and is listed in the stopped rows with that reason. Where a possible profile could not be tied to the person, none of its details are used.
Send us the client list you trust least and pick a call slot. We run it the day before: each email address checked for mail, each mobile number checked for a live line, and each person checked against the role on your row, up to 300 rows. On the call we show you three numbers: how many would be in your working file, how many were stopped, and how many raised a question, with what we decided. Then we walk your own rows through with you. No cost, and if nothing in there surprises you we stop.
The free check takes one file of up to 300 rows, chosen by you.