Get help through the right support route

Start Here

Most support outcomes are better when the request starts in the right place. This page exists to help you identify the correct support route before you send a message.

If you are not sure whether your issue is technical, billing-related, security-sensitive, or simply a general help request, this page should be your first stop.

How Support Works

PsyData Labs public support is structured so different types of requests can be routed more appropriately.

In general:

• General questions can use standard support routes
• Technical issues should follow technical support guidance
• Billing issues should go through billing-specific routing
• Security concerns should use security reporting paths

This separation helps reduce delay, improve clarity, and protect higher-sensitivity workflows.

Choose the Right Path

Use the table below to pick the best starting route based on the type of issue you have.

What to Include

Clear support requests are usually easier to route and resolve.

Good support requests often include:

• A short description of the problem or request
• What you expected to happen
• What actually happened instead
• When the issue began
• Any relevant account, environment, or product context you can safely provide
• Whether the issue is blocking, urgent, or informational

Priority and Urgency

Not every issue is equally urgent. Good support requests explain the actual impact clearly.

For example, urgency may be higher when:

• A production workflow is blocked
• A critical business process is affected
• There is a security concern or abuse scenario
• The issue has broad impact across users or systems

Urgency should be explained honestly and specifically. Marking everything as urgent makes routing harder.

Before You Contact Support

Before sending a request, it often helps to confirm a few basics first.

• Check whether the issue is already explained by a support, docs, or status page
• Confirm you have the correct account or environment context
• Gather the minimal information needed to describe the issue clearly
• Do not include secrets or unsafe sensitive data in a general support email

Special Cases

Some issues should not be treated like ordinary support requests.

• Security or abuse concerns should go to security reporting paths
• Billing or refund questions should go to billing support
• Higher-priority unresolved matters may need escalation routing

Using the right specialized route improves both speed and handling quality.

Next Steps

After this page, most visitors should continue to one of the following:

• Account Support for access and account-related problems
• Technical Support for troubleshooting and technical failures
• Billing Support for invoice, refund, and payment issues
• Security Reporting for security-sensitive concerns
• Escalation Paths when the issue needs structured escalation