Loading...
Support
Escalate with the context support needs.
Support works fastest when the issue includes the route, workspace, affected client or document, expected result, actual result, and whether it happens repeatedly.
Product bugs
Report broken workflows, incorrect state, UI issues, missing records, or unexpected redirects.
- Include the exact route and the button or action you used.
- Tell us whether a refresh, logout, or different browser changes the result.
Account access
Use support for workspace login loops, portal-login confusion, invitation issues, and workspace selection problems.
- Include the email address used for login.
- Mention whether this is workspace access or client portal access.
Billing and checkout
Use support for failed checkout, plan mismatch, invoice payment questions, or subscription access issues.
- Include the selected plan and approximate time of checkout.
- Never send full card numbers or sensitive payment details.
Security concerns
Report suspected access issues, exposed data, or security vulnerabilities with concise reproduction details.
- Include impact and the smallest safe reproduction path.
- Avoid sharing the report publicly until we investigate.
Workflow questions
Ask how to map your current sales, agreements, delivery, invoice, and portal processes into OnloZap.
- Describe your current tool stack.
- Share which handoff is causing the most operational drag.
Primary channel
Email is the direct support channel while a public ticketing portal is not exposed.
- Use support@onlozap.com for urgent product issues.
- Use hello@onlozap.com for product, partnership, or demo questions.
Next step
Use the help center before escalating routine questions.
The help center covers the most common sign-in, checkout, portal, and setup issues.