Contact Details

What Not To Share With Customer Care

Writer Brief: What Not To Share With Customer Care

Canonical planned URL: https://contactdetails.co.za/verification/what-not-to-share-with-customer-care/

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

1. Page Purpose

Important safety content for warning users not to share OTPs, PINs, passwords or unnecessary identity information. The page should satisfy informational / safety search intent for “what not to share with customer care” by giving a direct answer, explaining the safest official route and guiding users to related planned pages.

  • Search intent: Informational / Safety
  • Page type: Problem-Solving Guide
  • Cluster: Verification, Scam Prevention, and Trust

2. Target Reader

Users who need to verify a contact route, avoid scams or respond safely to a suspected fraud, fake number, phishing, smishing, vishing or impersonation risk.

3. Primary Keyword

what not to share with customer care

4. Secondary Keywords / Supporting Terms

  • what not to share with customer care

5. Recommended H1

What Not To Share With Customer Care

6. Recommended Meta Title

What Not To Share With Customer Care | ContactDetails

7. Recommended Meta Description

Find what not to share with customer care with official-source checks, safe support routes, scam warnings and related South African contact pages.

8. Suggested Page Structure

H1: What Not To Share With Customer Care

  • H2: Direct answer
  • H2: When to use this route
  • H2: Step-by-step guidance
  • H2: Official-source verification checklist
  • H2: What not to share
  • H2: Related contact pages
  • H2: FAQs
  • Suggested H3: Official source checklist
  • Suggested H3: details users must not share
  • Suggested H3: related pages
  • Suggested H3: escalation options where relevant

9. Section-by-Section Writing Guidance

Direct answer

  • Open with a direct answer for users looking for what not to share with customer care.
  • 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.

When to use this route

  • Cover the section in a practical, South African context for users searching for what not to share with customer care.
  • 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.

Step-by-step guidance

  • Cover the section in a practical, South African context for users searching for what not to share with customer care.
  • 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.

Official-source verification checklist

  • Prioritise urgent safety guidance and verification before the user clicks links, pays money or shares personal information.
  • Include warnings about fake numbers, phishing, smishing, vishing, OTP theft, impersonation and payment-link scams where relevant.
  • For emergency, bank fraud or identity-theft scenarios, route users to the official emergency/fraud channel after live verification.

What not to share

  • Cover the section in a practical, South African context for users searching for what not to share with customer care.
  • 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 contact pages

  • Link to relevant planned pages that help the user move from What Not To Share With Customer Care to the next logical support, complaint, fraud, payment, cancellation or verification topic.
  • Use natural anchor text and avoid self-links or unrelated SEO-only links.
  • Prioritise parent hub links, closely related sibling pages and safety/verification pages where appropriate.

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

Verify the contact route before calling, paying or sharing personal information.

  • 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 is the best way to use the What Not To Share With Customer Care page?
    Explain that users should identify their issue first, then use the safest official route or related planned page.
  • Where should users verify what not to share with customer care?
    Tell users to verify exact contact details on the official provider, regulator, ombud, government or organisation website before acting.
  • What details should users prepare before contacting support?
    Mention safe details such as account/reference numbers, dates and issue summaries; warn against sharing sensitive credentials.
  • What should users do if they cannot get help?
    Explain the provider-first process and the relevant escalation/complaints path if unresolved.

13. Content Notes

  • Source requirement: Use official organisation, regulator, ombud, government or provider 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: Important safety content for warning users not to share OTPs, PINs, passwords or unnecessary identity information. | Controlled expansion: source-gated core contact-directory row; no new top-level section created.
  • Planning note: Clear, direct, neutral, trust-first. Do not invent contact details or imply ContactDetails.co.za is the provider.
  • Planning note: Controlled expansion row; include a direct-answer opening, official-source verification warning, and scam/safety guidance where relevant.
  • Planning note: Use official sources only for exact phone numbers, emails, WhatsApp numbers, complaint routes, fraud/scam guidance, emergency routes and payment instructions.