Write to us. Postcard rules apply.
Short, direct, one address. Email us, start a discussion, or file an issue. Event Schedule is open source, so everything except the email happens in public.
Message
One address, and it is not a queue number. Nothing to log into, nothing to route, no reference to quote back at us.
Routing
Five addresses. Pick the nearest one.
Two of them answer you faster than we can, because the answer is already written.
| What you have | Where it goes | Why there |
|---|---|---|
| A how-to question | The user guide Searchable, and it covers schedules, events, tickets, newsletters, analytics and the API. Most how-to answers are already written down. | |
| A question about plans or fees | The FAQ What is on the free plan, what Pro adds at $5 a month, and why there are zero platform fees on ticket sales. | |
| Something is broken | GitHub Issues Issues are public, so you can see whether somebody has already hit it, add what you are seeing, and follow the fix. | |
| An idea, or a feature you want | GitHub Discussions Ideas are worth arguing out in the open, next to everyone else who wants a version of the same thing. | |
| Anything private, or anything else | [email protected] Your account, billing, or something you would rather not post in public. If none of the others fit, this address takes it. |
GitHub is the public half of this. The email address is the private half, and it is the right one for anything to do with your account.
Before you send
The back of a card is not very big.
Four lines turn a report into something we can reproduce. Everything else is optional.
- Your schedule address, which on the hosted site looks like your-name.eventschedule.com.
- Hosted or selfhosted. If you selfhost, the version you are running, which is shown in the admin portal.
- What you expected, and what happened instead. A screenshot beats a paragraph.
- A link to the event or the page it happened on.
Selfhosted and hosted are genuinely different code paths in places, so which one you are on is usually the first thing worth knowing.
And what you do not need
No ticket number. No call.
- There is no support portal and no case reference, so there is nothing to look up before you write.
- No demo call stands between you and a working calendar. Pricing is published and sign-up is self-serve.
- You do not need an account to write to us, or to read every issue and discussion in the repo.
Open source
The code is already public.
Which means so is the mail about it. Every issue, every discussion, every commit that closes one.
Discussions
Ask, or propose
Have a question or an idea? Start a conversation. It is the easiest way to reach both us and the people already using the thing you are asking about.
GitHub DiscussionsIssues
Report a bug
Found something broken? Open an issue and we will look into it. Because the tracker is public, you can watch the fix land instead of wondering.
GitHub IssuesSelfhost
Run it yourself
Prefer it on your own server? The installation guide walks through it, and selfhost questions are welcome on GitHub alongside everything else.
Installation guideReading the source is a legitimate way to get an answer. Open the repository
Helpful resources
You can also find answers here
The documentation and the FAQ already answer many common questions, and neither of them has to wait for us to read anything.
Documentation
The user guide, with a search box. Getting started, creating schedules and events, tickets, newsletters, analytics, the API, and a whole selfhost section.
Read the guideFAQ
The short answers, in one page: what the free plan includes, what Pro adds, why there are zero platform fees on ticket sales, and how selfhosting differs.
Read the FAQFollow us
Stay up to date with the latest news, features, and updates.
Six places to follow along, and not one of them is a support queue. For anything that needs an answer, the addresses above are better than a reply in a feed.
Frequently asked questions
About getting in touch, before you do.
How do I contact Event Schedule?
Email [email protected]. For anything technical you can also open an issue or start a discussion on GitHub, both of which are public. There is no support portal to log into and no ticket number to quote.
Where do I report a bug?
GitHub Issues. Reporting it there means other people can see it, add what they are seeing, and follow the fix. Include your schedule address, whether you are on the hosted site or selfhosted, and what you expected to happen instead.
How do I request a feature?
Start a GitHub Discussion. Feature requests are worth putting in the open, because somebody else usually wants a version of the same thing. Email works too if you would rather not post publicly.
Is there a phone number?
No. Contact is by email, or on GitHub for anything technical. Written requests are easier to answer accurately, especially when a link or a screenshot is what settles the question.
Do I have to talk to sales before I can sign up?
No. Pricing is published on the pricing page, the free plan needs no card, and you can create a schedule and start adding events without speaking to anybody. Ticketing is on the Pro plan at $5 a month, and Event Schedule charges zero platform fees on ticket sales.
I selfhost. Where do I get help?
The selfhost section of the user guide covers installation, email, Stripe, calendar sync, AI and the rest of the environment settings. For anything the guide does not answer, GitHub Issues is the right address, and it helps to say which version you are running.
Nothing to ask
Ready to get started?
Create your free schedule today. No credit card required.
Addressed to you
Or write first. The address is [email protected]