One person asking you to stop, applied everywhere at once. A revocation spoken on the call, entered on the keypad, written in the dashboard or sent to the API converges on a single database transaction that appends the revocation record, writes the internal suppression row, withdraws the consent standing behind the number and sets the dial-time fast path together.
Everything downstream follows from that one write. Every active campaign for the tenant stops calling that number, pending dials are cancelled rather than drained, and the next dial-time read finds the suppression already in place. A narrowed revocation is the dangerous failure here, so the write over-suppresses rather than under-suppresses by design: a person who asked you to stop about one thing is not called about another while somebody works out whether they meant it.
Federal rules give a caller a reasonable time not to exceed ten business days to honor a revocation made in any reasonable manner, and they treat a revocation received by any such method as definitive rather than as scoped to the campaign it arrived on. Vocapable does it in the same write. The ten business days is the bar the rules set; the same transaction is a property of our write path, and it leaves your team nothing to schedule, nothing to chase and nothing to reconcile afterwards.
The one revocation write path, and what it leaves on the record afterwards, are on the compliance engine page.