A support ticket is a unique, tracked request that a user submits to customer support when they need help with an issue, have a question, or want to report a problem. Each ticket has an ID, a status, and a history of messages between the user and the support team.
For financial and crypto services, support tickets are a core part of the support process. They allow users to describe their issue in detail, attach relevant documents or screenshots, and track progress until the issue is resolved.
Why support tickets are used
Support tickets help both users and support teams by:
- Creating a clear record – all messages, actions, and decisions related to an issue are stored in one place.
- Enabling tracking – users and agents can see the current status and history of a request.
- Prioritising work – tickets can be categorised by urgency, type, and impact, so critical issues are handled first.
- Ensuring continuity – if multiple agents work on a case, they can see the full history and avoid asking the user to repeat information.
- Supporting compliance – for regulated services, ticket records can serve as evidence of how issues were handled.
Tickets are especially important for complex, sensitive, or non-urgent issues that do not require immediate live chat or phone support.
When users create a support ticket
Users typically open a support ticket in situations such as:
- Account issues – problems with login, 2FA, verification, or account access.
- Transaction problems – delayed or failed deposits, withdrawals, or transfers.
- Disputes and errors – incorrect charges, suspected fraud, or transactions the user does not recognise.
- Product questions – how to use certain features, clarification on fees or limits, or requests for guidance.
- Compliance and documentation – submitting additional documents for verification, responding to compliance queries, or asking about regulatory requirements.
- Technical issues – bugs, app crashes, or features not working as expected.
For urgent security issues (for example, suspected account compromise), many platforms also offer faster channels such as phone support or priority ticket queues.
How support tickets are created
There are several common ways to create a support ticket.
In-app or web forms
- Users go to a “Help” or “Support” section in the app or website.
- They select a topic (for example, “Deposits and withdrawals”, “Account and verification”, “Security”).
- They fill in a form with:
- Subject or summary of the issue.
- Detailed description of what is happening.
- Relevant details such as transaction IDs, dates, amounts, error messages.
- Attachments such as screenshots, documents, or logs.
- Upon submission, the system creates a ticket and sends a confirmation email or in-app notification with the ticket ID.
Email-based tickets
- Users send an email to a support address (for example, [email protected]).
- The system automatically creates a ticket from the email and replies with a ticket ID.
- Further replies to the same email thread are attached to that ticket.
From live chat or phone
- If an issue cannot be resolved in a live chat or call, the agent may create a ticket on the user’s behalf.
- The user receives a ticket ID and can continue the conversation asynchronously via email or the app.
From help center articles
- Some help centers show a “Still need help?” or “Contact us” button at the bottom of articles.
- Clicking this may open a pre-filled ticket form related to the article’s topic.
Typical information in a support ticket
A well-structured ticket includes:
User and account information
- User name and registered email.
- Account ID or username (often auto-filled by the system).
- Verification level or customer type (retail, business, institutional), if relevant.
Issue details
- Clear subject line summarising the problem.
- Detailed description of what the user is trying to do and what is going wrong.
- Steps already taken (for example, “I tried resetting my password and enabling 2FA, but I still cannot log in”).
- Error messages, codes, or screenshots.
Transaction or event data (if applicable)
- Transaction IDs, hashes, or references.
- Dates, times, and amounts.
- Counterparty information (for example, bank name, wallet address).
- Network or chain details for crypto transactions.
Attachments
- Screenshots of error messages or app screens.
- Copies of relevant documents (for example, ID, proof of address, bank statements) when related to verification or disputes.
- Logs or technical details for bug reports.
Preferred communication channel
- Email, in-app messaging, or phone callback (if offered).
- Language preference, if the service supports multiple languages.
Support ticket lifecycle
Most tickets go through a standard set of statuses.
Submitted / Open
- The ticket has been created and is waiting for an initial response.
- Users typically receive an automated acknowledgment with an estimated response time.
In progress
- A support agent is actively working on the issue.
- The agent may request additional information or clarify details with the user.
- Status may change to “Waiting for customer” if more information is needed from the user.
Waiting for customer
- The support team is waiting for the user to provide more details, documents, or confirmation.
- The ticket may be paused until the user responds.
Resolved
- The issue has been fixed, answered, or otherwise addressed to the support team’s best ability.
- The agent explains the resolution and any next steps.
- Users are often invited to confirm that the issue is resolved or to reopen the ticket if it is not.
Closed
- The ticket is formally closed after resolution and any follow-up period.
- In some systems, closed tickets can still be viewed by the user but cannot receive new messages; a new ticket must be created for further issues.
Escalated
- For complex or high-impact issues, the ticket may be escalated to a specialist team, compliance, security, or management.
- Users may see a status change or receive a note that their case is being escalated.
How users can track and manage tickets
Users can usually manage their tickets in several ways.
Ticket list in the app or web dashboard
- A “Support” or “My tickets” section showing all open and past tickets.
- Each ticket displays:
- Ticket ID.
- Subject.
- Current status.
- Last update time.
- Users can click into a ticket to see the full conversation and add new messages.
Email notifications
- Automatic updates when:
- An agent replies.
- The status changes (for example, from “In progress” to “Resolved”).
- The ticket is closed.
- Emails often include a link to view the ticket in the app or web dashboard.
Adding updates and attachments
- Users can reply to the ticket thread with additional information, answers to agent questions, or new screenshots.
- Some systems allow attaching files directly in the app or via email.
Closing or reopening tickets
- Users may be able to mark a ticket as resolved if their issue is fixed.
- If the problem persists, users can usually reopen a resolved ticket or create a new one referencing the original ID.
Best practices for users when creating tickets
To get faster, more effective help:
- Use a clear subject – for example, “Withdrawal stuck for 3 days – TX ID: abc123”.
- Describe the issue in detail – what you expected, what actually happened, and when.
- Include key details – transaction IDs, dates, amounts, error messages, device and app version.
- Attach relevant evidence – screenshots, documents, or logs that help illustrate the problem.
- Check the help center first – many common issues have step-by-step guides that can resolve the problem faster than a ticket.
- Keep communication in one thread – reply to the existing ticket instead of creating multiple tickets for the same issue.
- Monitor your email and app notifications – respond promptly to requests for more information to avoid delays.
How support tickets differ from live chat
Support tickets and live chat serve different needs.
Support tickets
- Asynchronous – users and agents do not need to be online at the same time.
- Better for complex issues that require investigation, documentation, or multiple steps.
- Provide a persistent record that can be referenced later.
- Typically have longer response times (hours to days, depending on the service).
Live chat
- Synchronous – real-time conversation with an agent.
- Better for quick questions, simple troubleshooting, or urgent issues.
- May not create a detailed, long-term record unless a transcript is provided.
- Often has shorter wait times but may still escalate complex issues to tickets.
Many platforms use a hybrid approach: live chat for immediate help, and tickets for deeper investigation and follow-up.
