Actual plugin views and usage guidance

Import fields: the first spreadsheet row is treated as column headers. The importer auto-detects common lead fields including first name, last name, email, phone, child or student name, child age, lead origin, notes, target state, trial date, and lead date. Review the mapping step before importing so each spreadsheet column targets the intended Lead Director field.

Target field usage: email or phone is required so Lead Director can deduplicate imported leads. If a target state column is detected and mapped, each row can move the created or updated lead to that pipeline state after import. If the target state is trial scheduled, a trial date column can supply the scheduled date and time; otherwise calendar availability or calendar authorization may be required.

Submitted fields: first name, last name, and email are required. Phone, use case, child name, child age, and tier can be included when the form asks for them. The selected public app is stored as the requested product or beta origin for the lead.

After submit: the form creates a new lead in the intake pipeline, records the landing-page request in the lead history, and can return a success redirect for the public page.