Contact

One form, six topics, one queue. Whatever you send is written to the same tracked editorial queue that content reports go to, with a status and a reference — so a message about a wrong translation and a message about seats for forty learners are both things somebody has to close, not things that sit in an inbox.

What happens to your message

1. It is validated and written to the editorial queue as an open item, with your name and email address attached so we can reply.
2. You get a reference immediately. If nothing was stored, you are told that instead of being shown a confirmation.
3. It is triaged. A content error becomes a correction against the record and its version history; an enquiry gets a written answer.
4. It is closed with a resolution, which is stored on the item rather than in somebody’s memory.

DEV MOCK

In this environment the email provider is the local console mock, so no notification email is delivered. Your message is still written to the database — that part is real.

Faster than writing to us

Billing questions — plans, cancellation, refunds, VAT and how school seats are counted.
For schools — what a cohort, an assignment and a weakness report actually look like.
Privacy policy — data export and account deletion are self-service in Settings; you do not need to ask us.
Examination affiliation — we cannot answer questions about registering for, or the current rules of, an official examination. We are not the examination authority.

Privacy

Your name, email address and message are stored so we can answer and so the item can be tracked to a resolution. They are not added to a marketing list, and a resolved enquiry is deleted once it is no longer needed to evidence the correction it caused. Ask us to delete it sooner and we will.