What Information Is Needed for Technical Support? A Complete Guide

Help Us Understand Your Issue and Find the Right Solution

When you experience a technical issue with a software product or digital service, providing accurate and relevant information is one of the most effective ways to support the troubleshooting process.

A clear technical report helps support personnel understand what happened, identify possible causes, and determine the appropriate next steps.

TUSAQ offers business software products and digital services covering customer management, enterprise operations, accounting, e-commerce, QR technologies, digital business cards, hosting, and other business needs.

This guide explains what information to prepare before contacting technical support, how to describe a problem, which files may be useful, and what sensitive information you should never share.

1. Why Is Detailed Information Important?

Technical issues can have many different causes.

An error may be related to the application, account permissions, browser settings, network connection, third-party services, or a particular configuration.

Without sufficient information, the support team may need to ask additional questions before investigating.

A well-prepared technical report can help:

• Identify the affected product or service

• Understand the symptoms of the issue

• Determine when and how the problem occurs

• Reproduce the issue when possible

• Distinguish application problems from local device issues

• Evaluate the business impact

• Reduce unnecessary communication

• Select appropriate troubleshooting steps

Providing complete information does not guarantee immediate resolution, but it can make the investigation more efficient.

2. Which Product or Service Is Affected?

Start by identifying the product or service where the issue occurs.

TUSAQ's software portfolio includes:

• TUSCRM: Customer Relationship Management

• TUSERP: Enterprise Resource Planning

• TUPEOPLE: Human Resource Management

• TUCOUNT: Cloud Accounting

• TUPOSPAY: POS and Inventory Management

• TUSCART: E-commerce Software

• TUPRESS: Content Management System

• TUSCAN: QR Technologies

• TUVIQ: Digital Business Cards

• TUSPAY: Collection and Payment Links

• TUBOOK: Appointment and Booking Management

• TUWORK: Industry Solutions

Your inquiry may also concern domain registration, hosting, SMS services, or custom software development.

If applicable, include the name of the affected module or feature.

For example, instead of reporting a general ERP problem, specify whether the issue concerns accounting, inventory, human resources, reporting, or another area.

3. How Should I Describe the Problem?

A good technical description answers three essential questions:

What were you trying to do?

Explain the action you intended to complete.

What did you expect to happen?

Describe the normal or desired result.

What happened instead?

Explain the actual behavior, including any error message.

For example:

Unclear Description:

"The system is not working."

Better Description:

"When I attempt to save a new customer record, the form remains on the same page and the record does not appear in the customer list."

The second description provides more useful information for investigation.

These examples are fictional and do not represent confirmed defects in TUSAQ products.

4. When Did the Issue Start?

Include the approximate date and time when you first noticed the problem.

Useful details include:

• The date the issue began

• The approximate time

• Your time zone

• Whether the issue occurred once or repeatedly

• Whether the issue started after a recent change

• Whether the problem happens at particular times

For intermittent issues, record several occurrences if possible.

Accurate timestamps can help correlate reported symptoms with available technical records.

5. What Are the Steps to Reproduce the Issue?

Reproduction steps explain how the problem can be observed again.

If possible, write the steps in order.

For example:

1. Sign in to the application.

2. Open the relevant module.

3. Select the feature where the problem occurs.

4. Enter the required information.

5. Submit or save the form.

6. Observe the unexpected result.

Describe only actions you actually performed.

If the problem occurs unpredictably, state that it is intermittent rather than inventing reproduction steps.

6. Should I Include the Exact Error Message?

Yes. Exact error messages can provide valuable technical information.

When an error appears:

• Copy the message accurately.

• Include any visible error code.

• Record the time it occurred.

• Explain which action triggered it.

• Attach a screenshot if the support channel allows it.

Avoid paraphrasing a technical error when the exact wording is available.

Before sharing, check whether the message contains confidential information such as access tokens, credentials, personal data, or private system paths.

7. Which Browser and Device Information Is Useful?

For web-based applications, browser and device details may help identify compatibility or session-related problems.

Relevant information can include:

Browser

• Browser name

• Browser version

• Whether the issue occurs in another browser

• Whether browser extensions may be involved

Device

• Desktop, laptop, tablet, or smartphone

• Operating system and version

• Whether the issue affects multiple devices

Connection

• Whether your internet connection is stable

