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:

ChannelHow It WorksAuto-Ticket?
Emailsupport@sanafai.comYes — creates ticket automatically
In-App ChatChat bubble in portalYes — creates ticket automatically
Contact FormForm on lotwize.comYes — creates ticket automatically
PhoneCall support lineAgent creates ticket manually
Social MediaTwitter/X DMs, FacebookAgent creates ticket manually

Ticket Lifecycle

New → Open → In Progress → Pending Customer → Resolved → Closed

Status Definitions

StatusMeaningSLA Target
NewJust received, not assignedAssign within 15 min
OpenAssigned to agent, being workedFirst reply within 2h
In ProgressAgent actively investigatingUpdate every 24h
Pending CustomerWaiting for info from customerAuto-reminder at 48h
ResolvedFix applied, awaiting confirmationAuto-close after 72h
ClosedConfirmed resolved or auto-closed
EscalatedMoved to engineering/managementImmediate

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

PriorityDescriptionResponse TimeResolution Target
P1 — CriticalPlatform down, payment failures, security issue15 minutes4 hours
P2 — HighMajor feature broken, data incorrect1 hour24 hours
P3 — NormalFeature question, minor bug, how-to4 hours48 hours
P4 — LowFeature request, feedback, general inquiry24 hours7 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

  1. Select unassigned ticket
  2. Click "Assign"
  3. 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

  1. Open the ticket
  2. Read the full thread
  3. Check customer context (plan, community, recent activity)
  4. Write your reply:
    • Acknowledge the issue
    • Provide solution or next steps
    • Set expectations (timeline)
    • Include links to help articles
  5. 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:

  1. Click "Escalate"
  2. Choose escalation type:
    • Technical → Engineering team
    • Billing → Finance team
    • Management → Manager review
    • Security → Security team
  3. Add reason for escalation
  4. Engineering gets notified via Slack/email

Macros (Canned Responses)

Save time with pre-written responses:

Built-in Macros

MacroUse For
Password ResetForgot password requests
Payment RetryFailed payment instructions
Browser CacheLoading issues
Feature RequestAcknowledging suggestions
Refund RequestProcessing refund steps
Trial ExtensionExtending free trials

Creating Custom Macros

  1. Go to Support → Macros
  2. Click "New Macro"
  3. Write the response template
  4. Add variables: {{customer_name}}, {{community_name}}, {{ticket_id}}
  5. Save

Apply a macro: Click "Insert Macro" when replying to a ticket.


SLA Management

SLA Rules

Default SLA by plan:

PlanFirst ReplyResolution
Starter24 hours72 hours
Growth8 hours48 hours
Pro2 hours24 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:

  1. The system flags it
  2. Agents can click "Create Article"
  3. Write the article using the ticket as a starting point
  4. Publish to help center

Next Steps


Support tools not working? Contact the admin team at support@sanafai.com.

Was this helpful?