Example dial check for a member in Florida at 8:12 PM: the number is valid, it is not a vendor router, the litigation scrub is not running until the provider key is connected, the number is on no DNC list and in no never dial group, and the call is held because Florida calling hours close at 8 PM. The held dial is noted on the member timeline.

for the day the letter comes

A call floor that keeps its receipts.

When a TCPA demand letter arrives, the question is what your floor wrote down. QuoteTurbo checks your DNC lists and the member's local calling hours before the phone rings, keeps what the vendor sent as consent, and writes down who opened what.

QuoteTurbo helps reduce risk and keep records. It does not make a call compliant and is not legal advice.

The register

Each control, and where the record lives.

18 controls, sorted by when they act in a call. Each one says what it does, where the evidence sits afterward, and whether it runs for every agency or waits on a setting.

  • DNC lists

    Before the dial

    Every agency

    Platform, agency and campaign lists. A DNC disposition adds the number and asks for a note. If the list cannot be read, the dial is held.

    On record: DNC entry with who added it; removals need a reason

  • Calling hours

    Before the dial

    Every agency

    8 AM to 9 PM in the member's local time, 8 PM in Florida and Louisiana, no Sundays in Florida. The zone comes from the state, then the ZIP, then the area code.

    On record: Dial blocked on the member timeline; refused callbacks are logged

  • Never dial groups

    Before the dial

    Agency setting

    Filter groups the agency marks never dial are skipped by every manual dial and campaign.

    On record: Held dial that names the group

  • Litigation scrub

    Before the dial

    Waits on provider key

    Looks each number up on a TCPA litigator list. A litigator goes on the agency DNC list and vendor posts for it are refused. Federal and state DNC hits are flagged, and blocked only if you choose.

    On record: Check log with what asked and what happened, CSV export

  • Consent from lead vendors

    Before the dial

    Every agency

    A vendor post can carry a consent certificate link, the consent text version, the page URL, the IP and the time. They are stored with the post. The certificate is not verified with its issuer.

    On record: Consent recorded by the vendor, on the member timeline

  • Licensed state routing

    On the call

    Agency setting

    Turn on Route by caller state for a vendor number and only Ready agents licensed in the caller's state ring. For final expense, term or IUL the agent also needs an active appointment there.

    On record: Routing log on the vendor page, one row per decision

  • Recordings and transcripts

    On the call

    Every agency

    Recorded calls play in the call details. Where a transcript exists, it shows the disclosure and TPMO checks at the moment they happened. Agents see their own calls.

    On record: Call log, Calls tab on the member

  • Listen, whisper and barge

    On the call

    Off until switched on

    Supervisors can listen in, coach the agent, or join the call. Barge asks first.

    On record: Every use logged with start and end time

  • TPMO disclaimer

    On the call

    Agency setting

    The CMS sentence prints from a merge field, with carrier and plan counts from your appointments, the CMS plan list by county, or numbers you type. An unknown county stops the send.

    On record: The sent document, with where each number came from

  • Required before Sold

    On the call

    Agency setting

    Make a field such as TPMO disclaimer read required before a policy can move to Sold. A checkbox counts only when it is ticked.

    On record: Stage history on the policy

  • E-sign audit trail

    After the call

    Every agency

    Sent, delivered, viewed, signed, declined, reminded and resent, each with who acted and when, IP and browser on expand. Upload your own Scope of Appointment form and it gets the same trail.

    On record: Audit trail and signed PDF on the policy

  • Text consent and STOP

    After the call

    Every agency

    Template and typed texts go only to members opted in. STOP, UNSUBSCRIBE, CANCEL, END or QUIT opts the member out; START opts back in. Verbal consent on the call is recorded by the agent.

    On record: Opt in and opt out times on the member

  • Messaging hours

    After the call

    Every agency

    Automatic texts and app pushes wait for the legal window in the member's time, narrowed by your agency's hours if you set them.

    On record: Held sends on the member's Scheduled tab, with why

  • Roles and permissions

    Who sees what

    Agency setting

    Owner, Back office and Agent, plus custom roles built from the permission catalog, such as all call logs, all transcripts, post sale fields, DNC lists and payroll.

    On record: Role changes are audited

  • Sensitive fields

    Who sees what

    Every agency

    Bank, card and marketplace SSN fields are stored encrypted with AES-256-GCM. A member SSN comes back only as a mask. CVV is deleted after 24 hours.

    On record: Encrypted at rest; masked on screen

  • Reveals and views

    Who sees what

    Every agency

    Revealing a masked field writes an access record before the value comes back, and reveals are rate limited. Member views are logged too.

    On record: Member Activity timeline

  • Sign in

    Who sees what

    Every agency

    Email code or Google, no passwords to reuse. An admin can limit a user to a list of IP addresses, and sessions can be revoked.

    On record: Login history for owners

  • AI question flags

    Who sees what

    Every agency

    The assistant only reads, inside the asker's own permissions. Questions that ask for bulk personal data or try to get around access are flagged for the owner. A flag never blocks; it marks the question for a person to review.

    On record: AI usage review for owners

