Company
Contact
Email, by subject, so it reaches somebody who can answer rather than a queue.
By subject
Where to write, and what to expect
Addresses by subject, so a message reaches somebody who can answer it instead of a queue somebody triages. A message at the wrong address is forwarded rather than returned, so choosing badly costs a day and nothing else. A working day means Monday to Friday excluding England and Wales bank holidays: Consonas is a United Kingdom company, so that is the calendar every target on this page is counted against.
| Subject | Address | Response |
|---|---|---|
| Anything at all, if in doubt | hello@consonas.com | Two working days |
| Help using the product | support@consonas.com | One working day on a paid plan |
| Data protection, subject access, the DPA | privacy@consonas.com | Within one month, usually far sooner |
| A security issue | security@consonas.com | One working day, acknowledged |
| Something inaccessible | access@consonas.com | Two working days |
| Contracts and terms | legal@consonas.com | Five working days |
What to expect
How this actually works
A person replies, every time
There is no ticket number, no automated first response and no chatbot. If the answer is that we cannot do what you have asked, you will get that answer with the reason rather than silence.
Which also means every target in that table is a promise we keep by hand. There is no system counting them, nothing measures whether we hit them, and we would rather say so than imply a service desk we do not run. If a reply is late, the honest recourse is to write again and say so.
There is also no second line to pass you to, and no manager who reads what the first person did not. Whoever replies is somebody who can change the product, which is the whole of the arrangement and also its limit: when they are wrong, there is nobody to appeal to except them. The about page treats that as both an advantage and a risk.
On the free plan
Support from a person with a target is not part of the free plan, and saying otherwise would set an expectation we could not meet. The help centre is open to everyone, on every plan, without signing in.
That said, if you are genuinely stuck on something that looks like a fault rather than a question, write anyway. A fault is our problem regardless of what you are paying, and we would rather know about it.
There is no sales call
No demonstration to request, no discovery call and no qualification. Create a free organisation and use it for a fortnight on real work. That will tell you considerably more than an hour with someone whose target you are.
If you genuinely want to talk to someone, write to hello@consonas.com and we will make time. It just is not a step you have to go through first. If what you want is somebody other than us to talk to, the customers page says where that stands.
Particular kinds of message
Five things worth writing differently
Reporting a security issue
Write to security@consonas.com. You will be acknowledged within one working day by a person, and you will be told what we found and what we did, including when the answer is that we had already fixed it or that we disagree it is a problem.
Testing our security is allowed if you ask first, and the answer is usually yes. What we will ask for in return is that you test against an organisation you created rather than someone else's, that you stop at the point of demonstrating the issue instead of extracting data, and that you give us a reasonable period before publishing. We will not threaten anybody who reports something in good faith, and we will credit you if you want to be credited.
There is no bug bounty, because we are too small to run one honestly and a programme that pays late or argues about severity is worse than none. That is a limitation rather than a position.
A data protection request about your own organisation
Write to privacy@consonas.com. Most of what you need is tooling rather than correspondence: subject access, consent records, export and deletion are all in the product on every plan, and the data processing agreement sets out what we owe you beyond that. Where you need something the tooling does not cover, ask, and we will not charge for assistance of that kind.
A request about data somebody else holds about you
If an organisation uses Consonas and holds a record about you, they are the controller and the request goes to them rather than to us. That is not us avoiding it; we genuinely cannot decide what happens to a record we hold on someone else's instruction.
If you do not know who they are, or you have written to them and had no reply, tell us anyway. We will help you find the right place to ask and we will tell them you are waiting. Write to privacy@consonas.com. If they still do not answer you, complaints of that kind go to the Information Commissioner's Office rather than to a supplier of theirs.
Something that does not work with assistive technology
Write to access@consonas.com and tell us what you were using, what you were trying to do, and where it stopped. That last part matters more than the diagnosis, because the place a journey breaks is often not where the defect is.
The accessibility page lists what is enforced by a test on every build and, more usefully, what has not been tested at all. It stops short of claiming conformance with the Web Content Accessibility Guidelines, which is the standard whoever asks you will have in mind. A report about something on the second list is genuinely the fastest way for that list to get shorter.
A questionnaire from your procurement team
Send it to legal@consonas.com and we will answer it honestly, including every question where the answer is no.
Before you spend the time, read the section of the security page listing what we do not have. We hold no SOC 2 and no ISO 27001, there is no published penetration test, and two protections that are built are not yet enabled in production. If any of those is a hard requirement, the questionnaire will not change it and we would both rather find out in five minutes than in five weeks.
A small company
What we cannot do
We cannot look at your records to answer a question. Not without you asking us to, for a specific reason, and when we do it is limited to the people who need it and it is recorded. That means some questions have to be answered by describing what to look at rather than by looking.
We cannot recover a deleted organisation after the retention period. Thirty days of point in time recovery, then thirty days for backups to age out, and after that it is gone in a way we cannot undo. This is a consequence of deletion being real rather than a flag on a row.
We cannot move your organisation between regions. The database exists in the region you chose, which is the European Union or the United States, and organisations in the United Kingdom should choose the European Union. The remedy is a second organisation and an import, which takes minutes.
We cannot promise a date for something on the roadmap. We can tell you whether it is being worked on, whether anybody else has asked, and whether it has been decided against permanently. A date from a company our size is a guess with a confident voice.
We cannot let you back in without evidence you belong there. If the only person who could sign in has left, write anyway, and expect the exchange to be slower and more sceptical than you would like. A way back in generous enough to help every genuine case is also generous enough to hand someone's organisation to a stranger with a plausible story, and between those two failures we have chosen the one that leaves you locked out instead of the one that leaves you robbed.
We cannot confirm anything about an organisation to an address we cannot place. Accountants and consultants write to us about organisations they do not belong to and that is ordinary: say whose it is and in what capacity you are writing, and one line from someone inside it settles the rest. Where the work will continue, adding your adviser with the narrowest role that does the job beats either of us relaying messages, and the roles and permissions article covers what the narrow ones can actually do.
We cannot be your data protection officer. You are the controller of the records you hold, and no supplier can take that on for you. What we can do is make the obligations cheap to meet, which is why the tooling is on the free plan.
Writing in
Asked about getting in touch
Is there a telephone number?
No, and it is worth explaining instead of leaving as an absence. A telephone reaches whoever picks up, which in a company this size is whoever is free instead of whoever knows. Written correspondence reaches the person who can actually answer, leaves a record both of us can refer to, and does not require either of us to be available at the same moment. For anything genuinely urgent, write to the address and say it is urgent.
What should I put in a support message?
What you were trying to do, what happened instead, and roughly when. The organisation name helps. Screenshots help. What is least useful is the name of the feature you think is broken, because that is a diagnosis rather than a description and it is occasionally the wrong one.
Can I ask for a feature?
Yes, and the ones that get built are the ones describing a problem instead of naming a feature. Tell us what is stopping you using Consonas, specifically, and it becomes something we can size. Several items moved from the bottom of the roadmap to the top exactly that way.
How quickly do you actually reply?
Usually faster than the targets in the table, because the targets are what we are prepared to commit to rather than what typically happens. If something has gone quiet for longer than the target, send it again. It is far more likely that something went wrong than that we decided not to answer.
Write to us
If in doubt, use the first address. It reaches a person who can either answer or pass it to whoever can.
Three people, a thousand relationships, no card and no time limit.