What to Redact Before Sending a Procurement Support Screenshot
A screenshot can make a website problem easier to explain, especially when you are working between material requests, supplier offers, and project deadlines. It can also reveal more than the error: a client name, a delivery address, or a confidential budget may be visible in the background. Before sending an image, separate the details needed to understand the problem from information that does not belong in the conversation.
Matravo is a construction and landscape material RFQ-to-offer marketplace. When reporting a website or account issue, your goal is to provide a clear diagnostic record, not your entire procurement file. A carefully cropped screenshot and a short written explanation are a useful starting point.
1. Keep the evidence that explains the problem
Start with three questions: What were you trying to do? What happened instead? What did you expect to happen? For an access problem, say whether you were creating an account or signing in. For a problem involving a material request or an offer, include the relevant reference so support has a clear identifier to work with.
Keep the exact error message visible when possible. Avoid replacing it with a summary such as “the website is broken,” which removes useful context. Write down the time of the problem and the page address as well. If the time could be ambiguous, add your time zone.
- The action you attempted and the page involved.
- The exact error message, copied accurately.
- The date and time the problem occurred.
- The request or offer reference, when relevant.
- Your account email, provided to support for an account question.
These details can be written beside the screenshot. They do not all need to remain visible inside the image.
2. Remove project information that is not needed
Review the whole image, not just the error box. A procurement page may show a private project name, a site address, internal cost targets, buyer notes, or commercial details from an unrelated offer. Hide those details unless a specific item is necessary to explain the issue. Keep confidential files out of the support conversation.
For example, if a page fails to open, support generally needs the page address and error rather than a readable schedule of materials. If an offer display looks wrong, keep the affected area and its reference while removing unrelated project information. Describe the symptom in words rather than exposing an entire commercial discussion.
Also check browser tabs, bookmarks, desktop notifications, and anything visible around the page. A screenshot taken on a shared work device may accidentally include another project or a colleague’s contact details. Cropping to the relevant area reduces that distraction without losing the evidence you intended to send.
3. Exclude credentials and inspect the final image
Never send your password, verification code, recovery code, or full payment-card details. These are not troubleshooting evidence. Matravo support can investigate an account question without asking for those secrets. Do not include them in a screenshot, a copied error report, or the message accompanying an image.
Keep the page address as useful context, but inspect it before copying. If it contains a sign-in token, verification code, or another secret, remove that sensitive portion and explain that you have done so. An address should help identify the page, not provide access to an account.
- Crop away parts of the screen unrelated to the problem.
- Cover sensitive details with solid, opaque blocks rather than a translucent marker.
- Save a separate redacted image for sharing.
- Reopen that saved image and inspect it at a readable size.
Do not assume an editing preview is the file you will send. Check the actual attachment, including small text near the edges. If you cannot confidently remove a secret, send a written description instead.
4. Add mobile-browser details in writing
If the issue occurs on your phone, identify the device, operating system, and browser. Add version information if you can find it. Say which page was involved and whether the problem appeared when opening the page, entering information, or selecting a control. Those details communicate more than “it does not work on mobile.”
Matravo’s iOS and Android applications are in development. Continue using the website for now; official store links will be shared when the applications are available. Describe the problem as a website issue in the browser you actually used.
A concise report might read: “I was signing in on the Matravo website using this phone and browser. After selecting Sign in, I saw the following message at this time. I expected to reach my account.” Add the exact message, page address, and device information. If no error appeared, say so rather than guessing what failed.
5. Send a focused report, then return to account access
Use the support options on the Matravo website. Attach the checked image and explain the action, result, and expected outcome. Include your account email for an account question, or share your email if you want the team to contact you. Avoid adding unrelated documents just to make the report look complete.
The Matravo AI assistant is automated, and you can ask to speak to a person at any time. Ask for the support team when the matter requires an account-specific decision, concerns billing, or needs a verified answer. Replies depend on the team’s availability.
When you are ready to continue, return to the website’s Create account or Sign in route. Create an account with an email address you control and accurate business information, or sign in if you already have one. If access still fails, ask support for assistance using the focused, redacted evidence you prepared.
