Command Palette

Search for a command to run...

Support Tickets

Professional support engineered for security professionals. Complete guide to using the support ticket system effectively.

Pro Tip
Security incidents don't follow 9-to-5 schedules. Our support system is designed for the urgency and precision that real threat investigations demand.
Need Help Right Now?
Quick access to support channels based on your situation

Web Application

Create New Ticket

Telegram Bot

Mobile Support

Urgency Levels

Choose the right urgency level to ensure appropriate response times and resource allocation

Low

Non-urgent issues that can be resolved when convenient

Response: 24-48 hours
Examples: Feature requests, general questions, documentation improvements
Medium

Issues that should be addressed in a reasonable timeframe

Response: 4-8 hours
Examples: Account issues, billing questions, API problems
High

Important issues that need prompt attention

Response: 1-2 hours
Examples: Search problems, export failures, data discrepancies
Critical

Urgent issues requiring immediate attention

Response: 15-30 minutes
Examples: Platform outages, security vulnerabilities, data breaches

Support Ticket Statuses

Track the progress of your tickets through these distinct stages

Pending

Ticket is waiting for review

Processing

Ticket is being actively worked on

Resolved

Ticket has been completed

Support Categories & Labels

Accurate labeling ensures your ticket reaches the right specialist team immediately

All Available Labels
Select the most appropriate labels for your support ticket
Bug

Something is not working as expected

Localization

Translation or language-related issues

Feature Request

Request for new functionality

Enhancement

Improvement to existing features

Data Removal

Request to remove personal or sensitive data

Partnership

Business partnership inquiries

Question

General questions or clarifications

Vulnerability

Security-related issues or concerns

Free Subscription

Issues related to free tier access

API

API-related issues or questions

Web Application

Issues with the web interface

Telegram Bot

Issues with the Telegram bot

Documentation

Documentation-related issues or requests

Billing

Payment and billing-related issues

Custom Plan

Custom subscription plan requests

Referrals

Referral program related issues

Promocodes

Promotional code related issues

Games

Gaming features related issues

Regular Search

Basic search functionality issues

Advanced Search

Advanced search features issues

Identity Linking

Identity linking functionality issues

Exports

Data export functionality issues

Account

General account management issues

Authentication

Login and authentication issues

Duplicates

Duplicate data or entries issues

Incorrect Data

Data accuracy or correctness issues

Something is Wrong

General issues when unsure of category

Limits

Usage limits and restrictions issues

UI

User interface design issues

UX

User experience issues

Adaptive

Responsive design and mobile issues

Consultation

Request for advice or consultation

Account Merge

Request to merge multiple accounts

Database

Inquiries about purchasing database access or data

Advertisement

Inquiries about purchasing advertisement space on website or bot

CVSS 0 (None)

No vulnerability - CVSS score 0

CVSS 1 (Low)

Low severity vulnerability - CVSS score 1

CVSS 2 (Low)

Low severity vulnerability - CVSS score 2

CVSS 3 (Low)

Low severity vulnerability - CVSS score 3

CVSS 4 (Medium)

Medium severity vulnerability - CVSS score 4

CVSS 5 (Medium)

Medium severity vulnerability - CVSS score 5

CVSS 6 (Medium)

Medium severity vulnerability - CVSS score 6

CVSS 7 (High)

High severity vulnerability - CVSS score 7

CVSS 8 (High)

High severity vulnerability - CVSS score 8

CVSS 9 (Critical)

Critical severity vulnerability - CVSS score 9

CVSS 10 (Critical)

Critical severity vulnerability - CVSS score 10

Web Application Guide

Creating a Support Ticket
Step-by-step process for web application users
1

Navigate to Support Tickets

From your dashboard, click on "Support Tickets" in the left sidebar or navigate directly to /dashboard/tickets

Open Support Tickets
2

Create New Ticket

Click the "New Ticket" button in the top-right corner of the support tickets dashboard

3

Configure Your Ticket

Essential Configuration
  • • Subject: Clear, specific description (e.g., "API returning 500 errors for breach search")
  • • Priority: Match urgency to business impact
  • • Category: Helps route to right specialist
4

Write Effective Description

Include These Detail
  • • What you were trying to accomplish
  • • Exact steps you took
  • • What happened vs. what you expected
  • • Error messages (exact text or screenshots)
  • • Browser/device information (if relevant)
  • • When the issue started occurring
5

Submit and Monitor

After submission, you'll receive a ticket ID and email notifications. Monitor progress through the dashboard and respond promptly to any follow-up questions.

Telegram Bot Guide

Mobile Support Through Telegram
Get help directly through the Telegram bot interface
1

Access the Bot

Ensure your Telegram account is linked to your LeakZero account. If not linked, follow the integration process first.

Integration Guide
2

Navigate to Support

In the bot main menu, select "Profile" 🡒 "Tickets" to access the support ticket system

Bot Navigation

Main Menu Profile Tickets New Ticket

3

Create New Ticket

Follow the bot's prompts to create your ticket. The bot will guide you through each step with clear instructions.

Bot Will Ask For:

  • • Ticket subject (be specific and clear)
  • • Detailed description of your issue
  • • Urgency level selection
  • • Appropriate label categories
4

Manage and Monitor

The bot will provide real-time notifications for updates. You can view all your tickets and respond directly through the bot interface.

Real-time updatesDirect messaging

Best Practices for Faster Resolution

Do This
  • Be specific in subject lines: "API returning 429 errors on /search endpoint" vs "API not working"
  • Include error messages: Copy exact error text or provide screenshots of error dialogs
  • Provide reproduction steps: Clear step-by-step instructions to recreate the issue
  • Choose accurate labels: Select the most specific category that matches your issue
  • Respond promptly: Quick responses to follow-up questions keep your ticket prioritized
Avoid This
  • Vague descriptions: "Something is broken" or "It's not working" without specifics
  • Multiple issues in one ticket: Separate problems should get separate tickets for better tracking
  • Wrong urgency levels: Don't mark minor issues as Critical - it delays actual emergencies
  • Duplicate tickets: This will only slow down the resolution process.
  • Delayed responses: Slow responses to support questions extend resolution time
Response Time Expectations
Service level commitments by urgency and support tier
Critical
15-30m

Platform outages, security issues

High
1-2h

Blocking issues, data problems

Medium
4-8h

Account issues, billing questions

Low
24-48h

Feature requests, general questions

Note
Response times are measured from ticket creation during business hours (UTC). Critical issues receive 24/7 attention regardless of time zone.
Ready to Get Support?
Choose your preferred method and get the help you need
Documentation - LeakZero | LeakZero