> For the complete documentation index, see [llms.txt](https://docs.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pakk.io/websites/content/forms/how-customer-forms-work.md). # How Customer Forms Work {% embed url="" %} Customers in Pakk are identified uniquely by their email address * If the email is already registered to a customer on the system, the Form Submission is tied to that customer record * If the email is new, a new customer record is created in ‘Lead’ status and the Form Submission is tied to this new lead > Reminder, a “Lead” is just a “Customer” that has never purchased from you. Leads are upgraded to Customer status automatically on first purchase. There are a number of different customer form “types” available that influence how the new customer record is created: * RETAILLEAD/WHOLESALELEAD: dictates whether the new customer record is marked as a wholesale/trade customer or not * REQUIREMANUAL: does not automatically give access to the website to the registering customer. This is only really relevant for “private” style sites that require login to view products/prices. You may want to wait to review submissions before giving access to the site - this option allows you to do that. > We plan to build on these form "types" to offer different post-submission workflows in the future. ### Basic Form Options > Whether or not “Agreement to Privacy Policy” is explicitly requested for Forms is an option that is set globally in Website configuration. Once you’ve customised the content that is displayed before the form, you need to customise the form inputs. Basic options are as follows: * Comments Optional: the main form `comments` field can be made optional if you don’t need to collect any miscellaneous information from the customer (more useful for transaction type forms, like a serial registration or credit application form) * Comments Placeholder: give the customer an idea of what they should write in the comments field (e.g., “Please tell us something about your business”) * Enable Subscribe: give the customer the option to globally opt-in to email communication * Subscribe Wording: tell the customer why they should opt-in to email communication > Note that both the `email` and `name` field will always been shown as these fields are needed to create a customer record. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.pakk.io/websites/content/forms/how-customer-forms-work.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.