Get help with vSMAART
Tell us which module you use and what happened. A clear issue summary helps the support team understand the problem and identify the next step.
What to include
- The module and the action you were taking.
- What you expected and what happened instead.
- The time of the issue and your time zone.
- A transaction or case reference, where available.
- Steps that help the team reproduce the issue.
- The effect on your work and any workaround already tried.
Do not send passwords or sensitive records through the public contact form. Ask the support team which approved channel to use if it needs files or detailed evidence.
Help by module
CheQD: questions about cases, ownership, status, and investigations.
SynQD: questions about records, imports, and data validation.
TransaQD: questions about document processing and transaction results.
ConneQD: questions about connections and workflow handoffs.
Product questions before you start
Read our FAQs for an overview of the modules and what to prepare for a discussion. If your question concerns an active deployment, use the support route agreed with your organization.
Support arrangements
Your service agreement defines the support coverage and escalation process for your deployment. Include the effect on your operations when reporting an issue so the team can assess it in context. A message sent through the public form is a request to the team. It is not, by itself, a tracked ticket with a case number.