Voice AI Consent Check Across Forms, Surveys, and Calendars

By Sparkforge Support Team ·Last reviewed May 3, 2026

Before Voice AI dials, Sparkforge scans Forms, Surveys, and Appointment Forms or Calendars for valid opt-in tied to the contact and phone number. Add a required consent checkbox to each asset and verify in the contact timeline.

Sparkforge Voice AI runs a pre-call compliance scan to confirm a contact has opted in to receive voice calls. The consent engine now recognizes opt-in collected through Forms, Surveys, and Appointment Forms or Calendars, not just standard Forms.

Why the broader scan matters

Broader coverage: consent in any of the three asset types is honored before dialing.
Fewer false blocks: valid opt-in from any supported asset lets eligible calls through.
Centralized compliance: pre-call validation cuts down on manual review.
Better auditability: source and timestamp data show up in the contact timeline and call logs.

Sources scanned before a call

Forms (existing coverage)
Surveys (newly supported)
Appointment Forms or Calendars (newly supported)

Tip: use consistent consent language across every asset so allow and block decisions stay predictable.

What counts as valid opt-in

A clear, affirmative action such as a checked consent box.
Visible consent text that explicitly references voice calls. Avoid vague or bundled language.
A timestamp, plus submission detail like IP and user agent when available.
The submission must be tied to the contact and to the phone number you intend to dial.

Consult counsel for jurisdiction-specific wording. Keep the language region-agnostic and adaptable.

How to set it up

Step 1: Update Forms

Open or create a form.
Click the settings icon to edit consent details.
Add a required consent checkbox and confirm the phone field is mapped to the contact's phone.
Confirm submissions save the timestamp and the displayed consent text.

Step 2: Update Surveys

Add a required consent item, either a checkbox or explicit confirmation step.
Capture or confirm the phone number so consent is associated with the right contact.

Step 3: Update Appointment Forms or Calendars

Enable a required consent checkbox on the booking form.
Make sure the booking collects the phone number used for Voice AI calls.

Step 4: Verify with a test contact

Submit each asset once with a test contact, then open the contact timeline to confirm the consent entry, source, and timestamp appear correctly.

Investigating blocked calls

Open Voice AI call logs and the contact timeline to see the decision, the reason, and any consent source the system found. Recent opt-out or DNC flags always override prior opt-in.

Frequently Asked Questions

Is opt-out always stronger than opt-in?

Yes. A recent opt-out or DNC flag blocks calls even when prior opt-in exists for the same contact and number.

Do I need consent per phone number or per contact?

Best practice is number-specific consent. If your policy uses contact-level consent instead, confirm with your legal team that it satisfies your jurisdiction.

Are older Survey or Calendar submissions recognized?

Yes, as long as the submission is tied to the contact and the phone number being dialed. Verify in the contact timeline and call logs.

Where can I see why a call was blocked?

Open Voice AI call logs and the contact timeline. Both surface the decision, the reason, and the consent source the system relied on.

What should the consent text say?

Use a clear statement that authorizes voice calls specifically. Avoid bundling with unrelated permissions like marketing email or SMS in the same checkbox.