Customer support
Support built around the work that is waiting
A service advisor with a blocked invoice and an administrator with a setup question need different handling. Clear context and impact help the right person respond.
Customers can request help from within VMOTEK so the issue reaches support with account context. Requests are categorized by business impact, routed for investigation and tracked through resolution. Contracted coverage and response targets are documented in the customer agreement.
Planning detail
Decisions to make before the work begins
Use the right channel
Existing customers should start with the in-product support path so company and workflow context can be associated safely.
- Use help content for configuration and repeatable tasks
- Use support for account-specific errors or blocked work
- Use the public contact form for evaluation and general questions
Describe business impact
Priority depends on what the issue prevents, how many people or shops are affected and whether a safe workaround exists.
- Identify company, shop, page and record number
- State expected and actual behavior
- Include timing, reproducible steps and a redacted screenshot
Protect sensitive information
Support needs operational evidence, not authentication secrets or full payment information.
- Never send passwords, API secrets or private keys
- Redact card, banking and unnecessary customer data
- Use record identifiers so authorized staff can locate context
How it works
A controlled path from decision to daily use
- 01
Submit context
Describe the workflow, location, affected records, expected result, actual result and business impact.
- 02
Triage impact
Support separates how-to questions, data issues, integration failures and product defects.
- 03
Investigate
The team reproduces the issue, reviews permitted technical evidence and identifies a path forward.
- 04
Communicate
The requester receives status, workarounds where available and any information still needed.
- 05
Resolve
Configuration is corrected, guidance is supplied or a product change is released and verified.
- 06
Learn
Recurring issues inform help content, training, monitoring and product improvements.
What to expect
Clear ownership and practical safeguards
Useful intake
Good evidence shortens the distance from report to diagnosis.
- Business impact and affected workflow
- Record identifiers, not sensitive data
- Steps, timing and screenshots
Visible ownership
Requests have a category, status and responsible team rather than disappearing into an inbox.
- Impact-based triage
- Status communication
- Escalation for broad disruption
Safer troubleshooting
Support access and data handling follow role, permission and customer-agreement boundaries.
- Least necessary access
- No passwords in tickets
- Documented corrective action
Ready to move forward?
Bring support requirements into the evaluation
Tell us your operating hours, internal ownership and escalation needs so expectations are explicit.