Writing an effective support email

Last updated: August 21, 2026

The clearer your email, the faster we can help.

Subject line

Make it specific enough that someone scanning a list of issues knows what's wrong without opening the issue. A good subject names what's affected and what's happening.

Strong subjects:

  • Ferritin results not filing to patient record

  • Automation stopped running overnight, no output

  • HbA1c results incorrect for diabetic patients

  • Bot hasn't run since Tuesday, backlog building

Weak subjects to avoid:

  • Query

  • Ferritin

  • Help needed

  • Urgent

A one-word subject doesn't tell us enough. Naming the lab, or the result type does.

What to include in the email

  1. What's happening

  2. When it started

  3. How many patients or records are affected, if known

  4. One example, so we can trace it

A few things that help

  • One issue per email, rather than several problems in one message

  • Keep identifiers out of the email. Patient names, NHS numbers, and dates of birth should not be shared with SP Automate.

  • Start fresh for a new issue. Reply to an old thread only if it's genuinely the same problem