The difference between a problem resolved in one exchange and one that takes four is almost always the first message. This is what to put in it.
The five things we need
- What you were trying to do. The goal, not the mechanism. "I need the contact form to email sales@" tells us more than "the SMTP setting is broken".
- What actually happened. The exact error text, copied rather than paraphrased. Error messages are precise; summaries of them are not.
- Where. The full address of the page, the name of the service, the mailbox, the domain. "The site" is ambiguous on an account with three of them.
- When it started, and what changed around then. A plugin update, a password change, a new device, an office move. This single detail resolves more tickets than any other.
- Who it affects. Only you, everyone in the office, or your customers. This tells us how to prioritise it and often tells us where the fault is.
A worked example
Weak: "Email is broken, please fix."
Strong: "Since about 9am today, outgoing mail from accounts@ourdomain.com fails on Outlook on two PCs with the error 'Cannot send: 550 relay not permitted'. Incoming mail is fine. Webmail sends fine from the same address. Nothing changed that we know of except a Windows update on Tuesday. Affects two of five staff."
The second one can be answered immediately. The first cannot be answered at all without three more messages.
Things that slow a ticket down
- Screenshots of the whole screen where the error text is unreadable. Copy the text as well.
- Several unrelated problems in one ticket. They get different owners and different timelines. Open one ticket per issue.
- Replying to an old, closed ticket about something new. It inherits the old context and the old priority.
- "It still does not work" with no detail about what you tried and what happened this time.
Say what you have already ruled out
If you have tested from another network, tried a different browser, or restarted the device, say so. Otherwise the first reply will ask you to do exactly those things, and a day disappears.
Choose the department correctly
Billing questions to billing, technical faults to technical. A ticket in the wrong queue gets moved, and the move costs time.
After you send it
Leave the ticket open and reply to it rather than opening a second one about the same problem. Duplicate tickets split the history and slow everything down. If the situation gets worse or the impact grows, say so in a reply — that is genuinely useful information, and it is how a ticket gets escalated.
