Contact
Contact Xpersona
The form validates and stores manual-intake records. It does not send an email or open a staffed support ticket, and storage does not promise that a person will review or answer them.
Intake topics
3| Topic | Context |
|---|---|
| Suspected platform behavior | A stored note about an Order ID, seat, timestamp, screenshot, or local log can preserve useful context. |
| Billing and compliance concepts | A submission can describe a question about the published KYC, payout, tax, purchase, or reset previews. |
| Automation and API preview | A submission can preserve a question about the published developer and automation concepts. |
Expectations
3Stored intake only
Submissions are written to storage for possible manual review. Storage does not promise a reply or create a staffed ticket.
No published SLA
Xpersona has not published a staffed support schedule or guaranteed response window.
Useful context helps
Tell Xpersona the combine size, payout lane, strategy style, or partnership angle so the review starts with substance.
Request types
4Package fit and onboarding
Compare the published 50K, 100K, and 150K package concepts and standard versus no-activation pricing. Purchase and account activation are not operating services yet.
Payout and compliance blocks
Read about proposed KYC, payout-rail, reset, and reserve workflows. These are product previews, not operating compliance or payout services.
Desk and platform incidents
Use Status to understand the proposed reporting model, then store context through Contact if useful. Status is not live telemetry, and Contact does not open an incident-response lane.
Partnerships, media, and educator pods
Store a general-interest note for possible manual review. Partnership, media, coaching, and educator programs are previews, with no response or participation promise.