Should You Share a Verification Code with Procurement Account Support?

Should You Share a Verification Code with Procurement Account Support?

No. Do not share your verification code with procurement account support. The same applies to passwords and recovery codes. If you cannot register or sign in, useful troubleshooting information describes the problem; it does not give someone else the credentials needed to access your account.

For a buyer arranging construction or landscape materials, an access problem can interrupt request preparation or offer review. A clear support message helps keep the discussion focused. Here is what to include, what to leave out, and how to separate account troubleshooting from the procurement conversation itself.

1. Describe the access problem, not your credentials

Matravo is an RFQ-to-offer marketplace for construction and landscape materials. It is not a material seller or shopping cart. Your account is part of the process of preparing a request and considering supplier offers, so an access question should identify which step is blocked.

Start with the Matravo website. Choose Create account if you have not registered, using an email address you control and accurate business information. If you already have an account, choose Sign in. When contacting support, say explicitly which of these actions you were attempting.

“I cannot access my account” is a starting point, but it leaves several possibilities open. Explain whether a page failed to open, a verification message did not arrive, or sign-in produced an error. Report what you saw rather than guessing at an underlying technical cause.

For example, a missing verification message and an error after entering account details are different observations. Keeping that distinction clear gives support a more useful account of the interruption without requiring your code or password.

2. Send a compact troubleshooting record

The support team can investigate an account question using identifying and diagnostic information. Gather the following before sending your message:

  • Account email: the email address associated with your account or registration attempt.
  • Page address: the address of the page where the problem occurred.
  • Time: when you encountered the problem, with your time zone if useful.
  • Exact error message: the wording displayed, rather than only a summary.
  • Action and expectation: what you tried to do and what you expected to happen.

If the question concerns a particular request or offer, include its reference when relevant. For a straightforward registration problem, an unrelated offer history is unlikely to explain the failed step. Keep the initial report narrow enough that the main issue is easy to find.

A practical message might read: “I was trying to sign in using my account email. At the time below, the sign-in page displayed the error quoted below. I expected to reach my account. Please help me understand the next step.” Add the actual details, but no credentials.

3. Leave secrets and unrelated project details out

Never send your password, verification code, recovery code, or full payment-card details. The support team can investigate your account question without asking for those secrets. A verification code is not a request reference, and a recovery code is not troubleshooting evidence.

If someone asks for a code in a conversation presented as support, do not provide it. Use the support options on the Matravo website to raise the question instead. You do not need to test whether sharing a secret would make troubleshooting faster.

Screenshots deserve the same care as written messages. Remove confidential project information before sharing them. Check the whole image, not just the error box: surrounding content may show internal project names, commercial notes, or information unrelated to the access problem.

When a short written description and the exact error wording explain the issue, there is no need to add a project document merely for context. Keep confidential files out of the conversation and provide only the information needed to explain the blocked action.

4. Separate account support from supplier discussions

An account-access issue belongs with support, not in a material negotiation. Suppliers discussing quantities, specifications, or offer terms do not need your sign-in credentials. Keep the procurement discussion about the request and use support for the problem preventing account access.

On Matravo, web chat is available on the request before an offer: entitled sellers start threads, and buyers reply to existing threads. Opening phone or contact details after a deal is a separate rule; it is not the gate for web chat.

The Matravo AI assistant is automated. You can ask to speak to a person at any time. For account-specific decisions, billing questions, or an answer that needs verification, ask for the support team. Share your email if you want the team to contact you.

The team replies according to its availability. A clear report provides useful context, but it should not be treated as a promise of an immediate reply or resolution.

5. Return to the existing account route

Before sending your support message, check that it explains the attempted action, observed result, and expected result. Confirm that your account email, page address, time, and error wording are included, while secrets and confidential project information are excluded.

When you are ready to continue, return to the Matravo website and choose Sign in. If you have not registered, choose Create account instead. Once you have access, continue preparing your material request or reviewing offers, keeping account troubleshooting separate from the information suppliers need to discuss your requirements.

More posts