Support starts with the right context.
Find documentation, ask for product help, report reproducible problems or share a feature idea through the route designed for that kind of request.
The fastest route depends on what you need.
Keeping support, bugs and product ideas separate makes every message easier to understand, review and act on.
Documentation
Setup guides, feature explanations and product-specific help should solve the most common questions without waiting for a reply.
Contact support
Use this for installation, configuration, documentation and general help with a Veyra product.
Report a bug
Document unexpected behaviour, compatibility problems and steps that make the issue reproducible.
Request a feature
Describe the workflow problem, the result you need and why the improvement would matter in real projects.
Useful context makes support faster and safer.
Check the documentation
Use the relevant product guide first, especially for installation, setup and known workflows.
Describe the exact outcome
Explain what you expected, what happened and the steps already taken before opening the request.
Keep sensitive data out
Never include passwords, private API keys, license secrets or customer information in a support form.