How to Create a Support Ticket: Step-by-Step Guide

Get the Assistance You Need with a Clear Support Request

When you encounter a technical issue or need assistance with a digital service, submitting a well-prepared support ticket can help the support team understand your request and investigate it more efficiently.

A support ticket is a structured request used to communicate a question, report a problem, or request assistance with a product or service.

TUSAQ provides support resources and official communication channels for customers using its software products and digital services.

This guide explains how to prepare and submit a support request, what information to include, and how to communicate effectively throughout the support process.

1. What Is a Support Ticket?

A support ticket is a recorded request for assistance related to a particular product, account, or service.

Support tickets help organize communication between customers and support teams.

Depending on the support system, a ticket may contain:

• A subject or title

• A description of the issue

• The related product or service

• Contact or account information

• Attachments

• A reference number

• A request status

• Responses from the support team

Available fields and tracking features depend on the support channel used.

2. When Should I Create a Support Ticket?

A support request may be appropriate when you need assistance with:

Technical Issues

Application errors, unexpected behavior, unavailable features, or service access problems.

Account and Login Problems

Difficulty signing in, accessing an account, or using account-related features.

Subscription Questions

Plan information, renewals, upgrades, or service eligibility.

Billing and Payment Issues

Questions about invoices, payments, or subscription charges.

Domain and Hosting Services

DNS configuration, domain management, hosting access, or related technical questions.

Product Integrations

Questions about supported modules, API connections, or third-party integrations.

General Service Assistance

Other questions that cannot be resolved through available documentation.

The support options and scope of assistance depend on the product and applicable service conditions.

3. How Do I Create a Support Ticket?

The exact steps may vary by product or support platform.

Where a customer support ticket system is available, the general procedure is as follows.

Step 1: Visit the Official TUSAQ Website

Go to:

https://www.tusaq.com/

Use the official customer or support options available for your service.

Step 2: Access the Relevant Support Area

If your service includes a customer account or ticket management interface, sign in using the appropriate credentials.

Some general inquiries may be handled through a public contact form or another official communication channel.

Step 3: Select the Support Request Option

Look for the available option to create a new support request.

The name and location of this option may differ between products.

Step 4: Choose the Relevant Product or Service

If the form provides a product or service selection, choose the option that matches your issue.

For example, your request may concern TUSERP, TUSCRM, a hosting account, or a domain service.

Step 5: Enter a Clear Subject

Write a short title that accurately describes your issue.

A specific subject helps the support team understand the purpose of your request.

Step 6: Describe the Problem

Explain what happened, what you expected to happen, and how the issue affects your work.

Include the steps required to reproduce the problem if possible.

Step 7: Add Supporting Information

If attachments are supported, include relevant screenshots, error messages, or other non-sensitive information.

Step 8: Review and Submit

Check that your description is accurate and that you have not included confidential credentials.

Submit the request through the available support channel.

Step 9: Save the Confirmation Details

If the system provides a ticket number, confirmation message, or reference identifier, keep it for future communication.

Not all support channels issue a ticket number.

4. How Should I Write a Support Ticket Subject?

A good subject should be short, clear, and specific.

Avoid vague titles such as:

• Help needed

• Urgent problem

• Software not working

• Error

Instead, use descriptive subjects such as:

• Unable to Access TUSERP Dashboard

• TUSCRM Contact Form Displays an Error

• Domain DNS Configuration Assistance

• Hosting Website Access Issue

• Question About TUCOUNT Subscription Renewal

These examples illustrate how to describe an issue. They do not imply that every listed issue is a known product defect.

5. What Information Should I Include in the Description?

A useful support ticket answers several basic questions.

What Is the Problem?

Describe the issue in simple, direct language.

Which Product Is Affected?

Identify the relevant application or service.

When Did It Start?

Include the approximate date and time.

What Were You Trying to Do?

Explain the action you were performing.

What Happened Instead?

Describe the unexpected result.

Can the Problem Be Reproduced?

List the steps that trigger the issue, if known.

What Have You Already Tried?

Mention any troubleshooting steps you completed.

How Does It Affect Your Business?

Explain whether the issue prevents an important task or affects multiple users.

This information can reduce the need for additional clarification.

6. Example of a Well-Written Support Ticket

Subject: Unable to Save a Customer Record in TUSCRM

Product: TUSCRM

Description:

Hello TUSAQ Support Team,

I am experiencing an issue while attempting to save a customer record in TUSCRM.

After entering the required information and submitting the form, the record does not appear to be saved.

The issue started today and has occurred more than once.

I have already refreshed the page and tried again, but the same behavior continues.

Could you please help me investigate this issue?

Thank you.

Note: This is a fictional example showing how to structure a support request, not a report of an actual TUSCRM problem.

7. Can I Attach Screenshots or Files?

Some support systems allow customers to attach screenshots or files.

Attachments can help explain issues that are difficult to describe in writing.

Useful examples include:

• Screenshots of error messages

• Images showing unexpected interface behavior

• Relevant configuration screenshots

• Non-sensitive technical logs

• Documents required for an authorized service request

Before uploading any attachment, remove or conceal sensitive information that is not necessary for troubleshooting.

Attachment availability, accepted formats, and file-size limits depend on the support system.

8. What Information Should I Never Share?

Security should always be considered when contacting technical support.

