Hi, I have a form on my website where customers will fill out booking details , name and address etc. The form works fine and I receive an email on Submit. The default output is that each field appears in the order it is filled out and is in it’s own paragraph on the email. Is there a way to format the output in any other way? for instance without the line breaks or in a different order so it all takes up less space and is easier to read. Any help much appreciated
Hey Jerry👋
You’re right — that layout happens in the email itself, where each field shows in its own paragraph. You can tidy up the message text a bit in the form settings (for example: New message from {name} ({email}) | {message}), but the system still adds the full list below.
If you want full control, tools like Mailparser or Make can reformat the email nicely before it reaches your inbox. Hopefully we’ll get more flexibility natively soon!
Certainly! These tools can typically process form submission emails automatically. By forwarding your form emails to a service like Mailparser or Make, you can have the content parsed into structured fields (for example, name, email, message) and then reformatted or sent elsewhere — such as a custom email layout, spreadsheet, or CRM.
I haven’t tested this setup myself yet, but it’s a common approach used to clean up or automate notification emails without additional coding.
Hi, thanks for engaging. It’s a shame that message formatting is not included in Sitejet, it would make the output more professional and flexible. I have in the past used a 3rd party program, in my case Forms To Go, which worked very well with the old website builder I was using (Serif Webplus). However, it was a bit clumsy all told and relied on an embedded php script which does not seem to measure up to current hosting security protocols!
The contact forms we have natively build are a basic feature. If you like us to improve this to your needs, please head over to the feature request section and create a feature request. Please also check our guidelines for requests first
Happy to discuss this in our future product meeting.