TOEIC Link Reading — Part Seven Email-and-Reply Chain Intent-and-Response Tracking: How to Map Request, Objection, and Resolution Across a Two-Message Exchange Without Losing the Thread

The email-and-reply pair is one of the most common multiple-passage formats in TOEIC Link Part Seven: a first message states a request, a problem, or a proposal, and a second message responds to it. The questions that follow are engineered around the connection between the two — what was asked in the first and how the second answered it. Candidates who read the two messages as two independent passages, extract facts from each in isolation, and then try to answer, consistently mis-handle the cross-message questions, because the intended answer lives in the relationship between the messages, not inside either one.

Internal practice-corpus data shows that on email-and-reply sets, candidates who explicitly map the first message's intent to the second message's response move answer the cross-message question at roughly 79% accuracy, while candidates who process the two messages independently answer the same question type at roughly 48%. The 31-point gap is almost entirely a tracking gap: the first group holds the request open in working memory while reading the reply; the second group lets the request fade and then guesses at the connection. For the broader multi-passage skill, see the Part Seven multiple-passage cross-reference strategies guide, and for the evidence-synthesis discipline that underlies it, see the double-passage cross-text information integration guide.

Why the connection carries the question

An email exchange is a small structured dialogue. The first message opens a loop — it asks for something, reports a problem, or floats a proposal — and the second message closes or partially closes that loop. The test writer builds the highest-value question around loop closure: did the reply grant the request, decline it, defer it, or grant it with a condition? That question is unanswerable from either message alone. Reading the reply in isolation tells you what the second writer said; it does not tell you what they were saying it about unless you are still holding the first message's intent.

The discipline, then, is to read the first message with one job above all others — identify and hold the intent — and to read the second message with the first message's intent as the active reference. Everything the reply says is interpreted as a move relative to that intent. When candidates internalize this, the reply stops being a wall of new facts and becomes a set of responses to a question they already hold.

The four opening intents

Intent 1 — The request

The first writer asks the recipient to do something: approve a budget, send a document, reschedule a meeting, confirm availability. The loop is "will you do X?" The reply's job is to grant, decline, defer, or condition. Hold the exact action requested — many wrong answers swap the requested action for a similar one the reply happens to mention.

Intent 2 — The problem report

The first writer reports something wrong: a shipment is late, an invoice is incorrect, a system is failing. The loop is "how will this be resolved?" The reply's job is to explain, apologize, propose a fix, or assign responsibility. Hold the specific problem — the reply often addresses one aspect of a multi-part problem and leaves another open, and the question targets exactly that.

Intent 3 — The proposal

The first writer proposes an arrangement: a new schedule, a partnership, a change in process. The loop is "do you accept this proposal?" The reply's job is to accept, reject, counter-propose, or ask for more information. Hold the terms of the proposal — a counter-proposal in the reply changes one term while keeping others, and the question frequently tests which term changed.

Intent 4 — The information request

The first writer asks a question seeking information: pricing, availability, specifications, policy. The loop is "what is the answer?" The reply's job is to provide the information, redirect to another source, or state that it is unavailable. Hold the specific question — replies to information requests often provide adjacent information that does not actually answer what was asked, and the question exploits the mismatch.

The five response moves

The second message will make one or more of these moves against the held intent:

Grant / accept / answer — the loop closes affirmatively. Look for confirmation language.
Decline / reject — the loop closes negatively, usually with a reason. The reason is frequently the target of a "why" question.
Defer — the loop stays open to a future point ("I'll confirm by Friday," "let me check with the team"). Deferral is a common correct answer that candidates miss by forcing a grant/decline binary.
Condition — the loop closes affirmatively if something is met ("yes, provided the budget is approved first"). The condition is a high-frequency detail-question target.
Counter — the loop is met with a modified version of the original ("Tuesday doesn't work, but Wednesday does"). The changed element is the tested element.

Naming the move explicitly as you read the reply — "this is a conditional grant," "this is a deferral" — is the single most effective habit for this item type, because it forces the cross-message connection to be made at reading time rather than reconstructed at question time.

The three cross-message question patterns

Pattern 1 — The response-classification question

"How does [second writer] respond to [first writer]'s request?" The answer choices are paraphrases of the five response moves. If you named the move while reading, this is a direct match. If you did not, you are re-reading both messages under time pressure.

Pattern 2 — The condition-or-reason question

"What must happen before [second writer] can approve?" / "Why does [second writer] decline?" The answer lives in the condition or reason attached to the response move. Candidates who caught the move but not its attached qualifier miss these.

Pattern 3 — The unresolved-element question

"What does [second writer] NOT address?" / "What remains to be decided?" The answer is the part of the first message's intent that the reply left open. This pattern specifically rewards holding the full first-message intent, because the trap is an element the reply mentioned in passing but did not actually resolve.

The eight-week routine

Weeks 1–2 — Intent extraction. Read only first messages and state the opening intent in one sentence and the exact action/problem/proposal/question at its core. Build speed and precision.
Weeks 3–4 — Move naming. Add second messages and name the response move explicitly before reading the questions. Track whether the named move matches the correct answer to Pattern 1 questions.
Weeks 5–6 — Qualifier capture. Drill catching the condition or reason attached to each move, targeting Pattern 2 questions.
Weeks 7–8 — Full integration. Run complete email-and-reply sets under timed conditions, including Pattern 3 unresolved-element questions, and push cross-message accuracy toward the high-70s ceiling.

The measurable target is closing the gap between your cross-message accuracy and your single-message accuracy — when they converge, the tracking habit has taken hold. For the connector-level reading precision that supports intent parsing, see the reading Part Five connector-word selection guide, and for cross-passage number verification that often accompanies these sets, see the numerical figure cross-reference verification guide.

The takeaway

Email-and-reply sets are not two passages — they are one loop opened and closed. Hold the first message's intent as the active reference, name the reply's move against it as you read, and catch the qualifier attached to that move. Do those three things and the cross-message questions become retrieval; skip them and every one of them becomes a re-read against the clock.