Do not include:

• Account passwords

• One-time verification codes

• Private API keys or access tokens

• Complete payment card information

• Recovery codes

• Private cryptographic keys

• Unnecessary personal or confidential customer data

If sensitive information is required for a legitimate support process, ask the support team about an approved secure method.

Never send confidential credentials simply because someone requests them through an unexpected message.

9. How Do I Select the Correct Priority?

Some support systems allow customers to indicate the urgency or impact of a request.

Priority options may vary by product and service.

A general way to evaluate an issue is:

Low Impact

A general question or minor issue that does not significantly affect business operations.

Medium Impact

A feature is not functioning as expected, but important operations can continue.

High Impact

An important business process is significantly affected.

Critical Impact

A major service disruption or serious security concern is affecting essential operations.

These are general examples, not official TUSAQ ticket priority categories.

The actual classification and handling of requests depend on the applicable support process.

When describing urgency, focus on the business impact rather than simply marking every request as urgent.

10. What Happens After I Submit a Ticket?

After a support request is submitted, the process may include:

1. Receipt of the request.

2. Initial review of the information.

3. Classification or routing to the relevant support personnel.

4. Technical investigation, when necessary.

5. A request for additional details.

6. Communication of findings or suggested steps.

7. Confirmation of the outcome.

8. Closure of the request, where supported.

The workflow varies depending on the service and support channel.

A submitted request does not guarantee immediate resolution.

11. How Can I Check My Ticket Status?

If your service provides ticket tracking, you may be able to review the status through the relevant customer or support area.

Common ticket status concepts include:

• Open: The request has been recorded.

• In Progress: The issue is being reviewed or handled.

• Waiting for Customer: Additional information or action is required.

• Resolved: A solution or response has been provided.

• Closed: The support process has been completed.

These are illustrative status descriptions. The actual labels and workflow may differ.

If your support channel does not provide ticket tracking, follow the communication instructions supplied after submitting your request.

12. Can I Add More Information to an Existing Ticket?

Where supported, you may be able to reply to an existing ticket or add further information.

Additional details may include:

• A new error message

• Updated screenshots

• Results of suggested troubleshooting

• Changes in the affected service

• Confirmation that the issue continues

Whenever possible, keep updates related to the same issue within the existing support conversation.

This helps preserve context and reduces duplicated investigation.

13. Should I Create Multiple Tickets for the Same Issue?

Creating several requests for the same problem may make communication more difficult.

Where practical, submit one ticket for one primary issue and provide updates within that request.

If you encounter a separate, unrelated problem, a new ticket may be appropriate.

If the existing ticket is no longer accessible, use the official support channel and mention the previous reference number if available.

14. How Long Does It Take to Resolve a Support Ticket?

Resolution times vary depending on the nature of the issue.

Factors may include:

• Technical complexity

• Business impact

• Required investigation

• Customer response time

• Third-party service dependencies

• Applicable support coverage

• Current request volume

Some questions can be answered quickly, while others may require additional technical work.

Any guaranteed response or resolution times must be defined in the applicable service agreement.

15. What If I Cannot Access My Customer Account?

If you cannot sign in to your account, you may be unable to use an account-based ticket system.

In that situation:

1. Confirm that you are using the correct login page.

2. Check your email address or account identifier.

3. Use the official password recovery option if available.

4. Review any relevant account access instructions.

5. If the issue continues, use another official contact method provided on the TUSAQ website.

Account-specific assistance may require identity or ownership verification.

Never provide your password or authentication codes to another person.

16. How Can I Make My Support Request More Effective?

Before submitting your ticket, review this checklist:

• Is the subject clear?

• Have I selected the correct product?

• Have I explained the issue accurately?

• Have I included relevant error messages?

• Have I provided the approximate time?

• Have I described the business impact?

• Have I included safe and useful attachments?

• Have I removed sensitive credentials?

• Have I checked the available documentation?

A clear request helps the support team begin its investigation with better information.

Frequently Asked Questions

Do I need a TUSAQ account to create a support ticket?

This depends on the service and support channel. Account-based ticket systems may require login, while general inquiries may use other official contact methods.

Can I create a ticket before purchasing a product?

You can use available official contact options to ask about products and services. A dedicated ticket system may be reserved for eligible customers.

Will I receive a ticket number?

If the support system provides reference numbers, one may be issued after submission. Other contact channels may use different confirmation methods.

Can I submit a support ticket in Turkish or English?

You may describe your request clearly in Turkish or English. Available support languages and handling arrangements may depend on the relevant service.

Can I request technical assistance for third-party software?

You may ask about supported integrations or connected services. Assistance involving third-party products depends on the scope of support and technical feasibility.

Can I reopen a closed ticket?

This depends on the support platform and its workflow. If reopening is unavailable, use the official contact channel and reference the previous request.

Where can I find additional help?

Visit the TUSAQ Knowledge Base or use the official support options available through the website.

Conclusion

Creating a clear support ticket is one of the most effective ways to request technical assistance.

By selecting the relevant service, describing the issue accurately, providing useful details, and protecting confidential information, you can help make the support process more efficient.

TUSAQ aims to provide practical support resources that help customers use digital products and services with greater confidence.

Clear Requests. Better Communication. Smarter Support.

For product information and support resources, visit https://www.tusaq.com/.