Your source for Plansight help, training, and best practices.
Automated Carrier Follow-Up for RFPs
Chasing carriers for quotes — remembering who owes what, writing the same nudge email, checking back before the deadline — is work that Plansight now handles for you. Build a follow-up sequence once, and your RFPs remind their own carriers

Chasing carriers for quotes — remembering who owes what, writing the same nudge email, checking back before the deadline — is work that Plansight now handles for you. Build a follow-up sequence once, and your RFPs remind their own carriers automatically, ask only about what's still open, and stop the moment a carrier responds.



Why Use a Follow-Up Sequence

Write your reminder emails once. The sequence carries to every RFP you send — no rewriting the same follow-up from scratch each time.

Every reminder stays on point. Plansight tracks each benefit line separately, so a carrier who quoted Medical but hasn't answered on Vision gets asked about Vision only. Carriers are never nudged about work they already finished.

The sequence cleans up after itself. The moment a carrier settles every open line, they drop out automatically. Nobody has to remember to turn anything off.

Setting Up Your Sequence

Build the sequence

Write your reminder emails once in the sequence builder. Use merge fields — Carrier First Name, Employer Name, Open Benefit Types, and RFP Due Date — so every reminder reads as you wrote it for that carrier specifically.

Every reminder automatically includes the same Available Actions block your original RFP invite uses: Download RFP, Upload Quote, and Decline to Quote. Carriers can respond in one click, straight from the email.

Attach it to an RFP

On the Review & Send step, look under Proposal Due Date. You'll see your sequence and whether its cadence fits this RFP's window. From there you can:

  • Toggle the sequence on or off for this specific RFP
  • Nudge individual reminder dates
  • Compress the cadence to fit a tighter deadline

Then send as usual. Plansight handles the reminders from that point forward.

Rules to Know

  • A line is settled by a Quote or a Decline to Quote. Declining counts as a response — a carrier who declines stops receiving reminders for that line.
  • The RFP due date is a hard stop. No reminder sends on or after it. Steps scheduled past the deadline are skipped, not pushed later.
  • Silence escalates to a person. Any line still open at the deadline lands in the Needs Outreach queue — one row per carrier per RFP, listing the open benefit types, assigned by role: RFP Owner, Account Manager, or Producer. The queue clears itself if the carrier responds, or you can mark it done after you've made the call.

Set your sequence up once, and every RFP after that follows up on itself. The only carriers who reach your to-do list are the ones who genuinely need a phone call.



Common Questions


  • Does a carrier who declines still receive reminders? No — a decline counts as a settled response. The carrier drops out of the sequence for that benefit line immediately.
  • What if a carrier quotes one benefit line but not another? Plansight tracks each line independently. The carrier continues receiving reminders only for the lines still open.
  • Can I adjust the reminder schedule for a specific RFP without changing my default sequence? Yes — on the Review & Send step you can nudge individual reminder dates or compress the cadence for that RFP only. Your saved sequence stays unchanged.
  • What happens to reminders scheduled after the RFP due date? They are skipped entirely. The due date is a hard stop — no reminder ever sends on or after it.
  • Where do I see carriers who never responded by the deadline? They appear in the Needs Outreach queue, one row per carrier per RFP, with the open benefit types listed and a role assignment so the right person knows to make the call.
  • Do I have to set up a sequence for every RFP? No — you build the sequence once and it applies to the RFPs you send. You can toggle it on or off per RFP at the Review & Send step.

scout#listPublishFollowUpTemplates

scout#rfpBuilderReviewAndSend

scout#publishFollowUpTasks