AivahHelp CenterGo to Aivah
⌘K
No guide matched “”

Try fewer words or contact support for help.

Contact support

Contact Aivah support

Prepare a safe, reproducible support request without sending passwords, payment details, or customer records.

Who this is forAnyone who needs product, account, support, or sales help from Aivah

You will achieveSend a concise support request with enough context to investigate and without exposing secrets or unnecessary personal information.

Before you beginReview the requirements before changing anything.

Last reviewed 10 July 2026Owner: Product EducationCurrent guide
On this page
  1. Before you begin
  2. Steps
  3. 1. Remove sensitive information
  4. 2. Write a reproducible summary
  5. 3. Use an official contact path
  6. 4. Preserve the original state when safe
  7. Expected result
  8. Status meanings
  9. Usage credit impact
  10. Information stored or shared
  11. Limits and permanent actions
  12. Common problems and recovery
  13. Next step

Use this guide when troubleshooting has not resolved a product or account problem, or when you need sales or support help. You will prepare a concise report that Aivah can investigate without exposing secrets.

Before you begin

Try the relevant recovery in Troubleshoot Aivah, then collect:

  • Your account email.
  • The name of the affected AI employee.
  • The workspace area where the problem occurred.
  • The approximate date and time.
  • What you expected.
  • What happened instead.
  • The smallest steps that reproduce the issue.
  • A screenshot only when it contains no private customer information or secret values.

Steps

1. Remove sensitive information

Do not include passwords, reset links, payment details, private connection values, WhatsApp pairing images, access tokens, or full customer records.

If a screenshot contains sensitive information, create a new safe screenshot or describe the visible status in words.

2. Write a reproducible summary

Use this structure:

  • Account: [account email]
  • AI employee: [name, if relevant]
  • Workspace area: [exact label]
  • Approximate time: [date, time, and time zone]
  • Expected: [expected result]
  • Actual: [what happened]
  • Steps: [smallest repeatable sequence]
  • Visible status or error: [exact non-sensitive wording]

3. Use an official contact path

Use the official Aivah contact page or email aivah@opinionai.ai.

4. Preserve the original state when safe

Avoid deleting the affected employee, conversation, job, share, or connection before support reviews the problem unless leaving it active creates a safety or business risk. Do not repeat a payment or irreversible action while its result is unclear.

Expected result

You have sent a clear request through an official contact path with the affected area, approximate time, expected and actual results, reproducible steps, and no secrets.

Status meanings

Use any sent confirmation provided by the contact channel as evidence that your request left your device. This Help Center does not promise a ticket state, response time, or resolution time. If no confirmation appears, avoid sending repeated copies with additional private information; verify the address or use the other official contact path.

Usage credit impact

This article does not define a usage-credit charge for contacting support. Reproducing the issue inside Aivah can use supported activity, so avoid unnecessary duplicate tests.

Information stored or shared

Your support request is sent outside the workspace area where the issue occurred. Include only the minimum account and diagnostic information needed to investigate it.

Do not send full customer conversations or records unless Aivah provides an approved secure method and your organization authorizes the disclosure.

Limits and permanent actions

  • This article does not promise a response time, service level, refund, recovery, or technical outcome.
  • Support cannot safely investigate a secret sent in normal text; if one was exposed, follow your organization's process for that secret.
  • Third-party phone, Slack, WhatsApp, billing, or connected-service problems can also require action in that service.
  • Do not repeat a payment, deletion, external action, or manual job run merely to create more evidence.

Common problems and recovery

ProblemWhat to try
You cannot reproduce the issueInclude the last known time, exact screen label, visible state, and what changed before the problem appeared.
A screenshot contains private dataDo not send it. Recreate a safe screenshot or describe the status in words.
A private value was already exposedStop using it and follow your organization's approved incident and replacement process. Do not copy it into another message.
Payment verification is still pendingDo not pay again. Check the plan, balance, and billing area, then include only the approximate payment time.
The issue affects an outside serviceInclude the service name and action, but not its credentials or full records.

Next step

While waiting, avoid repeating irreversible actions. Review privacy, consent, and safe data handling if the issue involves personal information, public experiences, calls, or connected services.

Keep going