Support And Troubleshooting
Prepare support requests, allow audited support access, handle attachments, troubleshoot common issues, and use demo or pilot paths.
Support works fastest when you send clear context: which branch, which module, which order or table, what you expected, and what actually happened.
This page helps you self-serve common fixes and prepare a good ticket when you still need help.
Before you contact support
Gather:
| Item | Example |
|---|---|
| Organization name | "Spice Route Café" |
| Branch | Main branch vs Mall outlet |
| Your role | Owner, staff, admin |
| Module | Billing, KDS, POS, QR |
| Order / table ID | If applicable |
| Time it happened | Helps find logs |
| Recent changes | New menu import, plan change, new staff |
Also check:
- plan and feature catalog — is the module supposed to be on?
- sales workflow mode — POS only vs Combined?
- operational shift — open for protected actions?
- payment provider — Razorpay dashboard status vs Zesty
- device scope — one phone vs entire branch down?
Demo workspaces
The one-hour demo creates a synthetic restaurant for exploration.
| Property | Detail |
|---|---|
| Duration | Auto-deletes after one hour |
| Data | Fake menu and orders |
| Limits | Blocks external billing, invites, some branch admin |
| Use case | Click through product before signup |
If sign-in fails or session expired, start a fresh demo from the marketing site. Do not use demo for real menu or payment configuration.
Pilot program
For assisted onboarding, apply via the pilot program.
Pilots typically include:
- menu import help
- kitchen and billing configuration
- guided first shift with Zesty team
Pilots are not a self-serve sandbox—they are for restaurants planning to go live.
Support tickets (in-app)
Eligible users create tickets from the app.
staff-settings
Use the staff settings support category for role, invitation, branch assignment, notification, or access issues. Include the organization, branch, affected staff member, and the exact permission or setting that needs review.
Write a good ticket
- Subject — one line summary ("Billing queue empty but table unpaid")
- Steps — what you clicked, in order
- Expected — what should have happened
- Actual — error message or wrong screen
- Attachments — screenshot or export (no passwords, no full card numbers)
Safe attachments
- crop screenshots to relevant UI
- redact customer phone numbers if not needed
- do not upload
.envor credential files
Support access
Admins may allow support access tied to a ticket.
Rules:
- allow only while the issue is active
- state the reason in the ticket
- review access after resolution
- revoke if ticket closed
Support access is audited.
Troubleshooting guide
Missing module or menu item
- Check Settings → Features (owner)
- Check branch feature override
- Check sales workflow mode
- Check staff role permissions
- Sign out and in after plan change
Shift gate blocking actions
Message like "shift not open":
- Open shift from header control
- Confirm correct branch
- Manager reviews bypass only for emergencies
Guide: Operational shift
QR / wrong table order
- Confirm unique QR per table
- Reprint if QR damaged or swapped
- Check table record matches physical table number
Item missing from customer QR menu
- Item available?
- Category active?
- Branch override hiding item?
- Food type filter on customer side?
Payment mismatch
- Open provider dashboard (Razorpay, etc.)
- Match payment ID to Zesty payment row
- Do not double-charge while status is pending
- Refund only after manager confirms
Staff cannot access branch
- Branch assignment on staff record
- Branch active status
- Role permissions include module
- User signed into correct organization
Mobile layout confusion
- Easy vs Standard interface preference
- Solo Run vs Shared Crew org setting
- Compare with training screenshots for correct mode
Guides: Easy and Standard, Solo Run and Shared Crew
Newsletter or marketing contact
Public forms and newsletter signups have separate consent rules. Confirm recipient address and opt-in before bulk sends.
Customer campaigns: Customers overview
Demo or pilot login issues
- Demo expired → new demo session
- Pilot → contact your pilot coordinator, not generic support only
Escalation contacts
For public walkthroughs, product questions, or privacy requests:
Email: support@zesty.id
Include organization name and branch in the subject line.
What support cannot do instantly
- change your legal tax filing
- override payment-provider settlement timelines
- recover deleted demo data after expiry
- enable plan-locked modules without billing change