Contact Details

What to Include in a Complaint

Writer Brief: What to Include in a Complaint

Canonical planned URL: https://contactdetails.co.za/guides/what-to-include-in-a-complaint/

URL level: 2   URL-path parent: https://contactdetails.co.za/guides/

1. Page Purpose

Strong supporting page that improves all complaint-page usefulness. The page should satisfy informational search intent for “what to include in a complaint” by giving a direct answer, explaining the safest official route and guiding users to related planned pages.

  • Search intent: Informational
  • Page type: Support Guide
  • Cluster: Ombudsman, Complaints, and Escalation Contacts

2. Target Reader

Users who have an unresolved issue and need to understand the correct complaint or escalation path for What to Include in a Complaint without using unsafe or unofficial routes.

3. Primary Keyword

what to include in a complaint

4. Secondary Keywords / Supporting Terms

  • complaint checklist South Africa
  • complaint information to prepare
  • what evidence to include in a complaint

5. Recommended H1

What to Include in a Complaint

6. Recommended Meta Title

Complaint Checklist | ContactDetails

7. Recommended Meta Description

Use this South African guide for what to include in a complaint, with official-source checks, safe complaint routing and related escalation pages.

8. Suggested Page Structure

H1: What to Include in a Complaint

  • H2: Quick answer: what to include in a complaint
  • H2: Complaint details and timeline
  • H2: Evidence, screenshots and documents
  • H2: Reference numbers and follow-up
  • H2: Information you should not share
  • H2: Safe official-source checks
  • H2: Related complaint routes
  • H2: FAQs
  • Suggested H3: What evidence should I keep?
  • Suggested H3: Should I include bank or card details?
  • Suggested H3: How should I follow up?

9. Section-by-Section Writing Guidance

Quick answer: what to include in a complaint

  • Open with a direct answer for users looking for what to include in a complaint.
  • State that users should verify exact contact details on the official provider, regulator, ombud, government or organisation website before acting.
  • Do not publish unverified phone numbers, email addresses, WhatsApp numbers, payment details or escalation steps.

Complaint details and timeline

  • Explain the normal order: contact the provider first, keep reference numbers and written records, then escalate to the relevant ombud, regulator or authority if unresolved.
  • Name the category of escalation route only where the official source supports it.
  • Do not imply ContactDetails.co.za can submit or resolve the complaint on the user’s behalf.

Evidence, screenshots and documents

  • List safe information the user may need, such as account/reference numbers, policy numbers, booking details or case numbers where relevant.
  • Add a clear warning not to share OTPs, passwords, PINs, full card details or banking passwords.
  • Tell users to keep screenshots, reference numbers and dates for follow-up or escalation.

Reference numbers and follow-up

  • Explain when a phone route is appropriate and when an online/self-service route may be safer or more efficient.
  • Warn users to confirm numbers on the official website and avoid numbers found in comments, adverts or unofficial directories.
  • Mention that users should never share OTPs, PINs, passwords, card details or banking passwords with anyone claiming to be support.

Information you should not share

  • List safe information the user may need, such as account/reference numbers, policy numbers, booking details or case numbers where relevant.
  • Add a clear warning not to share OTPs, passwords, PINs, full card details or banking passwords.
  • Tell users to keep screenshots, reference numbers and dates for follow-up or escalation.

Safe official-source checks

  • Cover the section in a practical, South African context for users searching for what to include in a complaint.
  • Keep the writing direct and source-led, with clear distinctions between support, complaints, fraud, escalation and self-service where relevant.
  • Do not add exact contact details, payment details or promises unless verified on the current official source.

Related complaint routes

  • Explain the normal order: contact the provider first, keep reference numbers and written records, then escalate to the relevant ombud, regulator or authority if unresolved.
  • Name the category of escalation route only where the official source supports it.
  • Do not imply ContactDetails.co.za can submit or resolve the complaint on the user’s behalf.

FAQs

  • Answer practical questions users are likely to ask before contacting the provider or authority.
  • Keep answers brief, source-led and safe; tell users to verify exact details on the official website.
  • Avoid publishing unverified phone numbers, email addresses, complaint forms or payment links in FAQ answers.

10. Internal Link Suggestions

11. Conversion / User Action Guidance

Help the user prepare a clear complaint before using an official provider, ombud or regulator route.

  • Encourage the user to verify exact details on the official website before calling, emailing, submitting a form, paying, clicking a link or sharing information.
  • Route the user to the safest next action: official support, self-service, complaint, escalation, fraud reporting, verification or a related planned page.
  • Do not imply that ContactDetails.co.za is the provider or can resolve the issue directly.

12. FAQ Suggestions

  • What evidence should I keep?
    Answer briefly for users researching what to include in a complaint, with source-led wording and no unverified contact details.
  • Should I include bank or card details?
    Answer briefly for users researching what to include in a complaint, with source-led wording and no unverified contact details.
  • How should I follow up?
    Answer briefly for users researching what to include in a complaint, with source-led wording and no unverified contact details.
  • How should users complain about What to Include in a Complaint?
    Explain the provider-first approach, keeping references and records, then escalating to the relevant official ombud or regulator if unresolved.
  • What proof should users keep?
    Recommend keeping dates, screenshots, case numbers, call references, emails and copies of submitted forms.

13. Content Notes

  • Source requirement: Use official ombud, regulator, government, scheme, provider or company pages. Do not rely on third-party directories for contact details.
  • Official source checks: Identify and verify the current official provider, regulator, ombud, government, municipality, scheme or company source before publication.
  • Do not invent phone numbers, email addresses, WhatsApp numbers, form URLs, payment details, banking details, emergency routes, fraud routes or escalation steps.
  • Do not treat third-party directories, search-result snippets, adverts, user comments or social posts as the source of truth.
  • Include scam warnings where users may face fake numbers, phishing, smishing, vishing, OTP theft, impersonation, refund scams, courier scams or payment-link scams.
  • Anti-cannibalisation: keep this page focused on its exact primary keyword and URL intent. Use internal links rather than repeating the full purpose of neighbouring pages.
  • Planning note: Strong supporting page that improves all complaint-page usefulness. | Controlled ombud/complaints expansion under existing /complaints/ and /guides/ sections. Source-gated pending live official verification.
  • Planning note: Controlled expansion under existing /complaints/ and /guides/ sections. Warn about fake ombud numbers, phishing, smishing, vishing, fake WhatsApp routes, fake complaint forms, altered banking details, upfront-fee scams, impersonation and OTP theft.
  • Planning note: Open with safe routing guidance. Do not publish phone numbers, email addresses, WhatsApp numbers, forms, complaint routes, payment details or escalation steps until verified on live official sources.
  • Planning note: Use official sources only for phone numbers, emails, WhatsApp routes, complaint forms, escalation steps, payment instructions and fraud/scam guidance.