Sign in to SALT

Which questions are sent to which integration

Each integration has its own field map. Standard SALT questions generally flow to integrations cleanly. Custom Questions need explicit mapping to land in vendor systems. Some standard fields (like Occupation) aren't part of every vendor's rating flow.

Updated Apr 29, 2026 • For agency admin

In short: Standard SALT questions usually map to integrations automatically. Custom Questions need explicit mapping. Some standard fields (Occupation, for instance) aren’t accepted by every comparative rater.

How field mapping works

Each integration has a defined map between SALT fields and the vendor’s fields:

  • Standard SALT questions (Insured name, address, vehicle make/model, property characteristics) generally map cleanly to vendor fields.
  • Custom Questions are agency-specific; they don’t map automatically. You need a vendor-specific mechanism (custom property mapping, custom field setup, etc.) to land Custom Question data in the vendor.
  • Some standard fields are captured by SALT but aren’t accepted by the vendor’s rating flow. Occupation is the classic example — SALT captures it on some Forms, but several comparative raters don’t include occupation in their standard rating request.

What you can expect by integration type

Comparative raters (EZLynx, PL Rating, Epic Quotes, QuoteRUSH)

Standard SALT fields map cleanly. For the exact, current list of every field SALT sends to each rater — and the values that rater accepts — see the live field reference for that rater:

Things that don’t always map:

  • Custom Questions (need vendor-specific mapping; see below)
  • Some standard “soft” fields like Occupation (depending on vendor)
  • Free-form notes
  • Fields specific to other lines of business (commercial fields when sending personal lines)

CRM/AMS (AgencyZoom, HawkSoft)

Map cleanly:

  • Contact properties (name, email, phone, address)
  • Submission metadata (which Form, which Link, when created)
  • Standard insurance entities (Insureds, vehicles, properties — usually as related records)

Don’t always map:

  • Custom Questions (need explicit vendor-side custom property mapping)
  • Documents (sometimes attach, sometimes don’t)
  • SALT-internal fields like Tags or Saved View context

Data providers (Estated, Fenris, MeasureOne, Fize)

Map only what’s needed for the lookup:

  • Estated: address fields for property data
  • Fenris: address and risk-relevant fields
  • MeasureOne: prior carrier, policy info, consumer auth
  • Fize: same general area as MeasureOne

These integrations don’t push your Submission data wholesale — they take what they need to perform a lookup and return enrichment data.

Automation (Zapier, Webhooks)

Map everything that’s exposed:

  • Standard fields
  • Custom Questions (where exposed; sensitive ones may be gated)
  • Submission metadata
  • Tags, Status, assignee

Best general-purpose integration for capturing the full picture of a Submission.

Why “Occupation” might not be sent to your rater

Occupation is captured by SALT on some Forms because it’s useful for:

  • CRM lead qualification
  • Reporting and segmentation
  • Custom workflow routing

But several comparative raters don’t include occupation in their standard rating request. The field stays in SALT — visible on the Submission, exportable, available to non-rater integrations — but doesn’t push to the rater.

If your rater specifically supports occupation in its rating model and you need it sent, contact support to discuss extending the field map.

Extending field mapping for Custom Questions

For Custom Question data to reach a vendor system:

  1. Vendor-side custom property — create a corresponding field in the vendor (e.g. an AgencyZoom custom field).
  2. SALT-side mapping — wire SALT’s Custom Question to the vendor’s custom property in the integration settings (where supported).
  3. Test — submit a sample and verify the data lands.

Some integrations support this; some don’t. Check the per-vendor guide for capability.

Common questions

How do I see the actual map for a specific integration? Each per-vendor guide covers what’s mapped. Some integrations expose the map in their settings UI; for vendor-internal mapping, you’ll need to refer to the vendor’s documentation.

A field I expected didn’t make it. Where do I look? Three places: (1) the Submission itself — confirm the field has a value; (2) the vendor’s record — check whether their UI shows the field; (3) the integration’s recent error log — validation rejections sometimes drop a field silently.

Can I send different fields for different Forms? Per-Form mapping isn’t a built-in option for most integrations — the map is account-level. To get effectively different mapping per Form, use different integrations for different Forms (e.g. a Webhooks endpoint with custom logic per Form).

Does sensitive Custom Question data flow to integrations? Custom Questions marked for export consent are gated. They’ll flow to integrations after consent is accepted; before that, they’re held back. See Custom Question security.