Sort sequence replies so reps open only those worth a call
Reads each reply to your sequences for interest, a meeting, a referral, a "not now", an objection or a stop request, using your own competitor lists.
Try it on this example
Our sequence email they replied to: Subject: Month-end close at Halden Freight Hi Ingrid, Finance teams running several entities often lose the last week of the month to chasing invoice approvals by email. Teams like Northwind Logistics cut their approval time by more than half after moving to Ledgerline. Would 20 minutes next week be worth it to see how it would work across your entities? Best, Luca Romero Ledgerline
Their reply, with the quoted thread removed
- What is this reply to our outbound email, mainly?Meeting proposed100%
- Does the reply ask us to stop sending some or all messages?No94%
- Does the reply name or describe another person, role or address we should contact instead of, or as well as, the sender?Yes98%
- Does the reply say when we should contact them again later?No80%
- Does the writer say they use, have signed with or are evaluating a competing product or a manual process?Yes99%
- What is the main objection the reply raises, if any?No objection69%
- Does the reply ask us a question a rep should answer, such as about price, features, integrations or security?Yes97%
- Does the reply complain about our outreach itself, such as how often we write, how we found them or that it is irrelevant?No95%
These are real answers stored from one run on this example.
The prism behind it
Sort sequence replies so reps open only those worth a call
Fields
- Our sequence email they replied to
- Their reply, with the quoted thread removed
Context
These are replies to cold outbound emails from the sales development team at Ledgerline, which sells accounts payable automation software: invoice capture, approval workflows and supplier payments for finance teams at companies with several legal entities. Each reply is read as it arrives, before a rep opens it. Code has already removed the quoted thread and signatures where it could. Our ideal customer: a finance or accounts payable team at a company with 200 to 5,000 staff and more than one entity. Company size and entity count come from our enrichment data, not from these answers. Competing products we track: Tipalti, Coupa, Bill, Stampli, Medius, Basware, and spreadsheets or email approvals run by hand. The objections our team logs: price or budget; timing; already have a solution; no need; not their decision; security or compliance. Our rule on stopping: anyone who asks us to stop, in any words, gets no more sequence emails. Under US CAN-SPAM an opt-out from commercial email, business to business included, must be honoured within ten business days, and UK and EU rules give people the right to object to direct marketing. Code applies the stop, keeps the record and parses any date or name in the reply; these answers only say what the reply contains.
Questions
What is this reply to our outbound email, mainly? Choice
Pick the one option that fits the reply as a whole. Any reply that asks us to stop emailing is Opt-out, whatever else it says. A reply that proposes a time or asks for a booking link is Meeting proposed, not Interested. A reply that points us to someone else and gives no interest of its own is Referral.
Does the reply ask us to stop sending some or all messages? Yes / No
Read the reply in light of the message it answers. Count any wording that makes the wish to stop clear, such as "stop", "remove me", "no more of these", "wrong number, don't text", "leave me alone", "take me off your list", or insults that demand no contact. Do not count a complaint about the content alone, or a stop word used in another sense, such as "can't stop buying these". A plain "not interested" and an automated reply are not requests to stop. Yes: The reply asks us to stop some or all messages. No: The reply does not ask us to stop anything.
Does the reply name or describe another person, role or address we should contact instead of, or as well as, the sender? Yes / No
Count a name, a job title, a team or an email address the sender points us to, including a colleague they copy in or say they will forward to. An out-of-office message that names a stand-in counts. Yes: The reply points us to another contact. No: No other contact is named or described.
Does the reply say when we should contact them again later? Yes / No
Count a date, a month, a quarter, a season or an event after which they want us back, such as "after our renewal in March" or "try me in the new year". A time proposed for a meeting now does not count, and neither does a return date in an out-of-office message. A date or event given as a reason to talk now, such as a renewal they want to compare before, does not count. Code reads the date itself. Yes: The reply names a later time or event for us to follow up. No: The reply names no later time for a follow-up.
Does the writer say they use, have signed with or are evaluating a competing product or a manual process? Yes / No
Use the list of competing products in the context where there is one. Count any accounts payable, invoice capture or supplier payment product the writer uses today, has signed with or is evaluating, and a manual process such as spreadsheets or email approvals run by hand. Yes: A competing product or manual process is named or described. No: None is named or described.
What is the main objection the reply raises, if any? Choice
Use the objection list in the context. When the reply raises more than one, pick the one it gives first. Pick No objection when the reply raises none, as when it is keen, only asks a question, or is automated. A renewal or deadline given as a reason to talk now is not an objection.
Does the reply ask us a question a rep should answer, such as about price, features, integrations or security? Yes / No
Count any direct question to us about the product, the price, the company or next steps, including a request for material or a security document. Yes: The reply asks at least one such question. No: The reply asks us nothing.
Does the reply complain about our outreach itself, such as how often we write, how we found them or that it is irrelevant? Yes / No
Count annoyance at the emails themselves, the number of follow-ups, where we got their address, or a message that plainly does not apply to them. A polite "no thanks" is not a complaint. Yes: The reply complains about the outreach. No: The reply does not complain about the outreach.
Lens columns
reply_type, reply_type_probability, revokes_consent, revokes_consent_probability, names_other_contact, names_other_contact_probability, timing_given, timing_given_probability, uses_competitor, uses_competitor_probability, objection, objection_probability, asks_question, asks_question_probability, complains_about_outreach, complains_about_outreach_probability
Run it on your own text
Add this prism in the app, change any question, and test it on a file of your own.