Contact
One address. It is read by the person who built the product, and replies come from the same person.
Write to us
Questions, problems, feature requests, or to tell us we've got something wrong. There is no ticket number, no support tier, and no form with a dropdown of departments, because there are no departments. You will usually hear back the same day, always from a person, and always from somebody who can actually change the thing you wrote about.
If something is broken, the most useful message says what you did, what you expected, and what happened instead. A screenshot helps. But a two-line "this feels wrong" is welcome too; several of the product's better decisions started as exactly that.
Putting a company on it
Thinking about seats for a team? Write to the same address. Questions before buying, a pilot for one crew, how the contractor arrangement works, what happens when somebody leaves: all of it is answered personally, usually with a straight yes, no, or not yet. What we don't have is a sales team, a demo-call funnel, or an account manager, and if your procurement process needs a SOC 2 report, the security page will save us both the exchange: we don't have one yet, and it says so.
The case for running a company on this is on the business page, including the parts that argue against it.
Security reports
Found a vulnerability? Same address, and thank you. Say "security" in the subject line and it gets read first. The security page describes how the system is built and what we do and don't do, written to be checked against.