How RevSave handles consent, contact, and compliance

Before contact

RevSave checks consent, suppression, and quiet hours before placing a call. The rules engine also checks phone availability, cart or payment status, prior contact, order value, and brand-specific exclusions.

AI disclosure

The agent identifies itself as an AI assistant at the start of every call and names the brand connected to the recovery event.

What the agent does not do

• It does not invent discounts, guarantees, product claims, or policy exceptions.
• It does not collect card details over the phone.
• It does not contact a suppressed or opted-out number.
• It does not continue after an opt-out request.
• It does not answer outside the approved knowledge base.

Opt-outs and suppression

Opt-outs are honored immediately. Complaints, bad numbers, do-not-call requests, and sensitive outcomes are tagged and suppressed across enabled call and text workflows.

Recording and retention

Recording follows the client’s approved configuration. Retention rules apply separately to recordings, transcripts, event data, attribution records, and security logs. Client-specific schedules are documented during implementation.

Audit trail

Each session records the triggering event, rule-check result, disclosure, call outcome, message status, secure-link event, reason code, opt-out state, and attributed order when available.

Brand responsibility

Each brand supplies counsel-approved consent language, scripts, offers, suppression data, quiet hours, recording instructions, and escalation rules. RevSave executes the configured controls and records what occurred.

Review the workflow

RevSave can walk your team or counsel through the rules engine, sample disclosures, suppression behavior, retention settings, and audit records. Email zain@revsave.ai to arrange a review.