Give website visitors a direct way to ask about your club, organisation or athlete. Keep submitted messages in the private website enquiry workflow rather than publishing them as community posts.
Explain what the enquiry route is for and publish the relevant practical information nearby. A newcomer asking about training needs a different expectation from someone reporting an urgent issue. Do not present a general website form as an emergency or medical contact channel.
Supported submissions are available to authorised website administrators, with statuses to help organise follow-up. Notifications avoid including the visitor's identity and message. Review who has access before delegating enquiry handling to volunteers.
Website enquiries are retained for 90 days under the implemented workflow. Handle any necessary follow-up through the appropriate process within that period. Avoid asking visitors to send sensitive documents or private athlete information through an ordinary introductory enquiry.
Fictional demonstration
A fictional club directs first-session questions to its contact form. A website administrator checks the private inbox and updates the enquiry status while arranging a response.
Sign in and select an eligible identity you own. Choose the design at creation, add accurate content and eligible sources, then check the phone and desktop previews. Complete the first publication review and use the actual published address. Review the editor’s current publication state when updating an existing live site.
Check how this fits your club, website or event before getting started.
No. Website enquiries are private management content, not public posts or testimonials.
No. It records an enquiry. Membership, competition entry and group participation use separate workflows.
Use the existing setup workflow to choose your identity, review eligibility and prepare the information you want to publish.
