Structured Requests

Use the right path for service requests

This page explains how structured service requests should be approached across PsyData Labs. It is intended for access-change requests, setup help, operational asks, and support-adjacent requests that are not exactly incidents, bugs, or billing/security matters.

Service Requests Routing Aware Public Guidance
Read Guide Open Get Help

Guide

Service Requests

Use this page for structured asks that need review, routing, or support-adjacent handling.

Status

Active

Audience

Users, clients, partners, and stakeholders with non-incident service-related requests

Support Scope

Access changes, setup help, operational asks, and structured service-routing questions

Primary Route

support@psydata.net or help@psydata.net

Overview

Not every request is a failure, bug, security issue, or billing matter. Some requests are simply structured asks that need the right operational path.

This page helps distinguish service requests from incidents and explains how to submit them in a way that is easier to review and route.

Request Types

Many service requests fall into a few common categories.

Request Type Typical Example Best Route Urgency Pattern
Access Change Request A legitimate request to review or change access state, where allowed General support / service request routing Normal to Priority
Operational Request A structured ask related to a workflow, setup, or service-adjacent operation General support / service request routing Normal
Configuration / Setup Help A request for help completing a supported configuration or setup path General or technical routing depending on scope Normal to Priority
Unclear Mixed Request A request that does not clearly fit support, billing, security, or escalation alone Get Help / general routing first Varies

When to Use Service Requests

Service-request routing is usually appropriate when:

  • You are asking for a change, review, or supported operational action
  • The issue is not primarily a bug, outage, or security-sensitive concern
  • You need structured help with setup, onboarding, or configuration direction
  • The ask depends on review or approval rather than immediate break-fix support

What to Include

Good service requests explain what is being requested, why it is needed, and what context matters.

Helpful request details may include:

  • A concise statement of the request
  • The reason for the request
  • The relevant account, workflow, or operational context
  • Any timing considerations or deadlines
  • Whether the request is routine, urgent, or dependent on another issue

Review and Routing

Some service requests can be handled directly, while others may need review, clarification, or routing to a more appropriate function.

This is normal. Structured requests often require more context than standard support tickets, especially when access, operations, or coordination are involved.

Priority and Timing

Service requests vary in urgency. Some are routine and low-pressure, while others may affect near-term operational needs.

If timing matters, explain why. Support quality improves when urgency is linked to actual operational impact instead of vague priority language.

Request Quality

The best service requests are specific, scoped, and easy to understand.

  • Say exactly what is being requested
  • Explain why the request matters
  • Avoid mixing multiple unrelated issues into one request when possible
  • Use the right specialized route instead when the issue is really billing, security, or escalation-driven

Next Steps

After reading this page, most visitors should do one of the following:

  • Email support@psydata.net or help@psydata.net for structured service requests
  • Use Technical Support if the issue is actually a bug or system failure
  • Use Get Help if you are still unsure which route best fits the request

Helpful Notes

A few reminders for structured requests

These reminders usually make service requests easier to review and route.

Recommended

Be explicit about the ask

The clearer the request itself is, the easier it is to route and review.

Priority

Explain why it matters

Timing and business context help support understand why a request is important.

Important

Use the specialized route when needed

If the request is actually about billing, security, or a serious incident, use the correct specialized path instead.

Contact

Service request contacts

Use these routes for structured asks, operational requests, and support-adjacent request handling.

General Service Request Routing

For structured requests, setup help, access-change requests, and other support-adjacent asks.