A well-prepared ticket reduces back-and-forth and helps the support team route the issue correctly. It does not need technical language. Clear sequence, context and impact are more useful than guessing the cause.
Write a specific subject
Describe the affected area and result, for example “Checkout rejects valid postcode after delivery selection” rather than “Urgent—nothing works”. Keep one main issue per ticket where possible so progress and resolution remain clear.
Explain the sequence
State the page, product, device or service involved; the steps taken; what you expected; and what occurred instead. Include the approximate date and time, whether the issue repeats and how it affects customers or work.
Attach safe evidence
A screenshot can help when it excludes unrelated personal or confidential information. Include exact error wording where possible. Never place passwords, complete payment-card details, secret keys or identity documents in a standard ticket.
Keep replies in the ticket
Respond through the secure portal so context and attachments remain together. If circumstances change or the problem is resolved, add a short update. Open a new ticket when a separate issue would require a different owner or outcome.
Practical checklist
- Specific issue and affected area.
- Expected and actual result.
- Steps and approximate time.
- Device, browser or order reference where relevant.
- Sanitised screenshot or exact error.
- No passwords or full payment credentials.
Common mistakes to avoid
Avoid submitting the same issue through several channels, marking every request urgent, sharing secrets or replying to a different ticket because it happens to be open.
Your next step
Open the BROel Support Portal, choose the closest relevant category and use this checklist. Keep the ticket reference for future replies.