How to Triage Reader Emails: Tips, Complaints and Press Releases

Task: Separate the Inbox into Editorial Work

A shared newsroom inbox can contain a useful account of a public meeting, a complaint about a published sentence, an unsolicited product announcement and a reader asking when the next issue will arrive. They may arrive within minutes of one another. Treating them as one general correspondence queue makes it easy to overlook a reporting lead or leave a correction unanswered.

The triage task is to identify what kind of editorial work each message requires. Four categories provide a workable first pass: reporting tip, complaint or correction request, press release or promotional pitch, and routine correspondence. A fifth holding category, needs human review, covers messages that cannot safely be classified from their subject line or opening paragraph.

• Reporting tip: a claim, observation, document or lead that may warrant independent reporting.
• Complaint or correction: a challenge to something the publication has already printed or broadcast.
• Press release or pitch: material supplied to encourage coverage of an organization or event.
• Routine correspondence: subscription questions, general feedback and administrative messages.
• Needs human review: sensitive, ambiguous or potentially urgent material.

Inputs: Preserve the Message Before Summarizing It

Keep the original message, including its sender, subject, received time, attachments and full body. An AI-assisted draft should never become the only record of what arrived. A short summary can remove qualifications, change the apparent certainty of a claim or omit a sentence that explains how a source obtained information.

Before using an AI service, review the newsroom's rules for confidential sources and personal information. A reader may include a private phone number, an address, employment details or documents supplied on the condition that they remain confidential. Do not paste sensitive correspondence into an external service unless the newsroom has established that the service and its settings are appropriate for that material.

• Retain the original email and attachments in the newsroom's approved account.
• Separate public information from confidential source details.
• Remove unnecessary personal information before processing permitted material.
• Record the received date and the person responsible for the next action.

Tool Steps: Use AI for Classification and Drafting

For routine, non-sensitive correspondence, provide the tool with the message text and a fixed set of category definitions. Ask it to suggest one category, identify the sentence that supports the classification and summarize the requested action in no more than two sentences. Instruct it to preserve uncertainty and to mark unclear messages for human review.

For example, an email stating that a town department has postponed a public meeting may be classified as a reporting tip. The useful summary is that the sender reports a postponement and identifies the department. The summary does not establish that the meeting was formally postponed. A reporter still needs the department's notice, updated agenda or direct confirmation.

A second prompt can prepare a reply draft. Ask for a neutral acknowledgment, one clear next step and no promise of coverage or publication. For a correction complaint, the draft should acknowledge receipt and explain that the relevant material will be reviewed. It should not concede an error before an editor examines the record.

• Use the same category definitions for every batch.
• Require a short explanation for each proposed classification.
• Keep claims attributed to the sender.
• Ask for a draft reply separately from the classification.
• Send no message without a person's approval.

Human Checkpoint: Decide What Deserves Attention

A person must read every message that contains a serious allegation, a possible public safety issue, a correction request, a confidential source approach or an unfamiliar document. AI classification is an administrative suggestion, not a credibility assessment. A message may be promotional in tone and still contain a useful lead. A complaint may be angry and still identify a genuine factual error.

For reporting tips, identify the claim, the source's basis of knowledge and the evidence that could independently establish the relevant facts. Record what remains to be checked. For press releases, identify who benefits from the announcement, whether the event affects the publication's coverage area and whether another source can confirm the central claims.

For complaints, compare the challenged passage with the underlying reporting file, recording, document or published version. If an error is confirmed, follow the publication's corrections policy, including the appropriate wording, placement and update record. A reader's dissatisfaction alone does not establish that a correction is required, and an editor's familiarity with a story does not remove the need to inspect the evidence.

Known Failure: Categories Can Hide the Important Detail

The most consequential classification problem is a message that belongs in more than one category. A press release may identify a public contract that deserves scrutiny. A complaint may also introduce a new document. A routine-looking message may contain a time-sensitive tip in its final paragraph. A system instructed to select exactly one label can conceal these overlaps.

Use a primary category and an additional-action note when necessary. For example, label a message as a complaint and add a reporting follow-up if it includes evidence of a separate public issue. Do not allow a low-confidence classification to close the message automatically. An empty or uncertain summary is a reason to read the original, not a reason to discard it.

Author's Stopwatch Log and Slip Sheet

Stopwatch log: This entry is a recording template, not a reported timing result. For each newsroom repetition, record the date, number of messages, time spent on initial sorting, time spent on human review and time spent preparing replies. Keep the figures separate. A batch of 12 routine messages is not comparable to a batch containing source approaches and correction requests.

Slip Sheet: Record only a failure that an editor or reader actually identifies during a repeat of the procedure. Each entry should include the date, affected message category, original problem, resulting editorial action and any change made to the instructions. Do not turn a suspected omission into a confirmed failure. The next desk should begin by checking the needs-human-review queue and any unresolved correction requests.

Questions readers ask