How to Qualify Intent from a Two-Line Email Reply

Most SDRs have learned to read a two-line email reply as either a "yes" or a "not now." That binary is too coarse. A two-line reply carries significantly more signal than its word count suggests — if you know what to look for — and the teams that read those signals accurately spend their follow-up effort on the threads that actually move.

This post walks through the intent signal framework we use to score reply threads at Enrola: what the signals are, what they indicate, and how they map to prioritisation decisions. The goal isn't to replace human judgment — it's to give SDRs a consistent mental model for a kind of reading they often do intuitively but rarely do systematically.

Two lines that tell you a lot

Take a reply like this:

"Thanks for reaching out. We're actually looking at a few tools for this right now — can you tell me more about how the Salesforce integration works?"

That's 28 words. From those 28 words, you can extract: (1) active evaluation is underway ("looking at a few tools right now"), (2) there's a technical requirement the prospect cares about (Salesforce integration), (3) they're in compare mode, not just casually browsing, (4) they asked a specific question, which means they want a substantive response.

Now compare it to:

"Thanks, I'll have a look."

Five words. Active evaluation: absent. Specific requirement: absent. Question asked: none. This reply is a polite acknowledgment, not an intent signal. It still warrants a follow-up — the prospect didn't say no — but the priority, urgency, and tone of that follow-up should be calibrated differently.

The signal framework makes that calibration systematic rather than intuitive.

Signal dimension one: Active evaluation language

The highest-value intent signal in a short reply is explicit active evaluation language — phrases that place the prospect in an ongoing decision-making process rather than a passive browsing state.

High-signal phrases: "we're evaluating options," "looking at a few tools," "we have a review coming up," "we're comparing a couple of solutions," "our team is putting together a shortlist."

Why these matter: they indicate the prospect has internal momentum. There is a buying process underway, even if it's informal. This is categorically different from a prospect who might someday buy — these prospects are actively spending cognitive time on the problem right now. The response window for active evaluators is shorter and the urgency of follow-up is higher.

A subtle variant is timeline language that implies evaluation without stating it explicitly: "we're hoping to have something in place before Q4" or "we're mid-project on a workflow rebuild." These don't use the word "evaluating" but they carry the same signal — there is a specific operational context into which your product might fit, and the prospect is thinking about timing.

Signal dimension two: Specificity of the question asked

A prospect who asks a question in their reply is demonstrating that they've already mentally processed enough about your product to generate a specific inquiry. The specificity of that question is a strong predictor of conversion potential.

Generic acknowledgment (no question): "Thanks, I'll take a look." → Low intent signal. Polite, non-committal, no active evaluation implied.

Category question: "Can you tell me more about how this works?" → Medium intent signal. Curiosity is present but unfocused. The prospect hasn't yet identified the specific dimension they care about.

Feature/integration question: "Does this connect to our Salesforce environment?" or "Can the threshold be adjusted per campaign or only globally?" → High intent signal. The prospect has mentally placed your product in their stack and is testing fit against a specific requirement. This level of specificity indicates they've read your material and thought about implementation.

Commercial question: "What does pricing look like for a team of 8-10 reps?" → Very high intent signal. Commercial questions signal budget awareness and authority. A prospect asking about pricing is thinking about the purchase decision, not just the product decision.

In terms of follow-up prioritisation: a commercial-question reply from a mid-fit company should be worked before a polite-acknowledgment reply from a high-fit company. The former is showing active purchase intent; the latter hasn't yet.

Signal dimension three: Stakeholder and process references

A two-line reply that mentions another person — "I'll need to loop in our Head of RevOps on this" or "our IT security team would want to review anything that connects to our email" — is giving you valuable process intelligence. The prospect is thinking about their internal buying path.

This signal matters for two reasons. First, it tells you the deal has multi-stakeholder complexity, which affects your account strategy. The follow-up should acknowledge this: "Happy to put together a brief overview that's easy to share with your RevOps lead — would a one-page summary be useful?" This is more useful than a generic follow-up that ignores the stakeholder reference the prospect made.

Second, it indicates the prospect is mentally moving the conversation forward. They're not just receiving information — they're thinking about who else needs to be in the room. That's a form of internal advocacy, which is a strong deal-progression signal.

Signal dimension four: Problem framing in the prospect's own words

The highest-signal two-line replies are the ones where the prospect describes their current pain in operational terms. "We're running three SDRs off a shared inbox and it's a mess" is a gift. The prospect has told you: (1) their current state, (2) the specific operational problem, (3) that it's causing them enough pain to mention it in a brief reply.

Problem-framing replies deserve the most substantive follow-up. The prospect has handed you the entire discovery context in two lines — don't waste that by responding with a generic "great, here's a link to our demo page." Reference the specific thing they said. Acknowledge the pain. Show that you understood what they told you. That's the follow-up that gets a response.

We're not saying problem-framing replies are always high ICP-fit — sometimes it's a small company with a small-scale version of the problem. But within ICP-fit threads, problem-framing is the signal that most clearly separates active buyers from curious browsers.

How the signals combine into a thread priority score

In practice, these four signal dimensions combine to produce a composite intent score for a given reply thread. The scoring doesn't need to be mechanical — even reading the signals informally and asking "does this reply show active evaluation, specific questions, stakeholder references, or problem framing?" will improve triage quality.

For automated scoring, the four dimensions can be weighted into an Intent Signals score alongside the Company Fit and Role Fit dimensions of a standard ICP model. A 0-100 intent score, combined with the static firmographic and role scores, produces a thread priority ranking that better reflects actual deal readiness than firmographic rank alone.

The frame to keep in mind: a reply is not a binary yes/no signal. It's a data point about where the prospect is in their buying journey, what they care about, and how much cognitive engagement they've brought to the conversation. Reading that data point accurately — even from two lines — is one of the highest-leverage skills in sales development, and it's one that benefits from a systematic framework rather than pure intuition.

The signals are there. They're just not always labelled.