Account and onboarding support
Commercial, rollout, menu import, location setup and training questions are handled through the assigned account or onboarding channel.
Support Policy.
How Limvero handles restaurant support, incident routing, support sessions and safe troubleshooting.
Support channels
Support is routed by issue type and account context so restaurant operations, security and commercial requests do not mix.
Operational support
Restaurant Cabinet, POS, KDS, inventory, loyalty, reports, devices and integration issues should include tenant, location, user role and timestamp details.
Security reports
Suspected compromise, exposed API keys, unauthorized access or vulnerability reports follow security and vulnerability disclosure workflows.
Status updates
Confirmed incidents and maintenance notices are published on the public status page when they affect customer-facing service.
Support sessions
Support access is time-bounded, audited, read-only by default and elevated only through an explicit approval workflow.
Provider escalation
Payment, fiscal, delivery, hardware or hosting provider incidents may require escalation through that provider as well as Limvero support.
Good support requests
Clear scope helps Limvero troubleshoot without asking restaurants to expose sensitive data.
Include the affected workflow
Name the affected module, such as POS payment, KDS order status, inventory writeoff, API key, webhook, report export or tenant billing.
Include scope
Share tenant, restaurant, location, terminal or service point identifiers when available. Do not send guest exports through public forms.
Include timing and impact
Provide the date, time, user role, number of affected orders or devices and whether restaurant service is blocked.
Protect secrets
Never send passwords, POS PINs, full API keys, payment card data, raw tokens or private provider credentials in support messages.
Response windows and dedicated support coverage depend on the plan and signed agreement. Critical production incidents are prioritized ahead of advisory and onboarding requests.
Plan a clean restaurant rollout.
Talk through locations, POS devices, kitchen workflow, menu migration, API needs and security review before launch.