Information Support Teams Usually Ask For

Account details that help identify your enquiry

Start by identifying the account associated with the problem. The email address registered to your mSpy account is a useful reference because it helps distinguish one account enquiry from another. If the issue concerns access to the online dashboard, explain whether you cannot sign in, cannot locate expected account information or encounter a problem after signing in. These are different situations and should not be combined into a vague statement that the account is not working.

Keep the distinction between identification and authentication clear. A support enquiry may require an account reference, but that does not mean you should send your password or other sensitive authentication information in an ordinary message. If a representative requests additional verification, ask which information is required and use an appropriate official channel. Never include payment credentials or security answers in a general problem description.

• The email address associated with the account.
• A general description of the account access problem.
• The approximate date and time the issue began.
• Any relevant support reference from an earlier enquiry.

Device information and operating system

Device details help establish whether an issue might relate to compatibility or feature availability. Record whether the relevant phone uses Android or iOS and note its operating system version. If you do not know the version, check the phone's own system information rather than estimating it. Also identify whether the problem concerns the device itself, the online dashboard or the information displayed between them.

This distinction matters because mSpy feature availability varies with the operating system, version, plan and configuration. Some functions also require permissions on the monitored phone. A feature listed on the official website should not automatically be assumed to be available in every setup. Explain what you expected to see and what is actually available, then ask support to clarify compatibility for the particular device.

• Device manufacturer and model, if known.
• Android or iOS.
• Operating system version.
• Whether the issue concerns the phone or online dashboard.

A precise account of the problem

Support teams need observations rather than conclusions. Instead of saying that monitoring is broken, identify the particular function involved and describe what happened. For example, explain that a dashboard section does not display the information you expected, or that an account access attempt produces an unexpected result. Include the approximate time and whether the behaviour has happened once or repeatedly.

The phrase information support asks for should be understood as a request for relevant context, not permission to disclose everything available on a device. Distinguish between information you have directly observed and assumptions about the cause. If a function previously appeared to work but no longer does, mention that change. Do not claim that a technical fault has been established before support has examined the available information.

Troubleshooting and feature-specific context

Write down any reasonable checks already completed and their outcomes. This might include confirming that you are using the correct account email, checking whether the dashboard displays an account message or noting whether the phone's operating system has changed. Avoid repeating a troubleshooting action simply because it appears on a generic checklist. Ask support whether a proposed check is appropriate for your particular device and configuration.

For a feature-related enquiry, identify the function and explain what you expected it to do. GPS location tracking, route history, geofence alerts, supported messaging information and website blockers are not interchangeable features. More intrusive functions, such as keystroke logging, periodic screen capture, live screen streaming and call recording, require particular care. Their use should be proportionate, age-appropriate and legally permitted. Ask about permissions, limitations and appropriate alternatives rather than assuming availability.

Privacy, consent and the final information check

Before submitting an enquiry, check that every device mentioned is one you are legally entitled to monitor. For a parent or legal guardian, responsible use includes an open, age-appropriate conversation with the child about monitoring and the reasons for it. An employer should have a written policy and provide notice to employees before monitoring company-owned devices. Consent and transparency are not optional editorial details; they are important parts of responsible device supervision.

Laws differ between countries and can impose different requirements for collecting communications, recordings and device activity. Check local rules and seek qualified legal guidance where necessary. Send only the information needed to explain the issue, and remove unrelated personal details from any supporting material. Before submitting, review the account reference, device information, timeline and description for accuracy. Your next step is to assemble these details into one concise enquiry and check the official website for current support guidance.

Questions readers ask