Not checking yet

Litigation scrub

The scrub settings, the existing book scrub and the check log are in the product. Checks against the TCPA litigator list start once the list provider's API key is connected. Until then, no number is checked against it.

Once it runs, a litigator goes on your agency DNC list, vendor pings and posts for that number are refused, and an inbound call from one shows a warning without being blocked. You set how long an answer is reused and what happens if a lookup fails.

On the call

Missed statements show up on the transcript.

When a recorded call has a transcript, the call details mark whether the disclosure was heard and whether the TPMO statement came before any benefits. A miss shows where it happened, so a floor manager coaches from the line itself instead of a hunch.

The TPMO disclaimer prints from a merge field with your carrier and plan counts, taken from your appointments, the CMS plan list for the member's county, or numbers you type. An unknown county stops the send instead of printing a zero.

  • Required before SoldMake TPMO disclaimer read, or any field, required before a policy moves to Sold.
  • Scope of AppointmentUpload your own SOA form as an e-sign template. It keeps the same audit trail.
  • SupervisorsListen, whisper and barge stay off until you turn them on, and every use is logged.

Example transcript of a recorded Medicare call. The disclosure was heard at 3 seconds. Benefits came up at 24 seconds, before the TPMO statement, so the transcript shows an alert there and marks the TPMO statement missed.

Messaging hours

Texts wait for the member's morning.

Automatic texts and app pushes from workflows hold until the legal window opens in the member's own time zone. Set agency hours and they narrow the window further. The legal window always wins.

Example: an automatic text comes due on a Sunday at 7:30 AM Eastern. A member in Georgia gets it at 8:00 AM her time, a member in Texas at 8:00 AM his time, and a member in Florida on Monday at 8:00 AM, because Florida allows no Sunday sends.

Texts an agent types and sends by hand go when they press send, and email is not held. Template and typed texts reach only members who opted in.

Access

Who looked, and when, is written down.

Every member has an Activity timeline: who viewed the record, who revealed a masked field, who opened the policy and who downloaded the signed PDF. When a member asks who saw their information, the answer is a list, not a guess.

At rest
Bank, card and marketplace SSN fields are stored encrypted with AES-256-GCM. A member SSN comes back only as a mask, and a card CVV is deleted after 24 hours.
In transit
Data is sent over TLS.
Reveals
Written down before the value comes back, and rate limited.
Sign in
Email code or Google. Optional IP allowlist per user. Login history for owners.
Kept for
Seven years for activity, sign in and reveal logs. Two years for view logs.

Example member Activity timeline: an agent viewed the member record at 9:02 AM and revealed the date of birth at 9:04 AM; a back office user viewed the policy at 9:31 AM and downloaded the signed consent at 9:33 AM.

Questions

Questions before the audit.

What owners and compliance leads ask first. Anything not here, ask us on the demo.

Ask us in a demo
Does this make our calls TCPA compliant?
No software can promise that. QuoteTurbo checks DNC lists and calling hours before a dial, keeps consent and opt outs on the member, and records what happened. Your scripts, your lead sources and your counsel's advice decide whether a call is compliant.
Is the litigation scrub running?
Not yet. The scrub settings, the existing book scrub and the check log are in the product, and checks against the TCPA litigator list start once the list provider's API key is connected. Until then no number is checked against it, and the DNC lists and calling hours checks still run.
Do you scrub against the National Do Not Call Registry?
Not directly. The dial check covers your platform, agency and campaign DNC lists. Federal and state DNC matches come from the litigation scrub provider once it is connected, flagged by default and blocked only if your agency chooses.
How does consent from a lead vendor get recorded?
A vendor post can send a consent certificate link, the consent text version, the page URL, the IP and the time it was captured. They are stored with the post and the member timeline shows Consent recorded by the vendor. The certificate itself is not verified with its issuer, so keep your vendor agreements in order.
Are calls recorded, and who can play them?
Calls are recorded through the phone system and play in the call details, with a transcript where one exists. Agents see their own calls; a role with access to all call logs sees the rest. There is no recording announcement setting in the product today, so the disclosure lives in your opening script, and the transcript shows whether it was heard.
What about the Medicare Scope of Appointment?
There is no built in SOA tracker. Agencies upload their own Scope of Appointment form as an e-sign template, and it goes out with the same audit trail as any other envelope. The TPMO disclaimer prints from a merge field with your carrier and plan counts, and you can require a TPMO disclaimer read checkbox before a policy moves to Sold.
Which security controls can you name?
Bank, card and marketplace SSN fields are stored encrypted with AES-256-GCM, a member SSN comes back only as a mask, and data is sent over TLS. Revealing a masked field is written down before the value returns. Sign in is by email code or Google, an admin can limit a user to set IP addresses, and roles are built from a catalog of granular permissions. Ask us in the demo about anything this page does not name.

Watch a dial check run, start to finish.

A walkthrough of the register with the states and lead vendors your floor works.

QuoteTurbo helps reduce risk and keep records. It does not make a call compliant and is not legal advice.