Start with the right category

Get from the symptom to the right kind of help.

Technical trouble, account access, safety concerns, payment questions, and privacy requests need different evidence and different handling. Begin with the category that matches what you are trying to resolve.

Contact MicoCam Read the page

TechnicalCamera, audio, connection, or browser

AccountSign-in, profile, access, or data

Urgent safetyEnd contact first; use local emergency help for immediate danger

Self-service first

Solve common device and connection problems without exposing an account.

For a blank camera or silent microphone, check site permission, operating-system permission, and device selection. For freezing or dropped calls, reduce competing network use and keep the device on one stable connection.

Write down the symptom and the last successful step before changing settings. This makes it easier to tell whether the fix worked and gives support a reproducible path if the issue remains.

→Use the camera guide for blocked or wrong devices
→Use connection help for freezing, delay, or dropped calls
→Do not send passwords or one-time codes

Choose the owner

Safety, payment, privacy, and account actions need their own route.

End and block a harmful interaction before sending a safety report. For a payment question, collect the date, amount, status, and non-sensitive order reference. For a privacy or data request, use the account-data path so identity checks can be proportionate to the action.

Do not combine unrelated high-risk details into a general technical screenshot. A useful support message is narrow, factual, and directed to the team responsible for the next action.

→Separate a complaint from a formal data request
→Keep raw private chat or media out of general tickets
→Use local emergency resources for immediate danger

Support packet

What to prepare before contacting support

Enough context helps; unnecessary sensitive data creates risk.

01
Your issue category and the action you were trying to complete.
02
The device, operating system, browser, and approximate time.
03
What you expected, what happened, and the last step that worked.
04
A cropped screenshot only if it adds necessary context.
05
A non-sensitive order or case reference when relevant.
06
No password, verification code, private media, or full payment details.

Clear answers

Finding help

Where do I report harmful behavior?

End contact first, then use the visible report and block controls. Use local emergency resources for immediate danger.

What should a technical report include?

Include device, operating system, browser version, approximate time, symptom, and reproduction steps.

Can support ask for my password?

Do not provide a password or one-time verification code. Use only the authenticated recovery or account flow presented by the service.

Bring the right context

A clear issue reaches the right solution faster.

Describe the job, the symptom, and the last successful step—without handing over information support does not need.

Contact MicoCam