Agent Oracle is read by operators who are usually mid-decision when they write to us: a pricing change is already drafted, a hiring plan is already in a board deck, a churn number has already been questioned out loud. That context matters, so this page tells you exactly where a message lands, who reads it, and how long a useful answer normally takes.
Every message goes to a single reviewed inbox. There is no ticket-deflection bot in front of it and no outsourced first-tier queue writing back with links you already read. The publisher reads support mail personally, and editorial corrections are handled by the same person who approved the article in the first place.
Where your message goes
- Editorial corrections. A number, source, date or claim in an article looks wrong. Include the article URL and the specific sentence — that is enough for us to trace it to the source we used.
- Product and account support. Sign-in problems, turn balances, subscription changes, refunds, or a diagnosis session that behaved strangely. Include the email on the account, never a password.
- Press and partnerships. Interviews, commentary on operating trends, evaluation access for reviewers, or syndication of a specific piece. Write "Press" in the first line.
- Privacy and data requests. Export or deletion of your data. These are processed as formal requests and confirmed in writing, not resolved informally over chat.
What happens after you press send
Your message is stored against the brand you wrote from so replies come with the right context, and it is triaged the same working day it arrives. Support questions that only need an account change are usually resolved in one reply. Editorial questions take longer, because we re-open the source material before answering rather than defending the published version by reflex.
If a correction is warranted, we change the article, note what changed at the foot of the page and tell you what we did. If we disagree with a correction request we still answer, and we explain the evidence behind the original claim so you can judge it yourself.
How to get a faster, better answer
The single most useful thing you can include is a URL. The second is what you expected to happen versus what actually happened. For anything involving a chat session, the approximate time of day helps us find it; for anything involving billing, the last four digits and the date of the charge are enough — never send full card details by email or through this form.
- One issue per message keeps the reply focused and the fix traceable.
- Screenshots help far more than descriptions of screenshots.
- Tell us the browser and whether you were on the installed app or the web.
- If a deadline is attached to your question, say so in the first sentence.
What we will never ask you for
We will never ask for your password, a two-factor code, remote access to your machine, or payment details over email. No one from Agent Oracle will contact you first asking you to move a conversation to another messaging platform. If a message claiming to be from us does any of those things, forward it here and delete it.
Other ways to reach us
- Operator domain: myAgents.PLUS
- Support response time: typically within 2 business days
- Press & partnerships: use the form above and mention "Press" in the message
Reaching a person, and what to expect back
Pick the route that matches the problem
Editorial matters — a claim you think is wrong, a source you want cited, a figure that has gone stale — should go through the correction route so the message arrives attached to the page in question. General enquiries, partnership questions and press requests go through the contact form.
Account and billing issues need the account email and, for a charge dispute, the transaction reference. Without those, the first reply is a request for them, which costs everyone a day.
What happens to your message
Messages are read by the publisher, not by an autoresponder or a triage bot. Corrections that check out are applied to the page and acknowledged; corrections that do not are answered with the reasoning rather than ignored.
We do not add correspondents to a mailing list, and we do not use the contents of support messages as material for articles unless you explicitly offer them.
Privacy of what you send
The form collects only what is needed to reply. Messages are retained while the issue is open and for a short period afterwards so a follow-up has context, then deleted on the schedule set out in the privacy policy.
If you would rather not use the form, the data-request tab in your account handles access, export and erasure requests directly, and those are processed within the statutory window.
What we cannot do
We cannot give regulated advice — legal, tax, medical or investment. Where a question lands there, the answer will point you at the kind of professional you need rather than improvise.
We also cannot review your company's confidential documents over email. If a question requires numbers you would rather not send, the articles are written so you can run the calculation yourself without sharing anything.