> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anistratenco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Contact us

> Find the right place for a question, a problem, or an idea.

## Agent context: support routing

Reviewed 2026-09-04. This page routes people to existing support surfaces; it does not submit a request or prove delivery. General support and product bugs belong at [https://anistratenco.com/contact](https://anistratenco.com/contact). The user selects Report a bug in that form; do not promise a query-string preset until the application release is verified. Feature ideas belong on the public UserJot board. Availability belongs on the incident.io-backed status site. Never put health information, account credentials, payment details, recovery codes, or gift links in public feedback. Do not invent a response-time guarantee. Preserve any visible error reference without copying sensitive conversation content. Contact support is not emergency medical care. Recheck when contact categories, submission behavior, or destination URLs change.

You do not need to know what went wrong to ask for help. Start with what you were trying to do.

<Columns cols={3}>
  <Card title="Ask for help" icon="comments" href="https://anistratenco.com/contact">
    Use our dedicated contact form for an account or product question.
  </Card>

  <Card title="Suggest a feature" icon="lightbulb" href="https://anistratenco.userjot.com">
    Share an idea and the problem it would solve. This board is public.
  </Card>

  <Card title="Check service status" icon="signal" href="https://status.anistratenco.com">
    See availability updates before retrying something that is not working.
  </Card>
</Columns>

## Report a problem

<Steps>
  <Step title="Open the contact form">
    [Contact Anistratenco](https://anistratenco.com/contact) and choose **Report a bug** for a product problem.
  </Step>

  <Step title="Tell us what happened">
    Say what you tried, what you expected, and what happened instead. Include the approximate time and a visible error reference if you have one.
  </Step>

  <Step title="Review before sending">
    Remove private details from screenshots. Review the form, submit it, and check the result it shows. Opening the form does not send your message.
  </Step>
</Steps>

<Warning>
  Do not include passwords, recovery codes, full payment details, or gift links. Share only the information needed to explain the problem; avoid unrelated health records or conversation content.
</Warning>

<Note>
  Feature-board posts are public. Keep account-specific problems in the dedicated contact form, and do not use either surface as a place to store sensitive health information.
</Note>

<section className="help-faq" aria-labelledby="page-questions">
  <h2 id="page-questions">Questions? Answers.</h2>

  <Accordion title="Is this a bug or a feature request?">
    If something available does not work as expected, use **Report a bug** in the contact form. If you want a new capability or a different workflow, use the public feature board. Describe your goal rather than just naming a button you want.
  </Accordion>

  <Accordion title="Should I send the same request again?">
    First check the form's result and [service status](https://status.anistratenco.com). For a payment or another external action, check whether the original action completed before repeating it. Keep any visible reference so support can distinguish the attempts.
  </Accordion>

  <Accordion title="Where can I find help with my settings?">
    [Get started](/quickstart#find-your-settings) links to the voice, appearance, preferences, data, account, and billing guides. Each explains the relevant controls and limitations.
  </Accordion>

  <Accordion title="Can support help with an urgent medical problem?">
    This is product support, not an emergency or clinical-care service. For an urgent medical concern, contact an appropriate local emergency service or qualified health professional.
  </Accordion>
</section>