Sustema

D10

Get help or report incorrect information

Candidate documentation for reading and synthetic examples. Account creation, live API access, SDKs, collections and MCP are not available here. A released service profile and matching integration instructions are required before use.

For a technical or account issue, use Reports with a safe request/operation reference, the time, the action you attempted and the relevant error. For a disputed field, start from the permitted result or owned reference and identify the exact attribute and your reason. Supply only the evidence requested through the approved route.

Follow the case for its current status and the next action. A report acknowledgement is not a corrected fact, a refund or confirmation that the service recovered. An engineering ticket closing is not itself a verified customer outcome. A report may produce a permitted explanation, a request for information, a bounded recheck or a truthful non-fix disposition.

If you cannot sign in, use the supported identity recovery or bounded pre-login access route. Acknowledgement must not reveal whether an account exists. Control of a reply email or possession of a case reference does not bypass MFA or restore company authority. Do not send passwords, access tokens, client secrets, recovery codes or unrelated customer data.

The defined account/security and owned reporting/recovery paths remain accessible at zero matching credits, subject to current authority, rights, retention and abuse controls. Response times and escalation commitments must come from the published support policy; none are invented here.

Private reporting and identity recovery are not connected from these reading pages. For a general conversation, contact Sustema. Do not send secrets or private datasets through a general enquiry.