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

# Support

> How to reach the VisIQ team — email, the in-product dashboard, and where to file the details that get you a fast answer.

Need a hand? Here is how to reach the VisIQ team and what to include so we can
help quickly.

***

## Contact

<CardGroup cols={2}>
  <Card title="Email us" icon="envelope" href="mailto:hello@visiqlabs.com">
    Reach the VisIQ team at **[hello@visiqlabs.com](mailto:hello@visiqlabs.com)** for setup help, questions
    about governance behavior, connector access, or anything else.
  </Card>

  <Card title="Dashboard" icon="gauge" href="https://app.visiqlabs.com/dashboard">
    Manage keys, rules, agents, and your audit trail. Most day-to-day answers
    live here — start with **Harness → Agents** and **Harness → Rules**.
  </Card>
</CardGroup>

If you're working with a VisIQ contact already (a solutions engineer or your
account team), reach out to them directly — they have your tenant's context.

***

## Before you reach out

A few details up front turn a back-and-forth into a single reply:

<Steps>
  <Step title="What you expected vs. what happened">
    The rule or behavior you expected, and what the agent actually did (a tool
    that should have been blocked ran, a document that should have passed was
    suppressed, and so on).
  </Step>

  <Step title="The decision, not just the symptom">
    Open **Harness → Runtime Enforcement** in the dashboard and find the decision
    in the stream. The rule code (e.g. `[VisIQ decision=deny code=D-WRITE-DENY]`) and the agent id
    tell us exactly which evaluation to look at.
  </Step>

  <Step title="Your setup">
    The SDK and version (`@visiq/harness` / `visiq`), the framework you're
    wrapping, and the agent's mode (`monitor` / `enforce` / `off`). Never paste a
    full API key — the first 16 characters (`vq_prod_f3a91c0e…`) are enough to
    identify it.
  </Step>
</Steps>

<Warning>
  **Never share a full API key, or any secret, in a support request.** VisIQ stores
  only a SHA-256 hash of each key and can identify one from its first 16 characters.
  If you believe a key is exposed,
  [rotate or self-revoke it](/automation/api-keys#revoke-your-own-key-self-revocation)
  first, then tell us.
</Warning>

***

## Common answers first

Many questions have a direct reference:

<CardGroup cols={2}>
  <Card title="A call was (or wasn't) blocked" icon="shield-check" href="/rules/action/introduction">
    How action governance evaluates tool calls, and what each outcome means.
  </Card>

  <Card title="A document was filtered" icon="shield-halved" href="/rules/retrieval/introduction">
    How retrieval governance evaluates documents, redaction, and trust tiers.
  </Card>

  <Card title="Key or auth errors" icon="lock" href="/authentication">
    Audiences, permissions, rotation, self-revoke, and the `4xx` error reference.
  </Card>

  <Card title="Terminology" icon="book-open" href="/glossary">
    The outcomes, operation facets, modes, and audit primitives in one place.
  </Card>
</CardGroup>