A customer may forward a support email to a partner, an assistant, or a family member. The forward is often meant to be helpful, and the new recipient may reply with useful information. The support team still has to notice that the person writing is not the account holder. A re-verification step keeps the conversation moving without exposing the account.
This guide is for email support teams that handle account, billing, or personal-data cases. It explains how to spot a forwarded thread, how to verify the new sender, and how to record permission. The process should be short enough for a frontline agent and clear enough for a privacy reviewer. It also covers the records that show who approved the contact and what they were allowed to receive.
Spot the forward
Look for a changed sender address, a new signature, or a quoted header that names a different recipient. A message that begins with "forwarding this for my sister" is an obvious signal. A message that simply arrives from a new address with no explanation is a quieter one. Both deserve the same check.
Check the thread history before replying to the new address. The original case may have been verified with the account holder, but that verification does not automatically cover the new sender. Treat the new address as a new correspondent. The identity verification workflow explains why the check follows the person, not the thread.
Do not confirm sensitive details just because the sender can quote them. A forwarded message contains enough context to sound convincing. The quoted text is evidence that a message existed, not evidence that the sender is authorized. Keep the reply minimal until verification is complete.
Verify the new sender
Ask the new sender for their name and their relationship to the account holder. Record the answer in the case rather than only in the email thread. If the relationship is unclear, ask a direct question about who authorized the contact. A vague answer is a reason to pause, not a reason to guess.
Use the verification method that fits the case risk. A low-risk delivery update may need only a confirmation from the account holder, while a billing or access case may need a code or a call. Follow the policy for the case type. Do not lower the standard because the request sounds routine.
Contact the original account holder through the verified channel on file. Ask whether the third party is allowed to discuss the case and what information they may receive. Record the answer with the date and the channel. The third party contact boundary guide covers the permission levels.
Keep the first reply minimal
Acknowledge the forward without repeating account details. A short reply that says the team received the message and is checking authorization is enough. Do not include balances, addresses, order numbers, or case outcomes. The new sender has not earned access yet.
Set a time by which the customer will hear back. A clear window reduces the chance that the sender will keep forwarding messages to force a response. Record the window in the case. If verification takes longer, send an update rather than letting the window pass.
Avoid asking the new sender to send more documents than necessary. A request for an ID copy can create a new privacy risk if the sender is not authorized. Ask only for what the verification policy requires. The support record minimization guide offers a useful test for each field.
Record the permission level
Write down what the third party may do, not just that they may contact the team. The levels may include receiving status updates, providing information, or making a change request. Each level should have its own label. A single "authorized" flag is too blunt for a real case.
Name the account holder who gave permission and the date it was given. If the permission came through a call, record the call reference. If it came through a message, save the message. A later reviewer should be able to trace the permission to its source.
Set an expiry or review date for the permission. A one-time handoff is different from an ongoing arrangement. Record which one applies. If the customer did not specify, use the shorter default and confirm before extending it.
Handle a refused forward
If the account holder does not authorize the third party, tell the new sender only that the team cannot discuss the case. Do not explain the account holder's reasons or disclose that a refusal occurred. Keep the message short and neutral. The privacy request routing guide shows how to redirect without confirming details.
Continue the case with the verified account holder. Do not let the refused forward stall the original request. Send the account holder a note that the team received a third-party message and is continuing through the verified channel. Record the attempt.
If the new sender claims to be the account holder, restart verification from the beginning. A changed address alone does not prove identity. Use the approved method and document the result. A confident tone is not a substitute for a check.
Review the pattern
Count forwarded threads by case type and by team. A cluster may point to a confusing reply template that invites sharing. A template that says "share this with anyone who needs it" is a privacy problem, not a convenience. Fix the wording at the source.
Check whether agents are replying to the new sender before verification. Sample a small set of forwarded threads each month and look for early disclosure. Give feedback on the specific sentence that leaked, not just the outcome. The email thread fragmentation study offers a related measurement approach.
Update the email template when the pattern repeats. Add a short line that says the team may need to verify anyone new on the thread. Keep the line friendly and specific. A warning that sounds like a legal notice will discourage the helpful handoff the customer intended.
A forwarded support email is a normal part of modern customer care. The team should accept the handoff without treating the new sender as the account holder. Verify the person, keep the first reply small, and record the permission. That sequence protects the customer and still lets the case move.
