REALLY Launches Carrier-Native Voice Clone for Calls

REALLY, an Austin-based independent wireless carrier that operates on T-Mobile's 5G network, announced a product called Clone, an AI agent designed to answer inbound calls, screen callers, and place outbound calls on behalf of subscribers using the subscriber's real phone number and a cloned version of their voice, VentureBeat reports. Per VentureBeat and PCMag, the company says Clone will enter beta this quarter or in the coming weeks, and PCMag reports the company plans to offer early access free to new and existing customers. PCMag quotes the company: "Record a few minutes of conversation so Clone can learn your speech patterns, tone, and communication style. The more you give it, the more it sounds like you." PCMag additionally reports the company is emphasising privacy controls and says Clone "processes everything inside a secure enclave, locked, encrypted, and processed in isolated ha[rdware]" and that it will not sell subscribers' personal data to advertisers.

VentureBeat frames Clone as operating at the carrier layer rather than as a third-party application, which the coverage says lets the agent place and receive calls using the subscriber's actual phone number without call forwarding, secondary numbers, or VoIP workarounds. VentureBeat reports the feature aims to navigate IVR menus, cancel subscriptions, screen and transcribe calls, and engage spam callers using the subscriber's voice. PCMag and VentureBeat both describe the system as trained on recordings supplied by the subscriber to model their communication style; PCMag reproduces the company's setup guidance indicating a few minutes of recorded conversation.

Editorial analysis: Carrier-layer voice agents represent a shift in control from app-level assistants to telecom infrastructure, which changes both integration possibilities and the attack surface. Operators embedding AI at the carrier layer avoid some technical friction that app-based assistants face, but doing so concentrates voice authentication and call origination authority inside network-controlled systems, increasing stakes for secure key management and access controls.

MakeUseOf's coverage by Josh Hawkins and PCMag raise immediate abuse scenarios, including scammers using cloned voices to impersonate subscribers and fraudsters exploiting call-origin authenticity to bypass defenses. PCMag explicitly questions what would stop Clone from being abused to mimic others' voices, and MakeUseOf frames carrier-level voice-cloning as crossing a privacy line. These are reported concerns from the outlets, not assertions about REALLY's internal controls.

Editorial analysis: Observers should track:

• •the beta's enrollment flow and consent UX for recording voice samples
• •technical details of the claimed "secure enclave" processing and any third-party model providers
• •operator safeguards for preventing unauthorized model retraining or voice-sample theft
• •regulator or carrier-industry responses on consent and authentication for voice-originated transactions. Also monitor whether banks, identity providers, and enterprise IVR systems update voice-authentication policies in response

Editorial analysis: Engineers and security teams integrating voice or telephony AI should treat carrier-layer voice agents as high-impact threat vectors, re-evaluate voice authentication assumptions, and consider multi-factor approaches for sensitive transactions rather than relying on caller voice alone.