All features

64 features across 9 modules

Every feature of every module. Below them are the 13 shared services and the 9 steps every module runs.

Sender Check

Text-message sender registration and opt-in proof

Checks a business text-messaging registration against the reasons carriers reject them, hosts an opt-in page with the wording carriers look for, and keeps the consent record a reviewer asks for. It is for agencies and resellers who register senders for many clients. Carriers make the final decision on every registration.

  • Registration pre-check

    Compares a 10DLC or toll-free registration, its opt-in page and its privacy policy against the reasons carriers publish for rejecting a campaign, before you submit. Carriers make the final decision.

  • Hosted opt-in page

    A sign-up page for text messages with the disclosure wording reviewers look for and a consent box that starts unchecked. Each submission is captured as it was shown.

  • Consent record per subscriber

    Ties each opt-in to one phone number and one named business, with the wording shown, the time and the device. Records are kept separately for each client an agency manages.

  • Append-only check log

    Every check and its inputs are written with their dates to a log that is added to and never edited.

  • Reviewer export

    Produces the record for one subscriber or one campaign as a single packet you can hand to a carrier reviewer or your own counsel.

  • Message scope

    Works out what each opt-in covers: marketing or informational messages, which program and which seller.

  • Opt-out propagation

    Carries a STOP reply to every system that sends for that business and records when each one acknowledged it.

  • Change watch

    Re-runs the pre-check when an opt-in page, a privacy policy or a carrier requirement changes, and says what changed.

Contact Gate

Calling and texting rules, checked before each contact

Answers allow or block before a call or text goes out: consent on file, do-not-call status, the recipient's local time, state rules and any opt-out. Writes the reason to the record. It works for human callers and for AI agents.

  • Allow or block before each contact

    Answers allow or block before a call is dialed or a text is sent, and gives the reason for the answer.

  • Consent on file

    Checks that a consent record exists for this number and this seller, and that the wording the person saw covers this kind of contact.

  • Do-not-call checks

    Checks the number against the national registry data you supply and your own do-not-call list, and records which list version was used.

  • Recipient-local hours and state rules

    Works out the recipient's local time and applies the calling-hour and frequency rules of their state, using the stricter answer when the state is uncertain.

  • Opt-out handling

    Records an opt-out from any channel, works out what it covers from the message it answered, and starts the clock for honoring it.

  • Block when uncertain

    When a required input is missing or stale, the answer is block, with the missing input named.

  • Tool for AI agents

    A check an AI voice or text agent calls before it contacts someone, so the agent gets the same answer a human caller would.

  • Decision log

    Each allow or block is written with its inputs and their dates, so it can be produced later exactly as it was.

Renewal Check

Subscription sign-up and cancellation flows

Audits a subscription checkout and cancellation flow against state automatic-renewal laws, watches the pages for changes, and keeps a dated log of what each subscriber was shown and agreed to.

  • Sign-up disclosure check

    Checks whether the renewal terms appear near the purchase button and whether consent to the renewal is a separate, unchecked action.

  • Cancellation path check

    Walks the cancellation flow from outside and reports whether a customer who signed up online can cancel online, and what stands in the way.

  • State rule comparison

    Compares the captured flow against the automatic-renewal rules of each state in the rule library, each with its source and effective date.

  • Reminder and price-change tracking

    Records which renewal reminders and price-change notices were sent to each subscriber, and when.

  • Acknowledgment record

    Records that the confirmation sent after sign-up included the renewal terms and how to cancel.

  • Page change watch

    Re-runs the checks when a checkout or cancellation page changes and says what changed.

  • Dated record per subscriber

    Keeps, for each subscriber, the disclosure version shown, the consent, the notices and any cancellation request, with dates.

Dispute Pack

Proof of agreement for card disputes

Assembles what a customer was shown and agreed to at checkout into the evidence a card dispute asks for: the terms, the disclosure, the acceptance and the usage that followed.

  • Acceptance record tied to the transaction

    Links what the customer was shown and accepted at checkout to the order and the charge that followed.

  • Recurring-billing disclosure history

    Keeps the renewal terms shown at sign-up and each reminder or price-change notice sent afterwards.

  • Device and login details

    Stores the device, address and login details recorded at sign-up and at later sessions, the kind of details card networks ask merchants to match.

  • Usage after purchase

    Attaches the activity you send us that shows the product or service was used after the charge.

  • Cancellation history

    Shows whether the customer asked to cancel, when, and what happened to the request.

  • One packet per dispute

    Assembles these records into a single document for one disputed charge.

  • Works beside your dispute tool

    The packet is handed to the dispute tool or processor you already use. Dispute Pack does not file the response for you.

Assent Log

Proof that a customer agreed to your terms

Records how your terms were presented and how each customer accepted them, version by version, so you can show what was presented and accepted when an arbitration clause or a limitation of liability is questioned.

  • Screen capture at acceptance

    Records what the screen looked like when the customer accepted: the notice, the link to the terms and the control they used.

  • Terms version tracking

    Records which version of the terms was in force and linked at the moment of acceptance.

  • Action record

    Records the action the customer took, such as ticking a box or pressing a labeled button, with the time and the device.

  • Account binding

    Ties the acceptance to one account, email address or phone number.

  • Re-acceptance tracking

    When the terms change, shows who has accepted the new version and who has not.

  • Flow check

    Flags sign-up flows where a customer can finish without acknowledging the terms, or where the notice is easy to miss.

  • Export for a declaration

    Produces the record for one customer in a form your counsel can attach to a declaration.

