Forms module overview

With the Forms module, what the forms on your websites take in also reaches Demona: you see it under CRM → Form submissions, and each form can turn its submissions into an opportunity, a task or a newsletter sign-up. The forms work without the module too – the submissions then stay in the website admin only (Settings → Forms).

CRM → Form submissions lists what came in from every website of the team, newest first. Filter by website, by form, and with Unprocessed only by what nobody has dealt with yet. Click a row to open the submission: the questions and answers, the attached files (downloadable), the consent text and time, and what it became.

What a submission becomes. It is chosen in the form block (in the website editor, the In Demona field):

• Keep it only – the submission shows in the list and nothing else happens.
• Opportunity (with a customer) – the sender becomes a customer (or the existing customer is found by e-mail, then by phone), and a new opportunity opens in the default CRM stage with the answers.
• Task – a task in the project set under Settings.
• Newsletter sign-up – a subscriber, if the visitor agreed; an address that unsubscribed before is not signed up again.

When the target cannot be done (the CRM is off, or no project is set for tasks), the submission is kept and marked skipped with the reason. You can make up for it later with Create opportunity or Create task in the details.

Notifications and automation. Everyone with the module's manage permission is notified of each new submission (adjustable in the notification preferences). A Flow can start on the Website form submitted event, for example to assign someone or call a webhook.

AI summary. In the details one click asks for a short summary of what the sender wants and a possible next step.

Retention. The answers and attachments of a submission are deleted after 24 months; a customer, opportunity or task made from it stays.

Permissions. Anyone with access to the module sees the list; processing, converting, deleting and the settings need the module's manage permission. Admins and editors have both by default.