Should You Let an AI Assistant Make Phone Calls for You?

Yes for calls where the worst outcome is a wrong answer you can check in thirty seconds. No for calls that create a commitment, move money, or require proving who you are. That is the whole decision, and it holds no matter which assistant you use. An assistant that phones a hardware store to ask whether a part is in stock is doing errand work you would rather skip. An assistant that phones your insurer to change a policy is speaking as you, to someone who will act on what it says, with no easy way for either side to catch a small mistake before it turns into a real one.

This stopped being hypothetical some time ago. Google now offers what it calls agentic calling: you search for a product with a phrase like near me, answer a few short questions about what you want, and Google places the calls to local businesses for you and sends back a summary by text or email. The rollout is limited to the United States. The interesting part is not the technology, which mostly works. It is that the decision of which calls to hand over has quietly become yours to make, and nobody hands you a rule for it.

What the person on the other end actually experiences

Start here, because most advice about assistant calling skips it. There are two people in a phone call and only one of them opted in. When you delegate a call, someone at a shop or a front desk picks up expecting a customer and gets a system instead. Whether that is fine or rude depends almost entirely on who they are and what you are asking.

For businesses, the receiving side has been given some controls. The Google help page for business owners describes these as automated calls placed on behalf of customers, lists what they are used for, including booking appointments, checking wait times, and confirming pricing and availability, and states that the calls are monitored and recorded for quality assurance. A business can ask to be taken off the list during the call itself, or switch the calls off in its profile settings. The same page notes the feature is limited to the United States and excludes five states: Indiana, Louisiana, Minnesota, Montana, and Nebraska. It does not explain the carve out, which is worth noticing on its own. When a company draws a map around a feature and does not say why, the reason is usually that the rules underneath are not uniform.

For individuals, none of that exists. Your friend, your landlord, and your mother have no opt out setting and no expectation of being called by software. That asymmetry is the cleanest line available: an automated call to a business is an inconvenience absorbed by a job, and an automated call to a person is a message about how much their time is worth to you.

Three questions that decide every case

You do not need a policy for this. You need three questions, asked in order, before you hand over any call.

1. Does the call create a commitment? Asking whether something is in stock creates nothing. Agreeing to a deposit, a cancellation, or a change of terms creates something that persists after the call ends and is difficult to unwind.
2. Does it require proving who you are? The moment a call needs an account number, a date of birth, a PIN, or the last four digits of anything, you are no longer delegating an errand. You are handing over the pieces of your identity that exist to stop other people from acting as you.
3. Can you verify the answer cheaply? If checking the result costs you one glance at a website, delegate freely. If the only way to find out you were told something wrong is to show up, or to read a statement next month, the call is not a good candidate.

Notice that none of these questions is about capability. Assistants have gotten good enough that the call will usually go smoothly. Smooth is not the same as safe. The question is what happens in the small percentage of calls that go sideways, and who absorbs the cost.

A working list of what to hand over

How to delegate a call without losing the thread

1. 1

   Write the question down before you delegate it

   Not for the assistant, for you. A call you did not make is a call you will misremember, and a vague brief produces a vague summary that reads as though it answered something.
2. 2

   State the limit out loud

   Ask about availability and price, do not book. Ask about the wait, do not give a name. The limit is the part people skip, and it is the only thing standing between an errand and a commitment.
3. 3

   Ask for what was said, not just the conclusion

   A summary that says the item is available is worth much less than one that says a person named the price and the quantity. If all you get back is a conclusion, treat it as a lead to verify, not a fact.
4. 4

   Capture the outcome within a minute of getting it

   This is where delegated calls actually leak. The call succeeds, the summary arrives while you are doing something else, and a week later you cannot remember which of three shops had the part. Save the answer and the follow up date at the moment it lands.

Where the disclosure rules stand right now

The honest summary is that the rules are uneven and you are ahead of them. In the European Union, Article 50 of the AI Act sets transparency obligations for systems that interact directly with people, which means a person is supposed to be told they are dealing with an AI system unless it is obvious from the situation. We wrote about what the AI Act actually gives you as a user when the broad transparency threshold arrived. In the United States, where the calling features described here currently live, there is no single national rule that makes an assistant announce itself on every call, and state law varies, particularly around recording. None of this is legal advice, and it points to one practical conclusion: do not assume the person you called was told anything.

That gap is why the polite version of this feature is also the safe version. If you would be uncomfortable saying to someone afterwards that a system placed the call, that discomfort is telling you something about the call, not about your manners.

The part that actually saves you time

Delegating a call saves five minutes. Losing the answer costs an hour. Most people who try assistant calling discover the second problem within a week: the calls work, and the results scatter across text messages, emails, and memory. This is the same pattern behind every question about how much access to give an assistant, which we walked through in whether to let an assistant read your messages and in the list of privacy questions worth asking before you commit to one. The capability arrives long before the habits that make it useful.

Tase does not place calls for you, and that is a deliberate line rather than a missing feature. What it does is hold the other half: you say what you asked, what came back, and when to chase it, and it lands as a task with a date instead of a note you will never find. The assistant that talks to strangers and the assistant that remembers what happened are two different jobs, and only one of them fails silently when you skip it.