Skip to content
Mistress.to Wiki
Back to Mistress.to

Account & Support

FAQ & Support

Start with the focused guide for the feature you are using. When you need help, give support a clear summary without sending sensitive information you do not need to share.

#Find the narrowest guide first

Use the wiki search for the feature name, the action you were taking, or the exact error phrase. In the screenshot below, press Cmd/Ctrl + K and try a query like Voice Call or Clear memory.

The most useful guide is usually the one closest to your current screen.

Find the narrow guide: Use Wiki search or Cmd/Ctrl + K

Search the feature name, the action, or the exact error phrase, not a broad description of the whole product.

Always redact: Chats, emails, balances, codes, payment data

Crop screenshots to the affected control and visible state only.

#When you contact support

Click Contact support in the Wiki header (or Contact us in main nav). The screenshot below is the official contact surface — name the feature, what you clicked, what happened, and whether it repeats.

If you attach a screenshot, crop it tightly and hide emails, balances, chats, codes, and payment data.

Four useful details: Where, selected control, observed result, repeatability

These let support reproduce a problem without a long private chat transcript.

Official routes: Contact support, product FAQ, or official Discord

Use the Contact support control in the Wiki header for the product contact surface.

Make a report actionable without oversharing

The goal is a reproducible state, not a complete personal account export. Include only what helps someone inspect the named feature.

IncludeExampleRedact or omit
Page and exact control“In an active chat, I selected Voice Call.”The full chat transcript or another unrelated page.
Observed state or error“The call returned to idle after microphone permission was allowed.”Speculation about account or payment details.
Repeatability“It still happens after refresh in the same chat.”A claim that it is fixed without retesting.
Tight screenshotThe error and the relevant control in one crop.Emails, balances, referral codes, wallet addresses, QR codes, invoice IDs, or private messages.
A good support message is short and specific

“Voice call will not start in this chat after I allowed my microphone” is more useful than “the site is broken.”

#Use a four-part support message

State where you were, what you selected, what happened, and whether it repeats. Example: “In an active chat, I selected Voice Call after allowing microphone access. The call returned to idle. It still happens after refresh.”

For billing issues, note whether you chose card or crypto at Payment Method in the screenshot below.

Exact clicks

What to click in Mistress.to

These paths use the labels currently shown in the product so you can move through the feature without guessing.

Open official support

  1. 01

    Select Contact support in the Wiki header, or Contact us in desktop navigation.

  2. 02

    Name the feature and the action you were taking.

  3. 03

    Include the exact error text if one appeared.

  4. 04

    Attach only a cropped screenshot with chats, balances, emails, codes, and payment data removed.

Common questions

Quick answers

Where should I go when a payment is incomplete?

Use the transaction or incomplete-payment route shown by the product, then contact support through the official path if the status is unclear.

What should I include in a bug report?

The feature, the action you took, what happened, whether it repeats, and a tightly cropped non-sensitive screenshot if it helps.

Where is Contact support in the Wiki?

It is in the Wiki header and opens the official product contact surface.

What should I search first?

Search an exact feature or action, such as Voice Call, Clear memory, Start Tasks, Generate Image, or Terminate Subscription.

Should I attach a full invoice screenshot?

Only if support asks, and redact all payment, transaction, wallet, and account details first.

What makes a support report actionable?

Name the page, the exact control you selected, what happened, the visible error or state, and whether it still happens after a refresh. A cropped screenshot is useful when it shows those details safely.

When should I use a dedicated guide instead of guessing in Settings?

Use the linked guide whenever the action changes data, billing, memory, or account access. It explains the scope of the control before you confirm it.

Can I share a full account dashboard or private chat to explain a problem?

Avoid it. Share only the smallest crop that demonstrates the issue, with personal, financial, referral, and conversation details removed.

How do I check if an instruction is still current?

Confirm the relevant control in the live product. For released changes, review the Changelog and the guide linked from that entry.

Did this guide answer your question?