Security, consent and data handling
How Autessa Phone & Texting protects calls, texts and the people on them
Autessa Phone & Texting keeps sensitive details out of places they should not be: card digits go on the keypad instead of to the AI, recording is off until you turn it on, Call Redaction cleans recordings before they are saved, and texting consent is enforced on every message.
Controls
What is protected, and how?
| Area | How it works |
|---|---|
| Who can use Phone | People whose role can use agents. The browser phone registers only for them. |
| Who can set up numbers | Company admins (the owner or people who can manage team members) see Numbers & call flows and Speech vocabulary. |
| Who can register for texting | Only the company owner submits or changes A2P 10DLC registration; everyone else sees it read-only. |
| Calling out from a number | You need permission on that number. Numbers use Autessa sharing: private, company or specific people, with read, write or admin. |
| Twilio credentials | All four values for a linked Twilio account are encrypted before they are stored. Unlinking restores your previous Twilio settings. |
| Incoming webhooks from your Twilio account | Verified by Twilio signature, which is why the auth token is required. |
| Consent records | Phone numbers are stored encrypted and shown masked. Each record keeps the exact wording, its source and any evidence. |
| Business tax ID | Your EIN is shown back with only the last four digits. |
| Recording | Off by default per number, with an optional announcement such as "This call may be recorded." |
| Retention | Separate retention days for recordings and for transcripts. |
| Call Redaction | Removes card numbers, expiry and CVV, Social Security numbers, bank and account numbers, dates of birth, phone numbers, emails and addresses, replacing audio with silence or a tone. Only the cleaned copy is saved. |
| Recording links | Short-lived links that expire after about ten minutes. |
| Secure keypad capture | Card, bank and Social Security digits are typed on the keypad while the AI and recording are paused; the agent gets only a masked summary and a handle. |
| Sensitive values in transcripts | Agents can mask sensitive values in texts and transcripts. |
| Texting send rules | A text goes out only to someone who texted you in the last year or has an approved consent record. Opt-outs always win, and STOP, START and HELP cannot be overridden. |
Trust Center
Security documentation for Autessa
Autessa's security program, policies and reports are published in the Autessa Trust Center.
FAQ
Security questions
Can the AI hear card numbers on a call?
Not when you use secure keypad capture. The caller types the digits on the keypad while the AI and the recording are paused, and the agent only receives a masked summary and a handle it can pass to a payment step.
Are calls recorded by default?
No. Recording is off by default on every number; transcripts are on. You choose per number, with an announcement and retention days for each.
Where can I read about Autessa's certifications?
See the Autessa Trust Center at trust.autessa.com for security documentation and reports.
Am I responsible for recording-consent laws?
Yes. Recording-consent laws vary by place, and following them is up to you. The recording announcement helps you tell callers.
100% customizable, code and all
Make Autessa Phone & Texting fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours