LotWize Help Center — Support Ticket Workflow Guide
_Last updated: May 2026_
LotWize Help Center — Support Ticket Workflow Guide
Last updated: May 2026
This guide covers managing customer support tickets from creation to resolution.
Ticket Channels
Customers can reach support through multiple channels:
| Channel | How It Works | Auto-Ticket? |
|---|---|---|
| support@sanafai.com | Yes — creates ticket automatically | |
| In-App Chat | Chat bubble in portal | Yes — creates ticket automatically |
| Contact Form | Form on lotwize.com | Yes — creates ticket automatically |
| Phone | Call support line | Agent creates ticket manually |
| Social Media | Twitter/X DMs, Facebook | Agent creates ticket manually |
Ticket Lifecycle
New → Open → In Progress → Pending Customer → Resolved → Closed
Status Definitions
| Status | Meaning | SLA Target |
|---|---|---|
| New | Just received, not assigned | Assign within 15 min |
| Open | Assigned to agent, being worked | First reply within 2h |
| In Progress | Agent actively investigating | Update every 24h |
| Pending Customer | Waiting for info from customer | Auto-reminder at 48h |
| Resolved | Fix applied, awaiting confirmation | Auto-close after 72h |
| Closed | Confirmed resolved or auto-closed | — |
| Escalated | Moved to engineering/management | Immediate |
Ticket Dashboard
Queue Overview
Go to Admin → Support to see:
- New tickets (unassigned)
- Open tickets (assigned, in progress)
- Overdue tickets (past SLA)
- Escalated tickets
- Resolved today
Ticket Table
Columns:
- Ticket ID (e.g., #4821)
- Subject
- Customer name and community
- Priority
- Status
- Assigned agent
- Created time
- Last update
- SLA timer
Sorting:
- By priority (P1 first)
- By age (oldest first)
- By SLA (overdue first)
Priority Levels
| Priority | Description | Response Time | Resolution Target |
|---|---|---|---|
| P1 — Critical | Platform down, payment failures, security issue | 15 minutes | 4 hours |
| P2 — High | Major feature broken, data incorrect | 1 hour | 24 hours |
| P3 — Normal | Feature question, minor bug, how-to | 4 hours | 48 hours |
| P4 — Low | Feature request, feedback, general inquiry | 24 hours | 7 days |
Auto-priority rules:
- Contains "can't log in" → P2
- Contains "payment failed" → P1
- Contains "bug" or "broken" → P2
- Contains "how do I" → P3
- From Pro or PMC customer → +1 priority level
Working Tickets
Assigning Tickets
- Select unassigned ticket
- Click "Assign"
- Choose agent (or use auto-assign)
Auto-assignment rules:
- By expertise (billing, technical, onboarding)
- By customer tier (Pro/PMC → senior agents)
- Round-robin for equal load
- Language matching
Replying to Customers
- Open the ticket
- Read the full thread
- Check customer context (plan, community, recent activity)
- Write your reply:
- Acknowledge the issue
- Provide solution or next steps
- Set expectations (timeline)
- Include links to help articles
- Click "Send Reply"
Internal notes:
- Use the "Internal Note" field for team-only comments
- Great for: investigation notes, escalation reasons, customer history
Escalating Tickets
When you need help:
- Click "Escalate"
- Choose escalation type:
- Technical → Engineering team
- Billing → Finance team
- Management → Manager review
- Security → Security team
- Add reason for escalation
- Engineering gets notified via Slack/email
Macros (Canned Responses)
Save time with pre-written responses:
Built-in Macros
| Macro | Use For |
|---|---|
| Password Reset | Forgot password requests |
| Payment Retry | Failed payment instructions |
| Browser Cache | Loading issues |
| Feature Request | Acknowledging suggestions |
| Refund Request | Processing refund steps |
| Trial Extension | Extending free trials |
Creating Custom Macros
- Go to Support → Macros
- Click "New Macro"
- Write the response template
- Add variables:
{{customer_name}},{{community_name}},{{ticket_id}} - Save
Apply a macro: Click "Insert Macro" when replying to a ticket.
SLA Management
SLA Rules
Default SLA by plan:
| Plan | First Reply | Resolution |
|---|---|---|
| Starter | 24 hours | 72 hours |
| Growth | 8 hours | 48 hours |
| Pro | 2 hours | 24 hours |
Business hours: 9 AM - 6 PM ET, Monday-Friday.
After-hours: P1 tickets page the on-call engineer. All others queue for next business day.
SLA Breach Alerts
When a ticket is approaching or past SLA:
- Ticket turns yellow (approaching)
- Ticket turns red (breached)
- Manager gets notified
- Escalation required
Metrics & Reporting
Support Metrics Dashboard
- Tickets created today/this week/this month
- First response time (average and by priority)
- Resolution time (average and by priority)
- Customer satisfaction score (CSAT)
- Ticket backlog
- Agent performance
Customer Satisfaction
After a ticket is resolved, the customer gets a short survey:
- 😊 Good — "How did we do?"
- 😐 Okay — "What could be better?"
- 😞 Bad — "We're sorry — a manager will follow up"
Target CSAT: More than 90% positive ratings.
Knowledge Base Integration
Suggested Articles
When viewing a ticket, LotWize suggests relevant help articles based on the ticket subject and content. Agents can:
- Click to read the article
- Copy the link to send to the customer
- Flag the article as helpful or not
Article Gaps
If tickets keep coming in about something not covered in the knowledge base:
- The system flags it
- Agents can click "Create Article"
- Write the article using the ticket as a starting point
- Publish to help center
Next Steps
Support tools not working? Contact the admin team at support@sanafai.com.