AI Data Policy

1. What AI Does in DialerBee

DialerBee uses AI for one primary purpose: Answering Machine Detection (AMD). When a call connects, the system transcribes the first few seconds of audio and classifies the transcript as a live human or an answering machine. This classification determines whether the call is routed to an agent or handled as voicemail.

Predictive dialing pacing also uses statistical models to optimize call-to-agent ratios, but this operates on aggregate campaign metrics — not individual call content.

2. What Audio Data Is Processed

• AMD processes a short initial segment of call audio (typically the first 3 seconds after pickup)
• Audio is transcribed in real time and the transcript is classified immediately
• Raw audio segments used for AMD are not stored long-term
• Classification results (human/machine, confidence score, model version) are retained for analytics
• Full call recordings are a separate system and governed by your recording policy and retention settings

3. Model Training & Tenant Isolation

• AMD feedback (agent corrections) can be tenant-scoped and governed by customer retention and AI settings
• Customer call data is not used to train shared cross-tenant models by default
• Agent override data stays within the tenant boundary unless explicitly configured otherwise
• Base AMD models are trained on licensed, non-customer datasets and internal test data

4. Your Controls

5. Third-Party AI Services

AMD transcription may use Google Cloud Speech-to-Text. Only the short initial audio segment is sent for processing. Google's data processing terms apply to this service. See our subprocessor list for details.

6. AI Decision Audit Trail

AI classifications can be logged with confidence score, model version, and human override status where audit logging is configured. This audit trail supports transparency, debugging, and compliance reporting.