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

# Feedback and requests

> Report a bug, request a feature or flag something wrong in this documentation, and what happens next.

Everything goes to the same place: [**support@exoid.io**](mailto:support@exoid.io). What changes is what you put in the message, because that is what decides how fast someone can act on it.

## Report a problem

Something behaves differently from what this documentation says, or from what you expected.

<Steps>
  <Step title="Say what you were doing">
    The study, the section of the platform, and the step you were on when it happened. A link to the campaign is the fastest way to give all three.
  </Step>

  <Step title="Say what you expected and what happened instead">
    Two sentences are enough. "I expected the respondent to be sent to the ending screen, they were sent to the next question" tells us more than "the logic is broken".
  </Step>

  <Step title="Say whether it is blocking">
    A study that is live and collecting responses is treated differently from one still in draft. Tell us if it is.
  </Step>
</Steps>

<Tip>
  A screenshot of the settings panel or of the canvas usually saves an entire round of back-and-forth.
</Tip>

## Request a feature

The most useful requests describe the research problem, not the solution.

"I need to run a monadic test and assign respondents to cells automatically" gets acted on. "Add a randomizer block" is a guess at how to solve it, and it may not be the right one.

Include, if you can:

* the kind of study you are running, and how often you run it
* what you do today to work around the gap
* what it costs you — in time, in budget, or in studies you simply do not run

Before you write, it is worth checking what is already in development: [Research Desk](/en/soon/research-desk) and [video interviews](/en/soon/video-interviews) come up often.

## Fix this documentation

If a page is wrong, out of date or unclear, that is a bug too, and it is the one we most want to hear about.

At the bottom of every page there is a thumbs up and a thumbs down. Use it: it costs you nothing and it tells us which pages are not doing their job. When you have something specific — a step that no longer matches the interface, a name that changed, an example that does not work — send the page URL and the line to [support@exoid.io](mailto:support@exoid.io).

<Note>
  Documentation fixes are usually the fastest thing we ship. If a page is misleading you, it is probably misleading someone else too.
</Note>

## Talk to someone

Some things are faster said than written: designing a study, choosing between two methodologies, working out whether Exoid fits a specific research problem. Pick a slot and we'll go through it together.

<Frame>
  <iframe src="https://calendly.com/federico-grilli/exoid-meeting?hide_gdpr_banner=1&background_color=0b0d1a&text_color=e6e8f0&primary_color=4252ff" width="100%" height="720" frameBorder="0" title="Book a call with the Exoid team" />
</Frame>

If none of the slots work, write to [support@exoid.io](mailto:support@exoid.io) or [book a demo](https://exoid.ai/book-a-demo) from the website.

## Next steps

<CardGroup cols={3}>
  <Card title="Troubleshooting" icon="circle-help" href="/en/troubleshooting">
    Check first: most problems have a known cause and a fix.
  </Card>

  <Card title="What's new" icon="sparkles" href="/en/whats-new">
    Every product update, newest first.
  </Card>

  <Card title="Recipes by research type" icon="book-open" href="/en/recipes">
    Twenty-five studies you can build, before asking for a new feature.
  </Card>
</CardGroup>


## Related topics

- [Exoid documentation](/en/index.md)
- [Configuration](/en/webhooks/configuration.md)
- [How they work](/en/webhooks/introduction.md)