Tell us what is not working

Messages are read by a person and answered by a person, normally within one working day. If your message is about something that has stopped working on a system we look after, say so in the subject line, because it is routed differently and treated as more urgent.

The form is the best route, because it arrives with the context attached. If you prefer email, the department addresses are listed on this page: general questions, sales enquiries for new work, HR for careers, and a separate address for reporting an issue with something we built.

What you are trying to do, what happens now, and what you expected instead. If something is broken, say what you did and what you saw. That is usually enough for us to tell you whether it is something we can help with, and it saves a round of questions.

Not usually, because a price without a defined scope is a number that means nothing. What the first reply normally contains is a short read on the situation and the questions we still need answered. Where the scope is already clear enough, we will put an indicative range in it and say what it assumes.

We say so rather than guess. If a request is outside what we are set up to do well, we will usually be able to point you towards someone who does it properly. The services overview is the honest list of what we handle.

Your message is used to answer you and for nothing else. It is not added to a mailing list, and it is not passed to anyone outside the company. The detail is in the privacy policy, and the cookies this page sets are listed in the cookie policy.

For clients on a support arrangement, yes, and the arrangement states what is covered. For general enquiries, the honest answer is that we answer in working hours and would rather tell you that than have you discover it at the weekend.

Please report it through this form and choose the issue option. Naming the page and, if you can, the browser you are using gets it fixed faster than a description of where you clicked.