Compliance by construction
AI voice agent compliance starts before the call
VoiceForge makes permission to operate an execution rule. An outbound call cannot run unless its purpose and compliance checks pass.
A hard outbound gate
Compliance is evaluated before execution, not added as a warning after a campaign is configured.
- Consent records and allowed purpose
- DNC, DND, and opt-out suppression
- Calling windows, AI disclosure, and recording notice
- Audit logs for critical decisions
Allowed purposes are explicit
Supported outbound purposes include appointment reminders, missed-call callbacks, lead-form callbacks, order and event confirmations, and requested follow-up.
High-risk uses are blocked by default
Cold sales, political calls, debt collection, healthcare diagnosis, and financial or legal advice are not normal VoiceForge workflows.
Questions operators ask
The controls support responsible operations, but they do not replace legal review.
- Can VoiceForge be used for cold sales calls? Cold sales is blocked by default. VoiceForge is built for inbound calls and allowed, consent-based purposes such as appointment reminders, missed-call callbacks, lead-form callbacks, order confirmations, event confirmations, and requested follow-up.
- What happens before an outbound call runs? The compliance engine checks the call purpose, consent record, DNC/DND status, opt-out state, calling window, AI disclosure, recording notice, and required audit information. The call runs only when the gate passes.
- Does software replace legal advice? No. VoiceForge provides operational controls, not legal advice. Each operator remains responsible for the laws and permissions that apply to the call, location, industry, and data.