01 Support
Something is broken
A bug, an error you cannot get past, or a feature that is not behaving the way the docs say it should.
Include the URL you were on, what you expected, what happened, and the name of the workspace.
Contact
Talk to us.
Real people, and usually the ones who wrote the code you are asking about. Pick the route that matches what you need — each one opens your mail client with the subject already filled in.
No phone line or live chat is published. Email is the route that reaches us.
02 Sales & enterprise
You need a plan that fits
Seat counts, a custom plan, procurement, invoicing, or a security questionnaire you have to get through.
Include team size, the workspace you already have if any, and the deadline you are working to.
03 Security
You found a vulnerability
Responsible disclosure. We reply to every report, and we will not pursue good-faith research that avoids privacy violations, data destruction and service degradation.
Include steps to reproduce and the affected URL or endpoint — please do not include other people’s data.
04 Press & everything else
Anything that is none of the above
Press, partnerships, a question about the roadmap, or telling us the site is wrong about something. There is no separate press address — this reaches the same people.
Include what you are working on and what you need from us.
Faster, if you are already in
Use the widget in the app
Reporting from inside Planner.day is the quickest route: it creates a task on our board,
gives your report a short reference in the form PD-XXXXXXXX that appears in
the subject of every email about it, and emails you automatically when the work ships —
including if your report gets merged into someone else’s.
Before you write
It might already be answered
Some of what people write in about is already written down, in the same plain tone as an email back. The security page in particular is meant to be forwarded on to whoever is asking you the hard question.