Custom Questions overview
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.
In short: Custom Questions let your agency capture data the standard library doesn’t include — anything from “preferred carrier” to “garage door has automatic opener.” Build, publish, attach to Forms, and they show up alongside standard questions.
Why Custom Questions exist
SALT’s standard question library is insurance-shaped — designed to feed comparative raters and integrations cleanly. It can’t anticipate everything your agency wants to capture:
- A carrier-specific underwriting question
- A referral source for marketing attribution
- An internal flag agents use to triage leads
- A consent or disclosure unique to your jurisdiction
- Anything else your standard intake doesn’t cover
Custom Questions close that gap. You author them, you control them, they integrate with the rest of your Form workflow.
What you can do with one
A Custom Question:
- Has a question prompt and one or more inputs (text, select, multi-select, numeric, file, etc.)
- Has a scope — does it apply once per Submission, or once per driver, vehicle, property, etc.
- Has visibility logic (modifiers) that hide it based on other answers
- Can be marked as sensitive, requiring export consent
- Goes through a publishing workflow before it appears on a Form
- Counts toward your plan’s Custom Question limit when published
Plan-tier limits
The number of published Custom Questions you can have at once depends on your plan:
| Plan | Published Custom Question limit |
|---|---|
| Propel | 10 |
| Propel+ | 20 |
| Middle Market | 40 |
| Custom | Negotiated |
Hitting the limit blocks new publishing. Archive an unused Custom Question to free a slot, or upgrade.
How they fit alongside standard questions
A Form uses standard questions and Custom Questions together. The order you place them in the Form’s steps is up to you. Consumers see no distinction — both render the same way.
Behind the scenes:
- Standard questions feed integrations and raters cleanly.
- Custom Questions feed exports and (where supported) integrations like Zapier or Webhooks.
If a Custom Question’s data should sync to a particular vendor, check whether the vendor supports custom field mapping in its integration guide.
When NOT to use a Custom Question
- The standard library covers it. Use the standard question — it’s better validated and feeds integrations cleanly.
- You’re capturing PII outside the Insured fields. Don’t. Insureds, drivers, vehicles, properties already have appropriate PII fields with encryption and consent handling.
- It’s truly internal context. Use a Note instead — Custom Questions are for consumer-facing data capture.
Common questions
Are Custom Questions shared across forms? Yes — they’re account-wide. Each agency builds and manages its own.
Can a Custom Question be on multiple Forms? Yes. Build once, attach to as many Forms as you want.
Can I version a Custom Question? There’s no built-in versioning. Edits to a published Custom Question affect only future answers — past data stays as captured. See why old data doesn’t update when you edit a Custom Question.
Do Custom Questions appear in Live Intake? Yes — published Custom Questions are available to add to Live Intake templates.