Contact
Reach the right desk first time.
Four addresses, each with a clear remit. Choosing correctly is the fastest thing you can do — a technical question in the billing queue waits behind invoices, and a security report in a public forum is a disclosure.
- Written replies
- Business days, Monday to Friday
- Security handled privately
Where to write
-
Product support
An agent, an Ability, a decision, or an outcome that needs explaining. One ticket queue for everyone, free edition included — a paid licence changes how fast the first reply comes, not whether you get one.
Open a support ticket -
Sales and licensing
Plan selection, licence scope, seat counts, agency arrangements, invoicing questions before purchase.
[email protected] -
Billing
Invoices, renewals, cancellations, and refunds under the published refund policy.
[email protected] -
Press and partnerships
Interviews, briefings, integration proposals, and anything involving the brand.
[email protected]
Do not use any address on this page. Follow the responsible disclosure process, which explains what to send and what to expect.
Make it easy to answer
We answer in writing, and a good first reply depends almost entirely on the first message. Two habits help more than anything else.
Say what you were trying to do
Describe the operating goal, not only the error. “A content agent should be able to draft but never publish, and I cannot express that” is answerable. “Permissions are not working” is not.
Bring the request context
For anything technical, include the environment, the agent, the Ability, the decision, and the request identifier. The support page has a template you can copy.
We will never ask for an Application Password, a WordPress administrator login, or an unredacted request input. Anyone who does is not us.
Send a message
For sales, billing or press. If your question is about the product itself — an agent, an Ability, a decision that needs explaining — open a support ticket instead, so the conversation has a history and a status you can follow.
What does not belong here
- Requests to bypass the boundary. We do not provide a route around native WordPress authorization or the governed request lifecycle, in any plan.
- Custom development. We do not take bespoke build work on client sites.
- Unsolicited marketing. These addresses are for people using or evaluating the product.
- Working exploits. Even in a private email, follow the disclosure process instead.
How we handle your message
We use what you send to answer you, and we keep the correspondence only as long as it is useful for support history and legal obligations. We do not sell it, and we do not add you to a marketing list because you asked a support question.
Details of what we collect, why, and how long we keep it are set out in the privacy policy.
Before you write
The answer may already be documented.
Troubleshooting starts from the symptom you can see and works back to the gate that stopped the request.