Help center
Support
Support is currently public reference material plus stored intake.
Mayospell organizes account, billing, payout, rule, and platform concepts so a stored submission can include useful context. The Status route is reference-only, and no staffed escalation or live service-health feed is offered.
Contact intake
Stored intake only
Public status
Reference only
Live service SLA
Not published
Support snapshot
Mayospell support coverage is deliberately limited and explicit.
Its metrics and channels do not describe Mayospell. Mayospell currently offers public help articles and a stored contact form without guaranteed human review, a response, or a live-agent SLA.
Mayospell support snapshot: July 6, 2026. Current Mayospell support posture: public help articles, stored contact intake, reference-only status, and evidence-first incident handling that starts with stopping trading immediately.
Help-first support
Mayospell routes common questions through the public Help Center first, then stores a detailed contact request when a manual review may help.
Published channel coverage
Mayospell publishes the channels it actually operates: public help and a stored contact form. Live chat, phone, SMS, WhatsApp, and response-time guarantees are not offered.
Public support map
Help, Status, Contact, the trading room, and the learning routes form one navigable Mayospell support map; none implies a staffed real-time channel.
Incidents stay evidence-driven
For a suspected platform issue, stop sending orders and capture the seat, time, Order ID, screenshot, and relevant local logs before using Mayospell's stored contact intake.
Channel map
Published support channels and Mayospell availability are separate facts.
The Mayospell column states which channels exist and which do not, without turning another firm's coverage into an implied service promise.
Lane
Mayospell channel
Mayospell
Why it matters
AI concierge
Mayospell Help is the primary first-stop reference surface.
Not available. Mayospell currently provides public help articles and a stored contact form; there is no 24/7 desk bot or human handoff promise.
Planned capability; no support coverage is implied.
Chat
Mayospell does not expose live chat; Contact stores a manual-intake request.
Not available. Use the contact form for a stored manual-review request.
No real-time response promise is published.
Phone
Mayospell does not publish a phone-support lane.
Not available. Mayospell does not publish a phone-support number.
Use the stored contact intake instead.
Email / SMS / WhatsApp
Mayospell does not advertise email, SMS, or WhatsApp as staffed support channels.
Not available as advertised service channels. Contact submissions are stored for manual review; they are not a staffed SMS, WhatsApp, or email desk.
No channel-specific SLA is published.
Status page
Mayospell's Status route documents the intended incident vocabulary but is not connected to production telemetry.
The current status route documents the systems and incident states Mayospell intends to report; it is not wired to production telemetry.
Reference surface only, not live uptime evidence.
Public social-support handle
Mayospell does not publish an official social-support handle on this site.
Not available. Mayospell does not publish an official social-support handle on this site.
Do not send account details to an unverified social profile.
Support state
The current support posture is public self-service plus stored manual intake.
Mayospell does not guarantee human review or a response and does not publish a staffed live-agent schedule, channel SLA, phone line, or production status feed.
Lane
State
Mayospell reference
Mayospell move
Help center
Public self-service
Public Help handles the first pass across common account, platform, and policy questions; no staffed escalation is promised.
Mayospell currently routes common questions to public articles. A live concierge and staffed handoff are not available.
Contact intake
Stored intake only
Mayospell stores Contact submissions for possible manual review and does not promise around-the-clock follow-up.
Mayospell stores form submissions as manual-intake records. It does not guarantee human review or advertise text, WhatsApp, or around-the-clock follow-up.
Phone support
Not available
Mayospell does not publish a voice-support lane or business-hour coverage.
Mayospell does not publish a phone-support lane or business-hour coverage.
Platform incidents
Manual intake only
Stop trading first, then preserve Order IDs, screenshots, timestamps, and performance evidence before submitting Contact intake.
Stop sending new orders, capture evidence, and use the stored contact form. There is no live incident desk or automatic evidence export promise.
Public health routes
Reference routes
Status and Help reduce uncertainty before a Contact request is submitted; community and learning routes are not support channels.
Help contains public guidance; Status documents the reporting model but is not connected to live telemetry. Use Contact for manual intake.
Support flow
Step
Mayospell reference
Mayospell
Ask the concierge first
Public Help articles act as the first layer for common questions and route guidance.
Search the Mayospell Help Center first; automated concierge and human live-chat escalation are not currently offered.
Choose the right lane
Mayospell currently offers public references and stored Contact intake, not live chat, phone, SMS, or WhatsApp escalation.
Use the public Help and Status references, then store context through Contact. Storage does not guarantee that a person will review or answer it.
Check public health
Status and Help help traders self-diagnose before submitting a detailed Contact request.
Use Help for policy guidance. The current Status page is a reporting-model reference and does not confirm live room, webhook, or market-data health.
Escalate with evidence
The strongest support path uses concrete account, platform, and billing context rather than vague complaints.
Include the seat, time, Order ID, screenshots, and relevant local logs in the contact request; automatic evidence attachment is not available.
Evidence pack
Suspected platform behavior
If storing a note, include the Order ID, seat, time, screenshot, and relevant local logs. Mayospell does not automatically export evidence or operate a live incident desk.
Billing or payout preview question
Describe the package, preview state, and question. KYC, purchase, reset, reserve, and payout workflows are not operating services.
Automation preview question
Describe the device, project, and proposed workflow. Contact does not issue credentials, enable live API routing, or troubleshoot third-party code.
Review-model question
Name the published lane, tier, or reserve concept. Review notes and moderation states shown on the site are previews, not live desk decisions.
Public routes
Public routes explain the proposed operating model.
Help contains reference material, Status describes a reporting model, community routes are program previews, and Contact stores a note. None is a human escalation path.
Help Center
Read public reference articles about pricing and proposed reset, payout, account-state, and options-policy concepts before storing a request.
Status page
The current page explains Mayospell's intended incident vocabulary. It is not connected to production monitoring and must not be read as live uptime confirmation.
Community support
Community and coach pages describe the education model. They are not staffed support channels or a substitute for a formal contact request.
Trader Support escalation
The contact form stores manual-intake records. Mayospell does not guarantee human review or a response, and it publishes no live-agent coverage or response time.
Support routes
Use the route that matches the question, then store context for possible manual review.
Help provides public policy guidance; Status is a reporting-model reference; Contact stores a request. None of those routes imply real-time human support.
Open help center
Read public reference material about billing, payout, limit, reset, and options-policy concepts. These articles do not activate those preview workflows.
Open status page
Read the proposed room, data, webhook, and account-service reporting model. This reference page does not show live health or maintenance.
Open contact form
Store a combine, partnership, compliance, or general-interest note for possible manual review. No reply, priority, or human follow-up is guaranteed.
Open Desk TV preview
Read a proposed desk-media format. Mayospell does not publish a live stream, recorded show, schedule, or media-based support channel.
Open review preview
Inspect a product mockup for proposed KYC, payout-rail, tax, and review states. It does not perform identity review or payout processing.
Open billing and reset preview
Inspect proposed rebill, reset-price, purchase-gate, and Reset Bank states. No checkout, rebill, reset, or billing action is available there.
Open member preview
Inspect a member-area preview of package, software, funded-route, and proof concepts. It is not an active funded account service.
Open POP preview
View synthetic POP-card format examples. Mayospell does not currently operate a verified payout-history or share-state archive.
Proof routes
Support has no verified Mayospell payout artifacts to cite yet.
Synthetic POP-card examples are excluded from support evidence. Only settlement-backed public records belong here.
No verified Mayospell payout records are published. The POP Cards route contains sample format records only.
Next surface