Once a client's business app is switched on, every new submission from a Contact Form on that client's Mount Olympus sites also goes to the business app. Form Responses, the notification email, the auto-reply and the form's other integrations work exactly as before. Submissions from before the business app was switched on are not brought in.
What happens to a submission
- The contact is found by the email or phone (or made). Empty fields are filled; nothing already there is overwritten.
- A Form submitted entry goes in the contact's Activity history with every answer, the page it was sent from and any UTM tags.
- The form's tags are added and, for a contact with no owner yet, the owner is set.
- The business's owners and managers get a bell notification for a new lead (or the owner does, when the form assigns one), and the contact's followers hear about every new form from that person.
- The page, UTM tags and form become the contact's first touch (or latest touch, for someone you already have) under Where they came from. Custom fields with a default value are filled in for a new contact.
A submission with no email or phone waits under Unmatched form entries instead of making an empty contact.
Where each answer goes
Each form field is mapped once:
- Email, Phone, First name, Last name, Full name and Company go on the contact itself;
- an Opt-in tick becomes the contact's email permission, with the form's name and page as the record of how they agreed;
- the message or comments box goes in Additional information when that's empty. Later messages don't overwrite it, and every message is always in the Activity history;
- free-text notices aren't saved;
- anything else becomes a custom field.
Custom fields made for you
When a form has a field the business doesn't have yet ("Number of passengers", "Event date"), the business app makes it as a custom field for that client's business only:
- its type comes from the form field: email, phone, date, number, dropdown or radio buttons (with the same choices), checkboxes, file upload, single or multiple lines;
- it's named after the field's label and put in the From website forms folder;
- an existing field with the same name is used instead, and an archived one is reactivated. It never makes duplicates.
The fields are made when the site is published, so they're there before anyone submits, and when you open the form's Business app settings. A form changed some other way (Zeus or an AI app over MCP) is mapped on its first submission. The business's owners and managers get a bell notification, for example "3 new custom fields were created from your Contact form".
The mapping is remembered for each form field, so renaming a label later doesn't make a second field.
The form's Business app settings
In the editor, open the form's settings → Integrations → Business app (it shows when the site's client has a business app):
- Field mapping: change where any form field goes, including to a different custom field;
- Tags added to every contact from this form;
- Assign to: nobody, one team member, or round robin between several (each new contact goes to the next person in turn);
- Create an opportunity: tick Make an opportunity for each submission, choose the pipeline, the stage (the first stage unless you pick another) and, optionally, a value. A contact who already has an open opportunity in that pipeline doesn't get a second one, unless you tick Make a new opportunity every time.