Use the label that matches the public form.
MapMyStaff Help Centre
Explain the issue with enough context to make it understandable.
Indicate where and when the behavior appears, what you expected, what you observed and any relevant recent changes. Do not add unnecessary sensitive information.
01Gather context
The information that helps explain the issue
Send only what is necessary. Not every item is required in every situation.
Specify what is disrupted and whether a temporary workaround exists.
Explain what should have happened in the journey.
Include the exact message without unnecessary interpretation.
List the exact actions that lead to the behaviour.
Indicate the article reviewed, the targeted test, and its result.
02Write the message
Describe the facts in order
A short, precise message is enough: context, expected result, observed result, useful steps and checks already made.
Template to copy into the Message field
Replace only the text in brackets with the necessary information.
Page or module: [where the issue appears]
Approximate time: [date and time]
Expected result: [what should have happened]
Observed result: [what happened + exact message]
Non-sensitive reference: [if one exists]
Recent changes or checks: [relevant items]Preserve evidence without assuming an attachment
The current contact form does not support direct file uploads. Keep a sanitized screenshot and send it only according to the instructions and through the channel specified by the support team if they request it.
03Protect data
Send only what is necessary
Never send a password, authentication code, API key, token, full card number or unnecessary personal information.
Keep in the case file
- The exact message and the steps in order.
- A non-sensitive identifier.
- A sanitized screenshot kept on your side.
- The articles, tests, and changes already completed.
Never send
- Your password or an authentication code.
- A key, token, or full payment-card number.
- Unnecessary personal or medical data.
- An unmasked screenshot.
When to choose “Security or privacy”
This subject may be appropriate for unexpected access, possible data exposure, a potentially compromised secret or identifier, or unusual permission or visibility. These signs justify reporting the situation, but do not by themselves prove that an incident is confirmed.
Review the privacy policy →04Review and send
Check the message one last time
Make sure expected and observed behavior are distinct, the steps are understandable and no secret or unnecessary information is included.
Final checklist
- The subject matches the content.
- Expected and observed results are clearly separated.
- The steps are in order.
- The impact and current status are described.
Protection and context
- The checks already performed are mentioned.
- The request contains no secrets.
- Only necessary data is included.
- The screenshot remains stored on your side until transmission instructions are provided.