Source connection or access
Connection, authorisation, account/property mapping, refresh, or provider-access problem.
Early-access support
Report a connection, data, or trust issue
Support is designed to preserve the evidence needed to investigate Prismatics without collecting source credentials.
Data or metric mismatch
A reproducible source-to-Prismatics discrepancy, missing date, currency, conversion, or freshness concern.
Insight or recommendation
A correctness, confidence, suppression, evidence, or recommendation-safety concern.
Export or report
CSV/PDF generation, missing fields, source labels, or reporting-output concern.
Privacy, security, or incident
A suspected privacy/security exposure or verified service-status concern.
Safe context to include
Include the client/workspace name, source and account/property identifier already visible in Prismatics, affected date range, last Prismatics refresh time, rules version or export ID when relevant, and a redacted screenshot if it helps reproduce the issue.
Never send credentials. Prismatics support will never ask for your password, OAuth authorisation code, access token, refresh token, API secret, or an unredacted credential screenshot.
How critical reports are handled
Credible privacy/security exposure, unsafe write behaviour, or a materially incorrect cross-source conclusion affecting multiple users is treated as critical and pauses cohort expansion until contained. A material single-user source failure, metric mismatch, or unsafe/unsupported recommendation is treated as high priority. Early access uses internal response targets rather than a public SLA.
Contact
Email founder@prismatics.co. Please use one of the categories above in the subject and keep credentials out of the message.