Decision Notices

Notices and records for automated decisions

Tracks which people were told an automated system was used in a decision about them, what they were told, and what they asked for afterwards.

  • Pre-use notice delivery

    Sends the pre-use notice for an automated system, and records what was sent, to whom and when.

  • Adverse-outcome notice tracking

    Tracks the notice owed after an unfavorable decision and the deadline for sending it under each rule in the rule library.

  • Opt-out requests

    Where a rule gives people a way to opt out of automated decisions, logs each request and what was done about it.

  • Explanation and human-review requests

    Logs each request for an explanation, a correction or a human review, with who handled it and the outcome.

  • Retention by rule

    Keeps each record for the period the applicable rule sets and shows when that period ends.

  • One view across states

    Shows, for each decision process, which state rules are in the rule library, their effective dates and their sources.

  • Export per person

    Produces everything one person was told and everything they asked for as a single packet.

Signal Check

Whether your site honors an opt-out

Loads your site the way a visitor does, sends an opt-out, and reports which tags still fire. Keeps a dated record of each test.

  • Test with and without a signal

    Loads your site twice, once as an ordinary visitor and once sending a browser opt-out signal, and compares what loads.

  • Banner opt-out test

    Uses the opt-out or reject control on your banner and records which tags fire afterwards.

  • Named tags

    Names each advertising or analytics tag that fired after the opt-out and the page it fired on.

  • Opt-out link check

    Checks that an opt-out link is present on the page and that it leads to a working control.

  • Scheduled re-tests

    Repeats the tests on a schedule and after a release, and says what changed since the last run.

  • Dated report

    Keeps each test with its date, the pages loaded and the results, in a form you can hand to counsel or a regulator.

Disclosure Proof

Proof that a required disclosure was delivered

Sends the disclosure a state requires before a contract is signed, records that it was delivered and acknowledged, and tracks the cancellation window that follows.

  • State form selection

    Picks the disclosure form for the state and the kind of deal from the rule library, each with its source and effective date.

  • Delivery before signing

    Sends the disclosure and records that it was delivered before the contract was signed.

  • Acknowledgment record

    Records the acknowledgment by the seller or homeowner, with the time and the device.

  • Cancellation-window tracking

    Tracks the cancellation or rescission period that follows, where the state provides one, and records any cancellation received.

  • Order check

    Flags a deal where the contract appears to have been signed before the disclosure was delivered.

  • Record per deal

    Keeps the form version, the delivery, the acknowledgment and the dates together for each deal.

  • Export per deal

    Produces the record for one deal as a single packet for a title company, a regulator or your counsel.

Shared services

13 services every module shares

These sit under the modules. This list names the parts and says what each one holds.

Consent record
One entry per person, per permission, per seller
Page and flow capture
Wording, layout and the action taken, as shown
Identity binding
Phone number, email, account, device
Rule library
Each rule with its source, version and effective date
Check engine
Wording and flow compared against the rule that applies
Decision log
Append-only, timestamped and exportable
Opt-out and withdrawal ledger
What was withdrawn, when, and who was told
Change watch
Re-checks when a page or a rule changes
Evidence packet
One export per person, built for a reviewer
Client workspaces
Separate records for each client an agency manages
API and webhooks
Ask before you send; get told when something changes
Agent tool
A check an AI agent calls before it calls or texts
Integrations
Connects to messaging platforms, CRMs, billing systems and dialers through the API and webhooks

The record

The 9 steps every module runs

All nine steps run in every module, from capturing what a person was shown to producing the record when someone asks for it.

1. Capture
Record the page, form or script a person was shown, the exact wording, the time, the device and the action they took. A screenshot alone is not a record; the wording and the event are.
2. Bind
Tie the event to one person, one phone number or account, and one named seller. A consent that cannot be linked to the person who gave it is the kind courts have refused to accept.
3. Check
Compare the captured wording and flow against the rule that applies: a carrier registration requirement, a calling rule, a state renewal law, a card-network evidence standard.
4. Scope
Work out what the permission covers. Marketing or informational, which channel, which seller, which product, and for how long.
5. Decide
Answer allow or block at the moment of use, with the reason. When the answer is uncertain the default is block.
6. Record
Write the decision, the inputs and their dates to a log that is appended to and never edited, so it can be produced later exactly as it was.
7. Propagate
Carry an opt-out, a cancellation or a withdrawal to every system that needs to honor it, and record when each one acknowledged it.
8. Watch
Re-run the checks when a page changes, a rule changes or a registration lapses, and say what changed.
9. Produce
Export the record for one person as a single packet: for a carrier reviewer, a card network, an auditor or your own counsel.

Reviewed 12 November 2026

Consentra is software. Nothing on this site is legal advice, and using Consentra does not by itself make a business compliant with any law or carrier rule. Whether a rule applies to your business is a question for your counsel.

See the consent record for yourself

Book a call and we show you the record on your own flow: what each person saw, what they agreed to, and what you can hand over when someone asks.