real time web analytics

6 Tips to Manage Your OpenText Support Tickets Like a Boss

Originally published in November 2020. Last updated in November 2026.

As the old saying goes, in this world nothing is certain, except that support tickets never stop arriving. If you are responsible for managing enterprise applications, you probably already know the frustration of long ticket closing cycles. For this short article, we talked to former and current OpenText Support staffers, and we are happy to share some tips on speeding up the process of resolving your next OpenText support ticket.

 

1. OpenText support channels

OpenText customers can submit support tickets in three ways: through the OpenText MySupport portal, by phone, or by email at support@opentext.com.

The recommended and most efficient option is to submit tickets through the MySupport portal. If you don’t have access yet, you will first need to register your company and create an account before submitting your first ticket.

Important: If your organization purchased OpenText solutions through SAP, support requests should be submitted through SAP rather than directly to OpenText. However, you will still be able to access OpenText documentation and download software through the MySupport portal.

 

2. Issue description in OpenText MySupport

You might be surprised how often customers submit support tickets with messages like “We need support” or “We have an issue. Please help,” accompanied by a screenshot of a log file.

Unfortunately, this doesn’t give the support team much to work with and can slow down the troubleshooting process.

To get things moving faster, provide a clear and detailed description of the issue from the start. Try to organize the information in a structured way and include:

  • Issue description: What exactly is happening? What did you expect to happen instead?

  • Steps to reproduce: Describe the steps that led to the issue, in the order they occurred.

  • Date and time: When did the issue occur? If possible, provide the date, time, and relevant time zone, or the time range when the issue was observed.

  • Error messages and logs: Include relevant error messages, screenshots, and log files (if possible).

The more useful information you provide upfront, the easier it is for the support team to understand the problem, investigate it, and get you closer to a solution.

 

3. Adding all resources to each OpenText support ticket

As a general rule, it’s better to provide more information than not enough. However, when adding supporting materials such as screenshots, log files, or configuration files, upload them as attachments rather than inserting them directly into the ticket description. Whenever possible, attach the complete log file instead of just a few selected lines. This is especially important during new implementations or product upgrades, when customers often need to submit multiple support tickets related to the same project.

We know it can feel repetitive to share the same information or upload the same project files again, especially when you’ve already shared them with OpenText Support in previous tickets. Unfortunately, this can actually slow things down. There are several reasons why OpenText Support cannot always reuse information from another ticket:

  • The environment may have changed. A hotfix or configuration change may have been applied since the previous ticket was submitted.

  • The provided files may be outdated or incomplete. Previously provided files may not cover the time period relevant to the new issue.

  • Information must be verified. Before reusing files or details from another ticket, the support team may need to confirm with you that they are still relevant.

The best approach is to treat every new ticket as a separate case and include all relevant information and files from the beginning. It may take a few extra minutes to prepare your ticket, but it can save days of unnecessary back-and-forth and help the support team start investigating much sooner.

 

4. Full logs 

As mentioned earlier, always try to attach complete log files rather than selected extracts or screenshots. If the issue can be reproduced, enabling debug or verbose logging, where possible, can also provide valuable information for troubleshooting.

The more detailed the logs, the easier it is for the support team to identify what went wrong and determine the root cause. This can often help speed up the resolution process.

We understand, however, why customers may hesitate to enable debug logging in a production (PROD) environment. Additional logging can affect system performance. According to OpenText Professional Services, the impact can be as high as 10% in certain circumstances, depending on the product, environment, and logging configuration.

If your solution is hosted in the OpenText Cloud under a SaaS subscription, you may not have direct access to the logs at all. This depends on the product and hosting arrangement. In that case, you’ll need to work with OpenText Support to reproduce the issue and help them collect the necessary logs from the hosted environment.

Finding the right balance between collecting enough diagnostic information and protecting production performance is important. If you’re unsure, discuss the logging requirements with your technical team or OpenText Support before making changes.

Keep in mind that logs are sometimes the only source of information that can help identify the cause of an issue. Without them, troubleshooting may become much more difficult and take considerably longer.

 

5. System details

One thing customers often overlook when submitting a support ticket is providing basic system information. These details help the support team understand your environment and investigate the issue more efficiently.

For on-premises and customer-managed environments, always include the following information:

  • OpenText product: Product name, version, and build number.

  • Operating system: OS name and type, version, and build number.

  • Database: Database platform, version, and build number.

If you’re using an OpenText Cloud SaaS solution, you may not have access to the underlying operating system and database details. In that case, provide the product name, version, and any build information available to you. OpenText Support can identify the remaining infrastructure details from their side.

Providing as much information as you can upfront helps OpenText Support understand your environment, narrow down potential causes, and avoid unnecessary back-and-forth before troubleshooting can begin.

 

6. Contact details

Provide a direct phone number for someone familiar with the issue, rather than a general office number. We know not everyone enjoys unexpected calls (some of us would rather exchange a hundred emails!), but a quick conversation can often save a lot of time.

If you’re using an OpenText Cloud SaaS solution, your organization will typically designate specific Points of Contact (POCs) during onboarding. Make sure these contacts understand your implementation and can actively participate in troubleshooting and testing. Remember: Users who have Business Administrator access in OpenText Cloud SaaS solutions, must hold the required OpenText Cloud Practitioner product certification.

For on-premises solutions, simply make sure the person handling the ticket can be reached directly.

 

Looking for OpenText Support?

Unfortunately, not every issue falls within the scope of standard OpenText Support. Sometimes a ticket is declined because the requested work is outside the support agreement. This can happen for several reasons:

  • Customizations: The issue is related to custom code, scripts, or modifications made to the standard product.

  • Third-party integrations: The problem originates from an integration with a third-party application.

  • Product bugs: The issue is caused by a software defect that can only be addressed in a future product release or hotfix.

  • Out-of-scope requests: The request involves configuration changes, enhancements, or other services that are not covered by standard support.

  • Environment-related issues: The root cause lies in the underlying infrastructure, operating system, database, or another component outside OpenText’s responsibility.

If you find yourself in this situation, we’re happy to help. Feel free to schedule a free OpenText advisory session with our team.

Headquartered in Boston, Massachusetts, Ecodocx brings together experienced developers and support engineers who have worked with OpenText products and modules for many years. With more than 600 projects delivered, we help organizations implement, customize, optimize, and support their OpenText solutions.

You can also learn more about our OpenText Managed Support services.

When standard support isn’t enough, we’re here to help.

 

opentext managed support

Join OpenText professionals & get inside knowledge every week

Subscribe to our blog