Find the point where the problem begins

Keep a record before refreshing

Note the error while it is visible. If the problem concerns a paid action, retain its confirmation and submission time before trying again. Those details can distinguish the initial request from another attempt and help explain whether access, generation or payment needs attention.

1. Check that the page opens and identify the signed-in registration.
2. Record the companion and precise failing action.
3. Compare the action with account access, balance and device requirements.
4. Keep the error wording and time before refreshing.

Separate access notices from page failures

An offer to subscribe or unlock an item can be an access condition rather than a broken page. A missing control may be specific to the character or mode. Check those requirements before treating the problem as a general browser fault.

Try a current browser and stable connection. If a privacy setting or extension blocks a needed resource, identify the affected request before changing a setting; do not disable protections indiscriminately. An inappropriate-content notice belongs to moderation, not proof of an outage. Do not repeatedly refresh or reword a prohibited request to evade it.

Check the selected media on its own terms

Playback needs a working audio output. A supported call also needs microphone permission, and a generated format may produce a silent clip. Review the companion's controls and stated output before attributing every media difference to the device.

For generation, inspect the original status and result first. Repeating a paid request can create a second charge rather than recover the missing one. Preserve the request reference, quantity and approximate time for support when the outcome remains unclear.

Explain both the steps and the scope

Tell support the device, browser, account and what you did immediately before the error. Say whether the same problem affects one thread, one feature or several pages. That scope is more useful than concluding from one result that the entire service is unavailable.

For login, include the sign-in method but no password or recovery code. For payments, use the receipt reference and amount. A companion's generated answer cannot investigate a real transaction, so direct account concerns to support@candymail.ai.

Your questions

How do I check whether the issue is wider than one action?

Compare other pages or actions without repeatedly spending on the same request. Note what works and what fails, along with the time and error. A single missing reply or output does not establish a service-wide outage.

Why does one character have different audio options?

Inspect the feature support on each profile and your account's access. Then check the output or microphone permission relevant to that action. Voice playback and calling are separate, and their availability need not be identical across companions.

What should I do before buying another generation?

Look for the original request, recorded charge and any output or status entry. Keep its reference and time. If the result remains unclear, ask support to inspect that action rather than assuming another paid attempt will restore the first one.