Agent Oracle — Frequently Asked Questions

Most questions people send Agent Oracle are not about the software — they are about what the answers mean and how far to trust them. This page collects the recurring ones so the same explanation is written once, publicly, instead of being retyped in support replies where nobody else can read it.

Answers are kept in the page source rather than loaded on click, so the full text is available to search engines, screen readers and anyone who prefers to use the browser's find-in-page instead of the filters above.

When product behaviour changes, the affected answers are rewritten in the same release rather than being left to drift. Where an answer depends on a limit — turn allowances, retention windows, refund handling — the limit is stated plainly instead of being described as 'generous' or 'flexible'.

If a question here is answered in more depth elsewhere on the site, the answer links to it: billing and account matters point to the help centre, editorial and accuracy matters point to the trust page, and anything needing a human points to the contact routes.

Use the search box first — the index covers every published answer, not only the ones currently visible on the page. If nothing matches, the contact page lists which route reaches which desk and what response time to expect, and a correction request is always the fastest way to fix something that is wrong rather than merely missing.

A question earns a place here once it has been asked in three separate contexts — support, sessions, or reader mail — because a single asker usually needs a reply rather than a page. That threshold keeps the list short enough that scanning it is faster than searching it.

Answers are written to close the question rather than to tease the product. Where the honest answer is 'not yet' or 'no', that is what it says.

Every answer is rendered into the HTML rather than fetched when you click. That makes the whole page available to find-in-page, to screen readers, to translation tools and to search engines, none of which should have to run our filter code to read a sentence.

The filters and search box above are conveniences layered on top of content that already exists, which is also why the page works with scripting disabled.

Answers that quote a limit — turn allowances, retention periods, refund windows — are updated in the same release that changes the limit. An FAQ that contradicts the product is worse than no FAQ at all.

If an answer here disagrees with what the app does, that is a bug and worth reporting; the contact page routes it straight to the publisher.