Find out why an outbound list isn’t converting

<context>
I sent outbound to the list below and it isn't converting: [replies, bounces and meetings so far].
My target persona: [titles, seniority, department].
My ICP: [industry, company size, region].
The list was built on: [date].

List (name, company, title and email as they appear on my list):
[paste rows or attach the CSV]
</context>

<task>
Use Lusha to diagnose every row before I send anything else.

1. Check credits first. Run account_usage, which is free, and tell me what the full run will cost before spending anything.
2. Role check. For each contact, check Lusha for a company change or promotion signal, and compare their current company and title with what my list says. Mark every row where the person has left the account or moved out of my target persona, with the date it happened.
3. Email check. Compare the email on my list with the current verified work email. Search first, and reveal the email only for rows that failed the role check or where the domain on my list doesn't match the current company. Show the confidence grade and update date for every revealed email.
4. Timing check. Score each account on active buying signals. Mark accounts with no active signal, and name the signals behind the strongest ones.
5. Persona check. Mark contacts whose current title or seniority is outside my target persona.

Then give each row one diagnosis: Moved, Role changed, Wrong email, Off persona, No timing or Clean.
</task>

<output>
- A table: contact, company on my list, what Lusha shows now, diagnosis, fix
- A summary: the count per diagnosis and the single biggest cause
- A fix list: a new verified contact for every Moved row, the person now in that seat at the old account, and the five accounts with the strongest timing to work first
- The credits the run used
</output>

<constraints>
- Do not send, sequence or write anything to my CRM.
- Do not reveal phone numbers unless I ask.
- If a row can't be matched in Lusha, say so. Don't guess.
- Use the dates from the signals, not estimates.
</constraints>

The situation

We ran the diagnostic on October 25, 2026 against 20 sales leaders at US software companies with 51 to 500 employees. The role check looked back to April 1, 2026, so any contact who moved since then would still sit at their old employer on a list built in March.

Role and email check: 4 of 20 rows failed

The other 16 contacts were still in the same seat, with no company change or promotion in the window. On a list built in March, the four rows above would have sent email to addresses at their old employers.

Timing check: every account had at least one active signal

No account came back with zero signals. This sample was fast-growing software companies, so expect more No timing rows on a broader list. The three lowest-scoring accounts go to the bottom of the next sequence, not the top.

Credits the run used

30 credits: 1 for the search that returned the 20 contacts, 6 for the signal events returned, 20 for the account scores, and 3 for email reveals. One of the four emails had been revealed on this account before and cost nothing. The credit check at the start is free.