How this website handles enquiries
There are two ways to send an enquiry. Both let you prepare the text, but only one submits it to the server. Here is what happens after each choice and what the form’s confirmation means.
Choose a route
Through the website
- The form prepares a draft on the page. “Prepare enquiry” checks required fields and shows the full text. You can edit or copy it. Nothing has been sent at this point.
- When you choose email submission, the browser sends the filled fields to the server over HTTPS. The server stores the enquiry and queues its deliveries. A reference and “accepted” status mean the server accepted the record; they do not prove the email arrived or was read.
- Two independent jobs try to deliver the full enquiry by email and a Telegram notification. That notification contains only the enquiry ID and a link to the owner cabinet. Delivery states are tracked separately; a failed channel can be retried from the cabinet.
Your reply preference is separate
The form lets you choose where you would prefer my reply. That does not change how the enquiry is submitted: you can use the website form and ask for a Telegram reply, or open a Telegram draft and leave email as your reply preference.
Storage and access
The website sends enquiries over HTTPS. The owner cabinet requires a password and a one-time code. Telegram notifications contain no name, contact details or enquiry text. The 30-day period applies to the cabinet record and can be extended. Email and message copies already sent are stored separately and are outside that period.
The cabinet separates my work status from the email and Telegram delivery states. The work status tracks how I handle the enquiry; delivery states show the result for each channel. Neither confirms that I have read it.
What to define for similar automation
It helps to agree where requests come from, which fields are needed, who handles them and where notifications should go. We can also define working statuses, failure handling, retention and any external connections. A CRM, calendar or more team members can be added by agreement; they are not connected to this form now.
For an initial discussion, describe the task, the outcome you want, any timing constraints and links to relevant materials. Passwords, access codes and secret keys are not needed.