Why dec pages take a few minutes
Dec page retrieval is async — SALT requests it from MeasureOne, the carrier processes the request on their side, and the dec page lands on the Submission minutes (sometimes longer) later. Status states on the Submission tell you where in the flow the request is.
In short: Dec page retrieval is asynchronous. SALT submits the request to MeasureOne, MeasureOne contacts the carrier, the carrier responds. End-to-end is usually a few minutes but can be longer. Status updates on the Submission as the request progresses.
Why it’s slow
Declaration page retrieval involves multiple parties:
- The prospect provides consent and prior carrier info
- SALT submits the request to MeasureOne
- MeasureOne authenticates with the prior carrier on the prospect’s behalf
- The carrier responds with the dec page document
Each of these takes time. Carriers vary in responsiveness — some respond in seconds, some take minutes, some have intermittent issues. The end-to-end is dominated by the carrier’s response time, not anything SALT controls.
Realistic expectations: usually a few seconds to a few minutes. Occasionally longer.
Status states
The Submission shows a dec page status that reflects where the request is:
| State | What it means |
|---|---|
| Pending | Request received, not yet started |
| In progress | Actively in flight — SALT is talking to the carrier |
| Couldn’t retrieve | Carrier didn’t return a usable dec page |
| Skipped | Bypassed (consumer chose not to, or the integration was off) |
| Off | The dec page integration is disabled |
| Paused (monthly limit) | Per-vendor monthly cap reached |
| Paused (low balance) | Data Credit balance too low |
Watch for In progress to transition to either a successful dec page on the Submission or Couldn’t retrieve if the carrier didn’t deliver.
When the dec page comes back unavailable
A dec page can come back as unavailable for several reasons:
- The carrier doesn’t support MeasureOne’s retrieval flow
- The prospect’s authentication with the carrier failed (wrong credentials, expired account)
- The carrier returned no policy for the prospect (no active policy on file)
- A timeout or temporary issue on the carrier side
For unavailable cases:
- Ask the prospect to upload their dec page manually as a fallback
- Try Fize as an alternative provider where applicable
- Note the unavailability for follow-up if it’s a recurring carrier-specific issue
What you can do while waiting
Don’t worry about the dec page mid-call:
- Continue the rest of the intake — the dec page lands when ready
- The Submission updates automatically; you don’t need to refresh aggressively
- If the prospect has a copy of the dec page handy, manual upload is a faster fallback
- For rush situations, ask the prospect to forward the dec PDF directly via email
What if the dec page never arrives
If a request stays “In progress” for an unusually long time (hours):
- Check MeasureOne’s recent error log on the integration
- Verify the prior carrier’s authentication on the consumer’s side
- Consider a manual upload from the prospect
- Contact support if a pattern emerges across multiple Submissions
Common questions
Can I cancel a pending dec page request? Once submitted, the request runs to completion (success or failure). You can’t cancel mid-flight. Skip the integration for future Submissions if you don’t want to make more requests.
Will I be charged for a request that came back unavailable? Pull billing depends on the vendor’s terms. MeasureOne’s typical model charges only for successful pulls; check your Data Credit usage for actual debits.
Can I retry a failed dec page request? Where supported, yes — manually re-trigger from the Submission. This consumes credits again.
Can the prospect see the dec page progress? Where supported, yes — the consumer-facing flow shows progress and final status. Otherwise, the dec page is delivered to your agency’s view of the Submission only.