Custom Questions

Open Custom Questions, click new, write the prompt, pick a scope, configure inputs, and save. The question is a draft until you publish it. Once published, attach it to the Forms or Live Intake templates that should use it.

Custom Questions support text, select (single and multi), numeric, date, file upload, and others depending on configuration. Pick the input that gives you the right shape of data — a multi-select is not a free-text field.

Scope determines whether the question is asked once per Submission or repeated per record (driver, vehicle, property, Insured). Pick scope based on what the answer is about. Changing scope after publishing is risky — old answers may not align with the new shape.

Custom Questions are powerful but come with rules. Don't capture highly sensitive PII (SSN, full driver license numbers, payment cards) — SALT blocks Custom Questions that look like they collect prohibited data. Anything you do collect exports with the record and flows to integrations, so only collect what you have a business reason to.

A Custom Question is an agency-authored question that captures data SALT's standard question library doesn't cover. They have scopes (per-Submission, per-Driver, per-Vehicle, per-Property, per-Insured), a publishing workflow, plan-tier limits on how many you can publish, and security controls for sensitive data.

Publishing makes a Custom Question available to attach to Forms and Live Intake templates. Each plan has a cap on how many published Custom Questions you can have at once. Drafts and archived questions don't count against the limit.

Edits to a published Custom Question apply to new answers only. Past Submissions retain whatever inputs and labels they had when the answer was captured. For meaningful structural changes, build a new question instead of editing the old one.