Skip to content
Troubleshooting and support

Contacting us

What to send, where to send it, and what lets us answer on the first reply rather than the third.

Updated

support@vendorica.com reaches the team. You can also open support from the Help menu in the top bar of the app.

Most slow support threads are slow because the first message is missing one of these. Sending them up front usually turns three exchanges into one:

  • What you were trying to do, in your words. Not the error — the goal.
  • Where you were: the page, and the URL if you still have it.
  • Which record, by its display ID or name. “The vendor register” is a page; “vendor V-0142” is a thing we can look at.
  • What happened instead, including the exact wording of any message.
  • When, roughly, with your timezone. It lets us find the request in our logs.
  • Your organization name, if you belong to more than one.

A screenshot is worth all of the above put together, when the problem is visible.

We will never ask for your password, and we will never ask you to share an API key over email. If you receive a message claiming to be from Vendorica support asking for either, it is not us — please forward it to support@vendorica.com.

Security reports go to security@vendorica.com rather than to support, so they reach the right people immediately.

Tell us. The most useful version is the problem rather than the proposed solution — “I cannot show my auditor which controls changed last quarter” is far more actionable than “please add a changelog tab”, because it leaves us free to solve it in a way that fits the rest of the product.

Also support@ — and please say which page. Documentation that is wrong is worse than documentation that is missing, and we would rather hear about it than have it sit there.