• Whether the issue occurs on another network

• Whether a VPN or proxy is being used, if relevant

Share only the information necessary for troubleshooting.

8. Should I Provide Screenshots or Screen Recordings?

Screenshots and short screen recordings can be helpful when a problem is difficult to explain.

They may show:

• Error messages

• Unexpected page behavior

• Missing interface elements

• Incorrect visual layouts

• A sequence of actions leading to an issue

Before sharing visual materials:

1. Hide passwords and authentication codes.

2. Remove unnecessary personal information.

3. Conceal confidential customer or financial records.

4. Close unrelated applications and browser tabs.

5. Ensure the recording does not expose private notifications.

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

9. Are Technical Logs Helpful?

Technical logs may contain useful information about application errors, server responses, or failed operations.

Depending on the service, relevant records may include:

• Application error logs

• Web server logs

• Browser console errors

• Network request information

• Integration error responses

• Hosting-related diagnostic records

However, logs may also contain sensitive information.

Do not share complete logs without reviewing them.

If technical logs are needed, ask the support team which specific information is required and how it should be transferred securely.

Avoid modifying production settings or enabling extensive debugging without understanding the potential risks.

10. What Information Is Needed for Login Problems?

For account access issues, useful details include:

• Product or service name

• Official login page used

• Description of the login problem

• Exact error message, if available

• Approximate time of the attempt

• Browser and device information

• Whether password recovery was attempted

• Whether the issue affects one or multiple authorized users

Never include your password, one-time verification code, recovery code, or secret access token.

Account-related support may require appropriate identity or ownership verification.

11. What Information Is Needed for Domain and Hosting Issues?

For domain-related problems, you may need to provide:

• The affected domain name

• The type of issue

• The approximate time the problem began

• Relevant DNS record types and non-sensitive values

• Whether name servers were recently changed

• Whether the problem affects the website, email, or both

For hosting-related issues, useful details may include:

• The affected website address

• The hosting service involved

• The exact error displayed

• Whether the website is inaccessible to everyone or only certain users

• Recent configuration changes

• Whether the issue affects a specific page or the entire website

DNS and hosting changes can have significant effects on website and email availability.

Do not change important DNS records or server settings without understanding their consequences.

12. What Information Is Needed for Integration and API Issues?

When reporting an integration problem, explain:

• Which TUSAQ product is involved

• Which external service is connected

• What action or data transfer is failing

• Whether the integration previously worked

• The approximate time of the failure

• Any non-sensitive error codes

• Whether recent configuration changes were made

• Whether the issue affects all transactions or only specific cases

If an API request is involved, the support team may request sanitized technical details such as the endpoint, request method, response status, or a correlation identifier.

Never include secret API keys, bearer tokens, private credentials, or unredacted personal data in an ordinary support request.

Third-party integrations may require coordination with the external provider.

13. What Information Is Needed for Payment-Related Issues?

For issues involving payment or collection workflows, provide information that helps identify the affected operation without exposing financial credentials.

Useful details may include:

• Product or service name

• Approximate transaction date and time

• Non-sensitive transaction reference

• Type of payment issue

• Displayed error message

• Whether the issue occurred once or repeatedly

• Whether the transaction status is unclear

Do not send:

• Full payment card numbers

• Card security codes

• Online banking passwords

• One-time payment verification codes

• Unnecessary cardholder personal information

If a transaction appears duplicated or its status is uncertain, avoid repeating the payment without first checking the available transaction information or obtaining appropriate guidance.

14. Should I Explain How the Issue Affects My Business?

Yes. Business impact helps support personnel understand the practical consequences of a problem.

For example:

• A single user cannot access a non-critical feature.

• Multiple employees cannot complete a routine task.

• A website is unavailable to visitors.

• An important business workflow is interrupted.

• A suspected security issue may affect account integrity.

Describe the actual impact accurately.

Do not exaggerate urgency or assume that every issue qualifies for the highest support priority.

Priority handling depends on the relevant support process and service agreement.

15. Should I Mention Recent Changes?

Yes. Recent changes may provide useful clues.

Examples include:

• A browser or operating system update

• A newly installed browser extension

• A change in user permissions

• An integration configuration update

• A DNS or hosting modification

• A change to an external service

• A recently enabled module

However, a recent change does not automatically mean it caused the issue.

