Read-Only First: How Our AI Takes Order Actions

AI voice agents are starting to do more than talk. Some can now process a refund, edit an order, or apply a discount in the middle of a call — Aircall's AI Actions, Alhena, and Consio all advertise versions of this. It's a real direction for the category, and a useful one.

We take a different path to the same place. Instead of a fixed menu of mid-call actions, AI ReFounder gives you open control: through Functions, you can connect whatever actions your store needs and let the agent call them. The capability isn't the question — what we add deliberately is write by default. Our recommendation is read-only first, then turn on the rest as you're ready.

Here's what that means, and why we think it's the right way to bring an AI into your orders.

The Ladder of What an Agent Can Do

It helps to separate what a voice agent does on a call into three levels:

• Read — knows your catalog, order status, and inventory. "Your order shipped Tuesday." "The medium is in stock."
• Guide — answers questions, recommends products, walks the customer to checkout.
• Write — changes something in your store: cancel or edit an order, issue a refund, trigger a custom workflow.

Read and guide are understanding and conversation. Write is the agent taking a real action on its own. That last level is powerful — which is exactly why we make it a deliberate choice, not a default.

Why Read-Only Is the Right Place to Start

When you bring any new system into your store — a person, an integration, or an AI — you don't hand it the keys to everything on day one. You let it prove itself on lower-stakes work first, watch how it performs, and expand its responsibilities as it earns them. That's not caution for its own sake; it's the principle of least privilege that good systems are built on.

Read-only is that proving ground. In read-only mode the agent already does most of the job: it answers every call, knows your products, helps customers who are stuck, and captures after-hours sales you were missing. You get to listen to the calls, read the transcripts, and see exactly how it handles your store before it ever changes an order.

This isn't a statement that AI "isn't ready." The models are capable. It's about sequence: prove reliability where mistakes are cheap, then extend into actions where they aren't — once you've seen the track record yourself.

One action already sits safely between read and write: the agent can place an order on hold — a reversible pause, so nothing ships before your team reviews it. That alone catches most of the value of "doing something on the call." We go deep on it in how we save 35% of cancellation requests.

The Honest Position

So here's where we stand. Our recommendation is to start read-only — read, guide, pause — and watch the agent work on real calls first.

But that's advice, not a limit. Through Functions, you can give the agent whatever actions your store needs — cancel an order, edit it, issue a refund, trigger a custom workflow. The capability is fully in your hands. We just don't switch write actions on for you by default; you turn on what you want, once you've seen the agent handle your store and decided it's ready.

So this isn't "our AI can't change orders." It's "our AI changes orders when you decide it should, not before." Read-only is the default and the recommendation; the controls are yours.

How to Add Write Actions Safely

When you add write actions through Functions, the same discipline that makes read-only a good start applies to turning on the rest:

• Start with low-risk actions — pausing, tagging, status updates (easy to undo) before anything that moves money.
• Gate the money — keep a human confirmation step on refunds or anything above a threshold you set, at least until you've watched it run.
• Log everything — every action traceable, so you can review and roll back.
• Test on your own store first — run a new function on real-but-controlled calls before it's live for every customer.

Functions is flexible by design, which means it rewards setting up thoughtfully — and you don't have to figure it out alone. If you have questions about how to use or configure functions for your store, just reach out. We're always happy to help you wire it up the right way.

Bottom Line

The category is moving toward AI that takes real actions on calls, and so are we — on terms you control. The question was never whether an AI can process a refund. It's whether you've seen it handle your store well enough to trust it with one.

Read-only first answers that the right way: prove it on every call, lean on the on-hold safety net, and extend into write actions through Functions once you've earned the confidence to use them. For a founder-led store, that's not a missing feature. It's how you end up with an AI you actually trust with your orders. See exactly where the agent's line sits today on the how-it-works walkthrough.