Security & Operational Controls for iGents
Outbound compliance is an operating discipline shared between the platform and the floor running it. This page names the controls that exist, what each one does, and where its limits are — instead of offering a certification badge.
- DNC scrubbing as a shared operational responsibility
- Honeypot detection and blacklists, with stated limits
- Disposition tracking on every call outcome
- Approved health-adjacent questions with a defined human handoff
3–5 day trial · No credit card · ~15-minute deployment
What we do not claim
- No certification claims for health-data processing
- No claim of complete protection against litigator or honeypot numbers
- No blanket “built-in compliance” for your campaigns
- No guarantee that removes your own regulatory obligations
Control 01
DNC is a shared operational responsibility
Do-not-call scrubbing runs as part of the workflow, and internal do-not-call requests captured on a call are recorded as structured outcomes so they can be actioned in your list management. That is one half of the job.
The other half stays with you. Your organisation owns the list sources, the suppression lists it maintains, the registry obligations that apply to your campaigns and buyers, and the decision about what gets loaded into the dialer in the first place. iGents cannot validate the provenance of a list they did not source.
| Responsibility | Owner |
|---|---|
| List sourcing and provenance | Your organisation |
| Registry and buyer-specific suppression obligations | Your organisation |
| Scrubbing applied inside the calling workflow | Shared |
| Capturing a do-not-call request made on a call | iGents |
| Recording that request as an actionable outcome | iGents |
| Applying suppression to future list loads | Your organisation |
Control 02
Honeypot detection has limits
Honeypot detection and blacklist checks are applied to reduce exposure to known trap and litigator numbers. It is a real control and it is designed to reduce exposure.
It is not complete, and no vendor honestly claims otherwise. Trap numbers rotate, new ones are seeded continuously, and any detection set reflects what is known at the time of the call. Treat it as one layer alongside your own list hygiene, buyer vetting and legal review — not as a replacement for them.
- Known trap and litigator numbers screened against blacklists
- Detection reflects what is known at call time, not everything in existence
- Newly seeded numbers can pass any detection set
- Your list hygiene and buyer vetting remain necessary
Control 03
Keep protected detail outside the automated layer
Health-adjacent campaigns are configured so iGents ask only the approved screening questions your campaign requires. Protected detail is not solicited beyond that set.
Conversations that move toward sensitive health information are transferred to your human team rather than continued in the automated layer. Operators remain responsible for validating whether the full processing chain fits their regulatory requirements.
Approved questions only
The screening set is the campaign's, and iGents do not probe beyond it.
Transfer, not continue
Conversations heading into protected detail move to your human team.
Stated plainly
No certification is implied; validate the complete processing chain against your requirements.
Control 04
Protect the workflow without making absolute claims
Disposition tracking is the control operators underuse. Every call — connected or not — closes with a structured outcome, which means an auditor can reconstruct what happened across a campaign rather than sampling recordings and inferring the rest.
That auditability is the honest security story here: consistent configuration, complete outcome records and a clear boundary at the transfer. It does not amount to a guarantee, and it is not offered as one.
- Structured disposition on every call outcome
- Configuration changes applied uniformly rather than per seat
- Qualification data recorded per field for review
- Human verifier and closer beyond the transfer boundary
- Insight summaries every 3–4 days to surface drift early
FAQ
Controls questions
How do iGents handle sensitive health information?
iGents follow the approved screening set and transfer to your human team when a conversation moves toward sensitive health information. This is a workflow boundary, not a certification claim.
Does honeypot detection guarantee we avoid litigators?
No. It screens against known trap and litigator numbers and reduces exposure, but detection reflects what is known at call time and cannot cover newly seeded numbers.
Who is responsible for DNC?
It is shared. Scrubbing runs inside the workflow and do-not-call requests are captured as structured outcomes, but list sourcing, registry obligations and suppression management stay with your organisation.
Can we audit what happened on a campaign?
Yes. Every call closes with a structured disposition written back in your existing codes, so campaign-level reconstruction does not depend on sampling recordings.
Walk the controls before you trial
A deployment lead will map each control to your campaigns and list sources ahead of a 3–5 day trial.
WhatsApp consultation for a direct scoping conversation, or send campaign details through the trial form.