Compliance Guide — WhiteBoxForge AI Receptionist

Last updated: June 26, 2026 · Version 1.1

This guide explains, in plain English, the laws that apply when you use an AI receptionist and how WhiteBoxForge (HarbingerScope LLC d/b/a WhiteBoxForge) helps you meet them. It forms part of our Acceptable Use Policy: by using the Service, you agree to operate it in line with the responsibilities described here.

Before you go live

A short pre-launch review keeps your line compliant from the first call:

• AI disclosure stays on. Your assistant identifies itself as a virtual/AI assistant at the start of each call.
• Recording notice stays on. The assistant states that the call may be recorded for quality at the start of each call.
• Reminders and outbound. Contact only customers who have consented, honor opt-outs, and respect Do-Not-Call requirements.
• Test call. Place one real test call and confirm the greeting and booking flow before you forward your business line.

Why these matter

AI disclosure. The FTC prohibits deceiving callers into thinking they are speaking with a human. California's AB 2905 requires disclosing an AI or artificial voice on calls, and Utah's UAIPA requires proactive disclosure for regulated occupations (healthcare, legal, financial) and on request otherwise. Texas's TRAIGA focuses on government and healthcare contexts, where disclosure is the safe default. WhiteBoxForge keeps disclosure on by default.

Call-recording consent. Federal law permits recording with one party's consent, but 13 states require all parties to consent: California, Connecticut, Delaware, Florida, Illinois, Massachusetts, Maryland, Michigan, Montana, Nevada (phone), New Hampshire, Pennsylvania, and Washington. Because a caller's location is not known in advance, the assistant delivers the recording notice on every call, and continuing the call is treated as consent.

Inbound vs. outbound (TCPA). When a customer calls you, the TCPA's consent rules generally do not apply, and the AI may answer. When you call or text a customer — reminders, follow-ups, or missed-call callbacks — the FCC's 2024 ruling treats AI voices as artificial or prerecorded: you need the customer's prior consent, must identify yourself, must offer an opt-out, and must respect the Do-Not-Call list. Marketing calls and texts require written consent, and SMS requires A2P 10DLC registration.

Voice & biometric

The assistant uses a synthetic, library voice and does not create a voiceprint or biometric identifier of callers. If you operate where biometric law applies (e.g., Illinois BIPA, Texas CUBI, Washington), you are responsible for any notice or consent your use requires.

How WhiteBoxForge helps

The disclosure and recording notice ship on by default. We publish a Data Processing Addendum and a current sub-processor list, and record that the disclosures were delivered on each call for your records. The controls live in your panel: you stay in control of your script, and we give you the tools to use it lawfully.

Questions: HarbingerScope LLC d/b/a WhiteBoxForge · 7727 Vacek Meadows Loop, Richmond, Texas 77469 · [email protected].