Updated June 13, 2026. AI that answers real phone calls touches real rules: recording consent, caller notification and data handling. Here is how AeroReception deployments handle them. This page is transparency, not legal advice for your business.
Recording laws vary by state and country: some require one party's consent, some require everyone's. During setup we configure your deployment for the rules that apply to your location and callers, including a notification message at the start of the call where required. You approve the exact wording before go-live.
Some jurisdictions require or are moving toward requiring disclosure that a caller is speaking with an AI. AeroReception supports disclosure lines natively, and we configure them per client. Our default recommendation is honesty: a front desk that performs well doesn't need to pretend to be human.
Call data belongs to the business the caller dialed. It flows into that business's own systems (calendar, CRM), is retained per their configuration, and is deleted on request. Details are in the Privacy Policy and Security pages.
Where deployments send booking confirmations or follow-up texts, they are transactional messages triggered by the caller's own request, with opt-out honored. We do not run cold outbound calling or texting campaigns through AeroReception.
If a rule applies to your deployment, we'd rather configure for it on day one than retrofit it after a complaint. Bring your compliance questions to the demo call, and if your counsel has requirements, we build to them. Questions: jrmylzr25@gmail.com.