Skip to content
Inflection Point

Your employees' phones can now move data between apps without anyone touching the screen.

Agentic phones are different. Nobody installed anything. The capability came with the phone.

Your employees’ phones can now book flights, order food, and move data between apps without anyone touching the screen.

Not someday. Right now.

This spring, Google shipped agentic AI features on Samsung Galaxy S26 and Pixel 10 phones. Gemini, Google’s AI, can now take multi-step actions across apps on the user’s behalf. You tell it “order my usual from DoorDash” or “book a ride to the airport.” Gemini opens the app, navigates the menus, fills in the details, and completes the task. The user watches it happen in a window and approves the final step.

This isn’t a chatbot answering questions. This is an agent that operates your apps for you.

Here’s why this matters to you.

Back in March, I wrote about AI agents on laptops and desktops (OpenClaw and similar tools). Those agents required someone to install software on purpose. You could find them. You could block them. You could write a policy.

Agentic phones are different. Nobody installed anything. The capability came with the phone. It showed up in a software update. And your employee’s personal Samsung or Pixel already has it.

Now picture this. An employee opens their work email on their personal phone (because you allow BYOD). Gemini can read that email. The employee asks Gemini to “summarize my inbox and draft replies.” Gemini pulls data from Outlook, cross-references it with their calendar, and drafts responses that include customer names, project details, and financial figures. All processed through Google’s cloud.

No one in IT approved this. No one in cybersecurity reviewed it. And your acceptable use policy almost certainly doesn’t cover it, because it was written for a world where humans operated apps. Agentic phones break that assumption. The phone doesn’t wait for instructions. It acts.

And it gets bigger. At its June developer conference, Apple announced the same kind of capability for the iPhone. Its new Siri can take actions across your apps, and it runs on Google’s Gemini under the hood. Apple says it ships later this year. When it does, the agentic phone won’t be limited to Samsung and Pixel users. It’ll be on every phone in your building.

So what should you do?

  1. Check your acceptable use policy right now. Does it cover what an AI agent on a personal phone can do with company data? If it only addresses “apps employees install,” you have a gap.
  2. Add a section on agentic AI to your BYOD policy. Cover three things: what company data the phone’s AI agent can access, whether employees can use voice commands that process work information, and what happens when the agent sends data to a cloud service.
  3. Talk to your employees about it. Most of them don’t know their phone can do this. Some discovered it by accident. A short, clear message from leadership (“here’s what’s OK, here’s what’s not”) does more than any technical control right now.
  4. Ask your MDM vendor what controls exist for agentic features. This is new territory for mobile device management. Some vendors are ahead of it. Most aren’t. Ask the question now so you’re not surprised later.
  5. Treat this as an update to your AI governance program, not a new one. If you already have an AI acceptable use policy, extend it to cover phone-based agents. If you don’t have one yet, this is your reason to start.

The pattern is the same one we’ve seen with every new technology: the capability arrives before the controls. The organizations that close that gap first don’t just avoid incidents. They build the kind of trust with employees and customers that’s hard to earn back once it’s lost.

Does your acceptable use policy cover what your employees’ phones can do on their own?

-Kip