How do you qualify a lead?

Write the situation in one sentence before you open a tool: who it is, what you know, and what you want them to do. If that sentence fits the next fifty rows, you do not have a reason yet.

Write the situation in one sentence before you open a tool: who it is, what you know, and what you want them to do. If that sentence fits the next fifty rows, you do not have a reason yet. If the fact is not on the record, on their site, or in a source you can open, cut it.

Start from the record you can open

Write the situation in one sentence before you open a tool. Who it is, what you know, and what you want them to do. If that sentence would fit the next fifty rows, you do not have a reason yet.

Check the fact. If it is not on the CRM, on their site, or in a source you can open, cut it. A wrong detail is worse than a plain email.

Before the send goes out

Sendblox can draft from the record and hold the send until someone on the team has read it. It should not invent a reason the record does not have.

If one of those is missing, the send waits. A larger list does not fill in a missing fact or a draft nobody has read.

• The fact is on a record you can open.
• There is one ask, and it can be answered in a reply.
• Hard bounces are suppressed, and a complaint stops that address.
• A person has read the draft. The tool does not send while that read is outstanding.

Keep the test small

Change one thing, send it to a slice you can read the replies from, and look at bounces and complaints before you widen it. A larger list does not repair a bad list or a mailbox that is already in trouble.

Sendblox can draft from the record and hold the send until someone on the team has read it. It should not invent a reason the record does not have, and it should not send while that read is still outstanding.

One record, then a small send

Write who it is, what you know, and what you want them to do. If that sentence fits the next fifty rows, you do not have a reason yet. Check the fact against the CRM, their site, or a source you can open. A wrong detail is worse than a plain email.

Change one thing. Send it to a slice you can read the replies from. Look at bounces and complaints before you widen it. A larger list does not repair a bad list, or a mailbox that is already in trouble.

Widen it only after you can read it

A small send you can read is the test. Bounces, complaints, and the replies you would be glad to receive. If those are fine, then widen. If they are not, a longer list copies the problem.

Hold the send until someone has read the draft against the record. A tool can assemble the note. It should not invent the reason, and it should not send while that read is still outstanding.