Card numbers and SSNs redacted
When a caller reads out a card number or a Social Security number, icepac.ai removes it from the transcript and the summary. Your team sees that a number was given, not the number itself.
Trust
Your callers share names, dates of birth and sometimes card numbers. icepac.ai protects that information on every call, and you decide exactly what the AI may say and do.
Built for privacy
Built for HIPAA: we sign a business associate agreement (BAA), and patient details are protected by identity checks, redaction, locked fields and logged access.
When a caller reads out a card number or a Social Security number, icepac.ai removes it from the transcript and the summary. Your team sees that a number was given, not the number itself.
Dates of birth, account details and other protected fields stay hidden by default. Only people you give permission to can reveal them.
Each time someone reveals protected information, icepac.ai records who, what and when. You can review the log at any time.
Front desk, managers and owners each see what their role needs. Recordings, transcripts and reports follow the same permissions.
Calls, transcripts and reports move over encrypted connections between your phones, your browser and the platform.
Recordings and transcripts are kept with your call history on a phone system dedicated to your organization, not a shared pool. Speech recognition and the AI voice run on outside processing services that we contract with.
AI guardrails
Consent and recording notices
You choose which lines record. A recording notice plays at the start of the call in your words, and you can set it for all-party-consent states such as Florida. Text messages go only to numbers that have agreed to receive them, and consent is tracked for each phone number. A caller who opts out stays opted out.
Data retention
Set how long recordings, transcripts and reports are kept. Shared customer reports use private links that expire, and you can revoke a link at any time. Nightly backups protect your settings and records.
Built for HIPAA: we sign a business associate agreement (BAA), and patient details are protected by identity checks, redaction, locked fields and logged access. Access is role-based, every reveal of a protected field is logged with who opened it and when, and connections are encrypted in transit.
Speech recognition and the AI voice run on outside processing services that we contract with, so call audio is processed there during the call. Recordings and transcripts are kept on the phone system dedicated to your organization.
No. The AI works only with the scheduling and contact details it needs to handle the call, and it reads back only what is already on file.
It says so plainly and offers to connect the caller with your team, or takes a message with a callback number.
Only the people you allow. Access follows each person's role, and protected details stay hidden unless someone with permission reveals them.
Yes. In your free demo we show your team the privacy settings, the permissions and the reveal log on a live system. For healthcare practices, we sign a business associate agreement (BAA).
We will walk your team through redaction, permissions and the AI guardrails in a free demo of about 20 minutes, and answer your security questions.
Rather talk now? Use the chat button in the corner.
Or call 800-423-3221