Contact
Send a note to the studio.
Use this form for a general question, a care question, or a message about an existing request. For new work, the service request form gathers more useful starting information.
A real message queue
Your message is stored for staff review.
The previous site displayed a success message without sending or saving anything. This form now writes a real record to the protected staff dashboard. That means the confirmation you see reflects an actual stored submission, not a simulated interaction.
No public street address, phone number, or business hours are shown because verified values have not been supplied for publication. The website also avoids sending you to a fabricated map. When the owner approves those business facts, they can be added consistently to the contact page, footer, structured data, and policy text.
Please do not submit passwords, payment card details, access codes, medical information, or other sensitive material. The form is intended for ordinary service and studio correspondence.
What to include
Context helps the team respond clearly.
Use a specific subject line and explain whether your message concerns a new question or a request you already sent. If it concerns an existing request, include the same name and email address used in that submission. Avoid sending the same message repeatedly; duplicate records make it harder to follow one conversation.
For plant care questions, describe what changed and when. For flowers or events, include the relevant date range. For account questions, never include a password or verification code.
New project?
Use the service form when the work needs structure.
The service request form includes a service category and preferred date field. That information makes it easier for staff to triage requests and keeps project details separate from general correspondence. A request remains pending until someone reviews and confirms it.
Open the service request form
Privacy by default
Public forms should collect only what they need.
The message record contains the fields shown here, a workflow status, timestamps, and a one-way hash used for basic abuse control. The public page does not expose the stored record after submission. Staff access requires a server-validated account, and no form data is placed in browser local storage.
For more information about handling website submissions, review the privacy policy. The policy explains the system’s current scope without claiming a retention schedule or legal review that has not been supplied.
Read the privacy policy