Contact Fish Voice Support

Start with the support lane

Write to support@fishvoices.com. Put the request type in the subject: product, account, billing, refund, API or integration, partnership, security, misuse, or editorial correction.

One address gives the team a single review trail, while a clear subject prevents a security report from being treated like a general product question.

Build a useful request

For a product or account issue, include the affected account email, page or workflow, expected result, actual result, approximate time, and steps that reproduce the problem. Add a generation or transaction identifier when one is visible.

For billing and refund questions, identify the account and include the order or receipt ID if available. Check the refund policy for eligibility and timing. Do not send passwords, complete payment-card numbers, private keys, or unnecessary identity documents.

For an API or integration question, describe the endpoint or workflow, response code, time window, and a redacted request example. Remove tokens and personal or proprietary content before attaching logs.

For voice cloning or voice design questions, name the workflow step and describe the expected and observed result without attaching source recordings unless support requests them.

What support can decide

Support can investigate Fish Voice product behavior, account access, transactions, refund-policy requests, integrations, documented partnerships, and corrections to site content. The team may ask for a smaller reproduction or additional ownership evidence before changing an account.

Support cannot approve a user's rights to a voice, script, character, or recording, and cannot guarantee how an outside platform or authority will treat generated audio. Those questions require the relevant rights holder, platform, or qualified adviser.

Security and misuse reports

Mark urgent security or suspected misuse reports clearly. Include the affected URL, voice, account, or generation reference; what you observed; when it occurred; and a safe way to reproduce or verify it. For a voice-removal request, include a link to the voice and explain your relationship to the represented person or rights holder.

Do not publicly disclose access credentials or sensitive exploit details while a report is under review. Use the support address so the team can preserve context and follow up.

Response context

Requests are reviewed according to subject and available evidence. A concise timeline and reproducible details usually reduce follow-up. Send a new message if the scope materially changes rather than mixing unrelated account, partnership, and security questions into one thread.