How can we help?
Search product help, browse common topics, or ask Maya Support to triage the issue and prepare a human-reviewed ticket.
11 suggested articles
FAQ shortcuts
Find the right FAQ faster
Start with the support FAQ paths that solve common account, billing, privacy, Maya, matching, and messaging issues.
Recommended topics
Suggested articles
Answers before you open a ticket
Start here for common product, account, billing, privacy, Maya, matching, and message issues. Sensitive actions still require human review.
What Maya Support can do todayMaya can triage issues, ask for missing context, suggest safe next steps, and prepare reviewed tickets.
Maya Support can help triage an issue, ask one useful follow-up question at a time, suggest safe troubleshooting steps, and prepare a support ticket with the conversation attached. It does not perform account, billing, privacy, safety, or security actions autonomously.
What happens after you create a ticketThe ticket is attached to your account and the support team reviews the full conversation.
After a ticket is created, it is attached to your account, the support team is notified, and a human reviews the conversation before replying or taking action. You do not need to repeat the context already captured by Maya Support.
Billing issues require human reviewMaya can collect billing context, but plan and payment actions stay behind operator review.
Billing and subscription topics are supported, but they require human review. Share the invoice, plan, payment, or Stripe-related issue and whether it is blocking your work. Maya will collect the context for the reviewer.
Account and privacy changes stay controlledSupport can capture the issue, but sensitive account or privacy changes are never automatic.
For account, privacy, and safety-sensitive cases, Maya Support collects the details and prepares a human-reviewed handoff. It will not change account settings, expose private data, or act on another user's account.
Report a security issueVulnerabilities and data exposure concerns should go straight to [email protected].
For vulnerability reports, suspected data exposure, abuse, or security-sensitive issues, email [email protected]. You can still create a support ticket, but security disclosures should bypass normal support routing.
Fix an expired sessionSign in again when your token expires instead of retrying the same protected action.
If your session expired, sign in again and retry the protected action. In local development, use dev login when available. Expired tokens are treated as signed out rather than as a raw validation error.
Improve matching and goal recommendationsProfile completeness, active goals, and network context all influence matching quality.
Matching depends on your profile, active goal, network context, and recent signals. If recommendations look wrong, share the page, the match you expected, and the goal or profile context that should have influenced the result.
Troubleshoot messages and introductionsFor blank screens or failed sends, capture the page, action, and whether retrying changes the result.
For message or introduction issues, share the page, the last action you took, the visible error or blank state, and whether a refresh or sign-in retry changes the result. Maya can then decide whether to keep troubleshooting or create a ticket.
Fix workspace and company-page contextWorkspace issues are usually tied to the selected workspace, role, invite, or company page.
If workspace switching, invites, roles, or company pages look wrong, share the workspace name, the page URL, the action you took, and whether the issue appears in Personal, company, or team context. Maya can attach that context to a reviewed ticket so the team can check permissions safely.
Report slow, blank, or unavailable pagesFor product availability issues, include the page, time, last action, and whether retrying changes it.
When a page is slow, blank, or unavailable, include the URL, approximate time, browser, last action, and whether refresh or sign-in retry changes the result. Maya will first collect diagnostics, then create a human-reviewed ticket when the issue is still blocking you.
Write a support ticket that gets solved fasterA strong ticket includes the page, expected result, actual result, urgency, and screenshots when useful.
The fastest support tickets include five details: the page URL, what you expected, what actually happened, whether it blocks your work, and any screenshot or exact error text. Maya Support asks for these details one at a time so you do not need to format a ticket manually.
More help
Get a human reviewer when it matters
Billing, account, privacy, safety, and security-sensitive cases stay behind human review. Maya can collect context, but it will not take those actions autonomously.