Reference

Contact us

There are three ways to reach NeoSQL. For problems in the app, the bug report panel inside the app is fastest; for anything else, use the contact dialog on the website or email. First check whether FAQ or Troubleshooting already has the answer.

Where to send what

InquiryWhereSign-in
Errors in the app, something behaving oddlyThe Report a bug button in the app header (the bug report panel)Not needed
Feature requests, how-to questions, purchasing and contractsThe Contact Us dialog on the websiteNot needed
Enterprise adoption, volume licensingThe Contact us button on the website's pricing pageNot needed
You cannot open the app or use the dialogEmail ops@unvus.com or unvus.io@gmail.comNot needed

Reporting a bug from the app

Send problems in the app with the Bug report panel. The app version, web or desktop, OS, current screen, DBMS, and recent error log are filled in already, so you only need to write what you were doing and what happened. You can attach screenshots too.

  • It works in the desktop app without signing in.
  • Before sending, you can read, edit, or remove the error log and environment details that go with it. The error log can contain SQL statements or table names, so read it through.
  • If sending fails, the panel stays open and shows why. Sending again does not create a duplicate report.

Contacting us from the website

Open the Contact Us dialog from these places on the website.

PlaceWhat opens it
Bottom of the website's home pageThe Contact Us button
Enterprise section at the bottom of the pricing pageThe Contact us button
End of the FAQ on the education plan pageThe Contact us → link
  1. Click a button or link above to open the Contact Us dialog.
  2. Fill in the Subject field, the Email field, and the Message field. These three are required. The reply goes to the email you enter. The Phone field can be left empty.
  3. If needed, attach images, PDF, ZIP, text, CSV, log, SQL, JSON, or XML files under Attachments. Up to 10MB per file and 25MB in total.
  4. Click the Send button. When it is received, a Your inquiry has been submitted. We'll get back to you shortly. notification appears.
  • Sending goes through an automated-input check. If a Security verification failed. Please refresh the page and try again. notification appears, refresh the page as it says and send again.
  • If a Failed to send. Please try again later. notification appears, send again later or use email.
  • Closing the dialog discards what you wrote. Write long messages elsewhere first and paste them in.

Contacting us by email

Send to ops@unvus.com or unvus.io@gmail.com. These are the addresses shown in the company details at the bottom of the website and in the Terms and Privacy Policy. If a message to one address bounces, send it to the other. Use these addresses too when you cannot open the app to use the bug report panel.

Enterprise inquiries

If you need adoption sized to your organization, volume licensing, or dedicated technical support, open the Contact Us dialog with the Contact us button at the bottom of the pricing page. Including the following helps us answer precisely.

IncludeExamples
Company and contact personCompany name, department, contact name and details
Scale and timingNumber of users, when you plan to adopt
EnvironmentWhether the network is separated, OS, the DBMS types and versions you use
RequirementsQuotes and tax invoices, contract, legal, and security reviews, purchasing procedures

Plan features and team sizes are explained in Plans and features, and subscriptions and payment in Manage Subscription. Education plan applications for students and schools are also in Manage Subscription.

Information worth including

When reporting a problem, the following lets us check it faster. The bug report panel fills in the first three for you.

InformationWhere to find it
Web app or desktop app, OS and browserFor the web app, include the browser name and version
NeoSQL versionShown next to the logo in the app header as a number starting with v
DBMS and its versionCheck in the connection dialog or with your database administrator
Whether you are signed in, and whether it is a local or account projectOn Home, local projects carry the Local mark
Steps to reproduceWrite what you clicked and entered, in order
Error messages on screen, screenshotsCopy the error of a failed job from the Background Processes popover on the status bar

When requesting a feature, describe the situation where you need it. Knowing what you were trying to do and where you got stuck helps us set priorities.

  • Bug report: the panel for reporting problems from inside the app.
  • Troubleshooting: common problems to check before contacting us.
  • FAQ: frequently asked questions with short answers.
  • Manage Subscription: subscribing, canceling, refunds, and the education plan.