What to put in the email
Your dates, your pillow city, whether anyone needs a licensed driver, dietary notes as context (not as a booking), and the job — walk, market, vines, chef. If you arrived from an old /food-tours-articles/ bookmark, paste the URL; we can tell you where it now lives.
We cannot confirm a roster, hold a van, or reconstruct a 2010 headline as a reservation. We can tell you whether the Hunter wants an overnight or whether how to choose is the page you actually need.
Operators should use Advertise rather than a vague pitch. Privacy notes live on privacy.
Response habits
This is a small desk. If you write on a Friday before a long weekend, expect the reply after the hall reopens. Urgent allergen questions belong with the operator, not with an editorial inbox.
Please do not send attachments we did not ask for. A link and a paragraph will do. The about page explains the ethic behind that brevity.
If you need a public-facing planner rather than a reply, start at the [homepage](/) or the FAQ.
Please include a time zone if your dates are close. A Saturday in Sydney is not a Saturday in Perth. We will not invent a tour for a gap that does not exist. We will tell you if the Hunter wants a night you do not have.
If you are writing from an operator inbox, say so in the first line and use Advertise as the template. Mixed pitches that pretend to be traveller questions waste everyone’s citrus time. We would rather have a blunt listing note than a soft sell dressed as a reader.
Where we will send you next
Most mail is a city question dressed as a booking question. You will likely be sent to Melbourne, Sydney, Adelaide or a region page. That is not a brush-off. That is the product.
Trademark and copyright questions about third-party brands should go to those owners. Our footer disclaimer is the public sentence.
