Keep multi-part customer requests from losing one open item

Separate the requests before drafting a reply

Read the whole message once before responding. Look for separate outcomes the customer wants, not just question marks. A sentence such as “Please update the billing contact and send the revised schedule” contains two tasks, even though it is written as one sentence.

Write each item in plain language and keep it narrow enough to answer with a clear result. Avoid combining unrelated requests under labels such as “account issue.” If a detail is ambiguous, record that as a question to clarify rather than assuming what the customer meant.

Customer message: “Can you confirm whether the revised schedule is ready, change the billing contact, and tell me when the replacement will ship?”
Separate items:
1. Confirm whether the revised schedule is ready.
2. Change the billing contact, after confirming the requested contact details.
3. Provide the replacement shipping timing, if available.

Assign one owner to each item

For every request, name the person responsible for getting it to an answer. An owner may need to ask another colleague for information, but one person should still keep track of the item and communicate its status to the customer. Without a clear owner, “someone is checking” can mean nobody knows who should follow up.

If your team uses a shared note or task process, record the customer or thread, the item, its owner, and its status there. Keep the note concise and accessible to the people who need it. Follow your organization’s rules for where customer information may be stored.

• Use a person’s name or agreed team role, not “team” alone.
• If ownership changes, update the record and tell the new owner what remains to be done.
• Do not mark an item complete just because you forwarded it to someone else.

Use statuses that distinguish done from waiting

For a lightweight process, use two customer-facing states: “answered” and “pending.” Mark an item answered only when the requested information or action has been provided and checked. Use pending when you are waiting for a colleague, a customer clarification, or another necessary step.

For your own follow-up, add a short reason beside pending, such as “waiting for confirmed shipment timing.” If there is a specific next update date, record it. Do not promise a date you cannot support; if you do not know when you will have an answer, say that you will follow up when you have a confirmed update.

Check the whole set before sending

Before replying, compare your draft with the original list. Each item should have an owner and a current status. Verify names, dates, contact details, and any commitments against the original message and the relevant information available to you. An answer that sounds complete is not necessarily correct.

If a request cannot yet be answered, state what is missing or being checked. If the customer needs to provide a detail, ask for that detail directly. Avoid burying an unresolved item under a general closing such as “Let me know if you need anything else”; the customer should not have to infer that part of the request is still open.

Quick check before sending:
[ ] Every separate request appears in my list.
[ ] Each item has one owner.
[ ] Each item is marked answered or pending.
[ ] Any pending item says what is awaited and what happens next.
[ ] The reply does not promise an unconfirmed result or date.

Make the unresolved work visible to the customer

Use a short recap near the end of the reply. Label completed items as answered and open items as pending, in language the customer can understand. Include the next step and responsible contact where useful. This lets the customer see that an unanswered question has not been overlooked, while avoiding the impression that it has already been resolved.

A recap should reflect the actual state when you send it. If one answer changes before the message goes out, update both your tracking note and the recap. Keep the reply in the existing thread when appropriate so the customer can connect the summary to the original request.

To: [customer@example.com]
Subject: Re: [request subject]

Hello [customer name],

Answered: The revised schedule is ready. [Attach or identify the correct schedule.]
Answered: The billing contact has been updated to [confirmed contact].
Pending: I’m checking the replacement shipping timing with [owner or team]. I’ll send you an update when that timing is confirmed.

Regards,
[Your name]

Close items deliberately

After sending the recap, update each item’s status rather than treating the email as one finished task. Leave unresolved items pending and make sure their owners know the next action. When an answer arrives, verify it, send it to the customer, and then mark that specific item answered.

The process has worked when you can point to every original request and see its owner and status, and the customer can tell which parts are complete and which are not. If an item has no owner or no credible next step, it is still open—make that gap explicit and resolve the handoff.