Understanding the 'Assigned To' Field in Dazos Webform Snippets
Overview
When setting up a Dazos webform snippet, you may notice an Assigned To field included in the form code. This field is not intended to be filled out by website visitors — it is a backend configuration field used to automatically assign incoming leads to a specific CRM user or team.
Why the 'Assigned To' Field Appears
The Assigned To field is part of the webform snippet that Dazos generates to capture lead (Inquiry) submissions. It determines which CRM user or team will have visibility and ownership of any lead created through that webform.
Because this field is for internal tracking purposes only, it should never be visible to the end user on the front end of your website.
How It Should Be Configured
There are two recommended approaches for handling the Assigned To field in your webform snippet:
Set a static value in the snippet: Dazos Support can configure a specific user (e.g., Dazos Administrator, an Admissions Team user, or another CRM user) as a hardcoded static value directly in the snippet code. The field is then hidden on the front end of the webform so visitors never see it.
Leave it blank and assign after submission: The field can be left without a static value. In this case, a CRM representative can open the inquiry record in Dazos after it is received and manually assign it to the appropriate user based on factors such as region or team.
How to Hide the Field on Your Website
Once the static value has been set in the snippet (or if you choose to leave it blank), your web developer should hide the Assigned To field on the front end of the webform so it is not visible or editable by the person submitting the form. This is typically done by applying a CSS display: none style or using a hidden input field type in the HTML.
The field will still pass its value to Dazos in the background when the form is submitted — it simply will not be shown to the website visitor.
Updating the Assignment After Submission
If no static value is set, or if the assignment needs to change (for example, based on region or intake rep), a CRM representative can update the Assigned To field directly inside Dazos after the inquiry is received.
This allows your team to route and assign leads flexibly without requiring the webform to handle the logic upfront.
Tips & Notes
⚠️ Warning: If the Assigned To field is left visible on the front end of your webform, website visitors may see and attempt to interact with it. Always ensure this field is hidden from the public-facing form.
💡 Tip: If you want Dazos Support to set a static value for you, simply provide the name of the CRM user or team you'd like leads assigned to by default (e.g., Dazos Administrator). Support can update the snippet and resend it to you.
✅ Best Practice: Even when using a static default value such as Dazos Administrator, plan for your team to review and reassign incoming inquiries in Dazos as needed to ensure proper ownership and follow-up.