Contact form
Every venue site carries a Contact page in its public navigation, at /t/your-venue/contact. A visitor fills in their name, email, and message (phone optional) and presses Send message; Platypus emails the lot to the address you save as the Contact Form Inbox. Messages are delivered as email and nowhere else — Platypus keeps no copy.
What the visitor sees
The page has two halves. Beside the form, a Get in touch card lists whatever contact details you've chosen to publish: the Public Contact Email, Public Contact Phone, and Public Contact Address from the Contact tab of Settings, plus the Venue Address from the Venue tab. Each line appears only when it's set; leave them all blank and the card disappears, leaving the form on its own.
The form asks for a name, an email address, an optional phone number, and a message of up to 2,000 characters. On success the visitor sees a confirmation: Your message has been sent. We will be in touch soon. Sending a message adds nobody to anything — the mailing-list signup is the separate Subscribe page, covered in Mailing list & campaigns.
If you theme your public pages with custom CSS, this page exposes the hooks #page-contact, #contact-details, and #contact-form.
Where messages go
Submissions are delivered to the Contact Form Inbox, on the Contact tab of Settings in the admin sidebar. That address is never shown publicly, and it's deliberately separate from the Public Contact Email: the address printed on the page receives nothing from the form, so you can publish a general address while submissions go to the person who actually answers them.
Each submission arrives as one email with the subject New contact form message — your venue's name, carrying the sender's name, email, phone (when they gave one), and message. The sender's address is set as the Reply-To, so replying in your mail app goes straight back to the visitor.
Delivery uses your venue's mail provider — the same settings that send your tickets. On the default Platypus hosted mail it works with no setup.
Is there an inbox inside Platypus?
No. Despite the setting's name, the Contact Form Inbox is an email address, not a screen in the admin. There is no page of past messages: Platypus doesn't store submissions, so a message exists only as the email it becomes. That's worth taking seriously — if your mail provider is broken, a visitor's message is gone, not queued. The test send on the Mail tab is the cheap way to be sure that isn't happening.
When no inbox is set
You can't save the Contact tab with the inbox blank, but a venue that has never saved that tab has no inbox at all. The contact page still renders and still shows the form; a visitor who submits sees Contact is not currently available. Please try again later. and no email is sent. Set the inbox before you point anyone at the page — it's the one field on that tab that makes the form do something.
Spam
There's no CAPTCHA. Submissions are rate-limited to ten a minute per visitor, which blunts a crude flood, and whatever gets through is ordinary email you delete like any other. Nothing lands in Platypus, so there's nothing to clean up on this side.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Visitors report Contact is not currently available | No Contact Form Inbox saved | Set it on Settings → Contact |
| Messages stopped arriving | The mail provider broke, or the inbox address changed hands | Run a test send; check the inbox's spam folder |
| Messages turn up at the public contact email | They won't — that address gets nothing from the form | Watch the address saved as Contact Form Inbox |
| Replying to a notification emailed the visitor, not you | The notification's Reply-To is the sender | That's the point — replying answers the visitor directly |
| The Get in touch card is missing | All four contact detail fields are blank | Fill in whichever of them you want published |
If a clean test send arrives but form messages still don't, that shouldn't happen — email support@platypus.tickets.