How My AI Front Desk detects sensitive data, prevents PCI and SSN collection, and gives you granular control over what transcript data flows to external integrations.
How each type of sensitive data is detected and handled during AI phone calls.
| Data Type | Detection | Action | Status |
|---|---|---|---|
| Credit card numbers (PCI) | Pattern detection | Not collected — AI redirects to secure channel | Active |
| Social Security numbers | Pattern detection | Not collected — AI redirects to human | Active |
| Phone numbers | Captured intentionally | Stored as contact info in CRM | By design |
| Email addresses | Captured intentionally | Stored as contact info in CRM | By design |
| Medical information (PHI) | Not auto-detected | Recommend human handoff for PHI | Guidance |
Best practices for ensuring payment and financial data never enters call transcripts.
Configure your AI receptionist to redirect payment conversations to a secure channel (payment portal link via SMS, or transfer to a human agent). This prevents PCI data from entering transcripts entirely.
Set up escalation rules so that when a caller mentions payment, credit card, or billing, the AI transfers to a human agent or sends a secure payment link via SMS. No sensitive financial data is processed by the AI.
Granular controls over what transcript and call data is pushed to your CRM integrations.
| Control | Available | Details |
|---|---|---|
| Send call summary to CRM | Yes | Push AI-generated summary to Salesforce, HubSpot, etc. |
| Send full transcript to CRM | Yes | Configurable: on/off per integration |
| Send link only (no text) | Yes | CRM receives a link to the transcript rather than the full text |
| Suppress transcript from CRM | Yes | Send only metadata (caller, duration, outcome) with no transcript |
| Field-level suppression | Roadmap | Coming soon: suppress specific fields from CRM sync |
Request the full security pack or schedule a call with our security team.