Share the information as context rather than presenting an unverified cause as fact.

16. What Troubleshooting Steps Should I Try First?

Before contacting support, you may consider basic, low-risk checks:

1. Confirm that your internet connection is working.

2. Verify that you are using the correct service address.

3. Refresh the affected page.

4. Try another updated browser when appropriate.

5. Check whether the issue affects another authorized user.

6. Review relevant Knowledge Base articles.

7. Record the exact error message.

8. Check for official service notices if available.

Avoid deleting important data, modifying production configurations, or repeatedly submitting financial transactions as troubleshooting experiments.

17. What Information Should I Never Share?

Protecting confidential information is essential during technical support.

Never share the following through ordinary support messages:

• Account passwords

• One-time authentication codes

• Account recovery codes

• Secret API keys

• Access tokens

• Private encryption keys

• Full payment card details

• Unnecessary customer records

• Confidential business documents unrelated to the issue

If sensitive diagnostic material is genuinely required, request an approved secure transfer method and share only the minimum necessary information.

18. How Do I Submit My Technical Report?

Start with the official TUSAQ website:

https://www.tusaq.com/

Use the relevant support channel available for your product or service.

Where a ticket system is available:

1. Select the appropriate support request option.

2. Identify the affected product.

3. Enter a descriptive subject.

4. Explain the issue and reproduction steps.

5. Include relevant timestamps and error messages.

6. Attach safe supporting files if supported.

7. Review the information for sensitive content.

8. Submit the request.

9. Save any confirmation or reference number provided.

The exact process depends on the service and support platform.

19. Example of a Complete Technical Support Request

Subject: Unable to Complete a Record Update

Product: TUSAQ Business Software

Issue Description:

Hello TUSAQ Support Team,

I am experiencing a problem while updating a record in the application.

Expected Result: The changes should be saved and displayed in the relevant record.

Actual Result: After submitting the form, the updated information does not appear.

Issue Started: Today, approximately 10:30 AM (UTC+3).

Steps to Reproduce:

1. Sign in to the application.

2. Open the relevant record.

3. Change an editable field.

4. Select the save option.

5. Check the record again.

Troubleshooting Already Attempted:

I refreshed the page and repeated the process in another browser.

Business Impact:

The issue is preventing me from completing a routine administrative task.

Could you please investigate and advise on the next steps?

Thank you.

Note: This is a fictional example intended to demonstrate a clear support request.

20. Technical Support Information Checklist

Before submitting your request, confirm that you have included the following information where relevant:

• Product or service name

• Clear subject

• Detailed issue description

• Expected and actual results

• Approximate date, time, and time zone

• Steps to reproduce the issue

• Exact error message or code

• Browser and device information

• Relevant recent changes

• Troubleshooting already attempted

• Actual business impact

• Safe screenshots or supporting files

• No passwords, secret keys, or confidential credentials

Not every issue requires every item. Provide the information that is relevant and reasonably available.

Frequently Asked Questions

Do I need technical knowledge to contact support?

No. Explain the problem in your own words. Clear descriptions and examples are often more useful than unfamiliar technical terminology.

Is a screenshot required?

Not always. Screenshots can help, but their availability and necessity depend on the issue and support channel.

Should I share my password so support can investigate?

No. Do not share passwords or authentication codes. Use official account recovery and authorized support procedures.

Can I report an issue without an error message?

Yes. Describe the unexpected behavior, the steps leading to it, and the result you expected.

What if the problem happens only sometimes?

Explain that the issue is intermittent and include examples of when it occurred.

Should I send the entire application database?

No. Do not send complete databases or sensitive datasets through ordinary support channels. Ask what specific diagnostic information is necessary.

Can I report issues involving third-party services?

Yes, you may ask about supported integrations or connected services. Investigation and resolution may depend on the external provider and applicable support scope.

Where can I request technical assistance?

Visit the official TUSAQ website and use the support channel associated with your product or service.

Conclusion

Accurate information is one of the most valuable tools in technical troubleshooting.

By identifying the affected product, describing the problem clearly, recording error messages, explaining the business impact, and protecting sensitive data, you can help make the support process more effective.

TUSAQ encourages clear communication and responsible information sharing to support reliable digital business operations.

Better Information. Faster Understanding. More Effective Support.

For technical assistance and product information, visit https://www.tusaq.com/.