AI AgentIntermediate15 min read

Shopping, payments and phone calls: safe defaults for a Bot that can act

Why these actions are red by default, defaults for shopping, payments and calls, a brief shape where the Bot prepares and you decide, handling mistakes, and when to leave the features off.

Shopping, payments and phone calls: safe defaults for a Bot that can act

Shopping, Payments and Phone Calls: Safe Defaults for a Bot That Can Act

Looking things up and drafting text are low-stakes. Buying something, paying for it or phoning a stranger in your name are different, because the result lands in the real world and often cannot be taken back. This tutorial is about the safe defaults for those three kinds of action. It covers what is reported about Grok Bot's shopping, payment and calling abilities, why they sit at the top of your permission map, a set of defaults for each, how to brief them so that the Bot prepares and you decide, and what to do when something goes wrong. The tutorial is optional, and a perfectly good setup can skip these features entirely. If you do use them, you will use them with your eyes open.

Difficulty: ★★★☆☆ (best after the permission map and trust lessons)
Tools needed: Grok Bot
Last updated: November 2026

Overview

Most of what a Bot does can be undone. A wrong summary can be corrected. A bad draft can be deleted. A mistaken file move can be reversed if you kept a list. Because of that, the habits in this path, such as checking, evidence and moving up the trust ladder, can be fairly relaxed for low-risk work.

Three kinds of action break that pattern. Spending money takes it out of your account. Paying involves your payment details and often cannot be reversed without effort. Phoning someone puts your voice, or a voice speaking for you, in front of another person, who may not know it is a machine, and who may act on what they hear. None of these is easy to take back, and each can affect other people as well as you.

The Grok Bot material around the November updates reports that the Bot can search for products through to checkout, apply promo codes, pay with Link, and place outbound phone calls. These reports come from Matt Palmer's updates, as repeated by news sites. They are reported, not confirmed, as of 14 November 2026, so confirm in the app, and for your plan, that a feature exists before you rely on it. This tutorial does not need any of them to exist. It is about what to do if they do.

The central idea is the one you have met throughout this path: the Bot prepares and you decide. For shopping, that means it finds, compares and fills a basket, and you press pay. For payments, it means you never hand over card details in chat, and you approve each charge. For phone calls, it means you write the script, hear the plan and think about who is on the other end.

The tutorial has seven steps. You place these actions on your permission map. You set defaults for shopping. You set defaults for payments. You set defaults for calls. You write the briefs. You handle the consequences, such as refunds and mistakes. And you decide when not to use these features at all.

Who This Is Useful For

  • People curious about letting a Bot shop, pay or call on their behalf.
  • Anyone who has seen these features mentioned and wants to know how to approach them safely.
  • People responsible for a team's Bots, who need a clear default.
  • What You Will Learn

  • Why shopping, payments and calls belong near the top of your permission map.
  • Safe defaults for each, and how to write them into a brief.
  • How to keep card and account details out of the Bot.
  • How to think about calls as something with another person on the line.
  • How to handle mistakes, and when to leave these features off.
  • What You Need

    1. Grok Bot, and for these features a plan and version that offers them. Confirm in the app.
    2. Your permission map and job cards from the earlier lessons.
    3. A willingness to start small: a cheap, low-stakes purchase or an easy call.
    4. About thirty minutes to write your defaults.

    News report on the November Grok Bot updates

    A news report on the updates Matt Palmer described, including calls and shopping. Reported, not official, so confirm in the app.

    webpronews.com
    Grok Bot

    The AI teammate from SpaceXAI. The official page has downloads and current plans.

    x.ai

    Reported, as of 14 November 2026. The shopping, payment and calling features come from Matt Palmer's updates as repeated by a news site, not from an official page I could confirm. Whether they exist, and what they do, depends on your plan and version. This tutorial gives no price, limit or screen name, and it is not financial advice. Treat everything about what the features can do as something to verify in the app.

    Step 1 — Place these actions on your permission map

    Go back to the permission map from the earlier lesson and run these three actions through the four-question risk test.

    QuestionShoppingPayingCalling
    Can it be undone?Sometimes, via returnsRarely, and with effortNo. Words said cannot be unsaid
    Who is affected?You, and the sellerYou, your accountAnother person, who may not know it is a Bot
    What does a mistake cost?Money, timeMoney, possibly moreReputation, a relationship, a legal issue
    Would I notice if it went wrong?Only if I look at the orderOnly if I see the statementOnly if I hear a recording

    The result is clear. Under the rule from earlier, with two or more worries, or money, confidential material or outside commitments involved, an action is red, at least to start. All three of these are red by default.

    Red does not mean never. It means the Bot may not do it alone. In practice, the safe configuration for all three is the yellow version of the same thing: the Bot prepares and you take the final step.


    Step 2 — Defaults for shopping

    Reports say the Bot can search for products through to checkout and apply promo codes. Use that capability for the part that is safe, and keep the part that is not.

    Compare, do not buy. Start with "find the best three and list prices". A comparison is reading. It carries no risk to your money.

    Ask before paying. Always: "show me the cart before you pay." The cart is where you see the item, size, colour, delivery address, price, shipping and any extras that crept in.

    Set a spending limit in the brief. A clear ceiling, written in plain words, that the Bot may not exceed.

    Check the seller. Ask the Bot to say where it found the product, who the seller is and what the return policy says. Open the page yourself. A product that looks right from an unknown seller is a classic trap.

    Use the Bot to prepare, then place the order yourself, at least for the first dozen purchases.

    A brief that follows these defaults:

    Role: Shopping helper.
    Task: Find three options for a desk lamp, warm light, under a stated budget. For each: product, seller, price with shipping, delivery date, return policy, and a link to the page you used.
    Limits: Do not buy anything. Do not add anything to a cart unless I ask. Do not sign in anywhere. Do not apply codes unless I ask. If a price or detail is not on the page, say "not stated".
    Report: A comparison table, your recommendation with reasons, and three lines: what I did, what I found, what I am unsure about.

    When you do move to "fill the cart", the limits change to: "Add the chosen item to a cart. Stop at the page before payment, and show me the cart contents, the total and the delivery address."

    Step 3 — Defaults for payments

    The reports mention paying with Link. Whatever payment methods exist in your version, the safe defaults do not change.

    1. Never type card numbers into the chat. Not in a brief, not in a message, not "just this once". Anything you type in a chat can be stored, and may be seen again.
    2. Never put passwords or one-time codes into a brief. If a payment needs verification, you do that step yourself, on the provider's own page.
    3. You press the final button. However the checkout works, the last step, pay, belongs to a person.
    4. Prefer a payment method with a limit. A card or wallet with a low balance or a spending cap has a smaller worst case than your main account. That is a choice you make with your bank or provider, not with the Bot.
    5. Check the statement afterwards. For the first month, look at every charge that follows a Bot-prepared purchase.
    6. No recurring payments. Do not let a Bot set up subscriptions, automatic renewals or standing orders. Those continue after you forget.

    Leave approvals and one-time codes to yourself, always. If a tool asks you to hand those to a Bot, decline.

    If a feature lets the Bot pay by itself within a limit, treat it as the top rung of the trust ladder, and the least likely to be justified. Be prepared to keep it off.

    Step 4 — Defaults for calls

    Reports say the Bot can place outbound phone calls. Calls are different from shopping and payments because another person is part of the transaction.

    Say who you are calling for. A call made by a Bot on your behalf should say so plainly. The person on the other end has a right to know they are speaking with an automated assistant, and many places have rules about it.

    Follow the rules where you live. Rules on automated calls, calling lists, recording and consent differ by country and by region. Check yours before you try it. If you are unsure, do not.

    Keep calls short and low-stakes. A good first call is simple and factual: confirm opening hours, ask whether an item is in stock, check an appointment time. A bad first call is anything involving a complaint, a negotiation, a dispute or someone upset.

    Write the script. Decide what the Bot will say, what it will ask and what it will do if the person asks something else. The safest answer to an unexpected question is "I will pass that on" and ending the call politely.

    Review afterwards. If a recording or transcript is available, read it. Check what was agreed, if anything.

    Do not use a Bot for a sensitive call. A medical, legal, financial or emotional matter should be a person calling. So should anything where the other party might feel deceived or hurt.

    Role: Call helper.
    Task: Call the shop at the number I have given you and ask: are you open on Sunday, and is the red model in stock in size 42?
    Limits: State at the start that you are an automated assistant calling for me. Ask only those two questions. Do not agree to anything, give any personal or payment details, or book anything. If asked something else, say you will pass it on and end the call politely.
    Report: What they said, in their words where possible, and three lines: what I did, what I found, what I am unsure about.

    Step 5 — Brief them so the Bot prepares and you decide

    Across all three kinds of action, the briefs share a shape. Use it as your template.

    1. The task is preparation: compare, fill, draft the script, list the questions.
    2. A hard stop before the irreversible step: "stop before payment", "do not agree", "do not book".
    3. A spending or scope limit, in plain numbers or words.
    4. A ban on details you do not want shared: card numbers, passwords, addresses, personal data.
    5. A report with "what I am unsure about".
    6. A stop rule: "if anything is unclear, or the price changes, or the seller asks for more information, stop and tell me."

    If the brief passes those six checks, the worst case is a bad suggestion, not a bad purchase.

    Step 6 — When something goes wrong

    Even with defaults, mistakes happen. Know your response in advance.

    A wrong purchase. Check the seller's return policy first. Contact the seller yourself. If a payment was made that you did not approve, contact your bank or provider quickly, and tell them what happened. Then fix the brief and the permission that allowed it.

    An unexpected charge. Look at the statement. Pause the Bot's access to any payment method, and review what it was allowed to do.

    A call that went badly. If the other person was upset or confused, a short follow-up from you, a human, is often the best repair. Review the transcript, and tighten the script or stop using the feature for that kind of call.

    A security worry. If card details or a code were ever typed where they should not have been, treat them as exposed. Contact your provider, and replace the card if they advise it.

    Afterwards, write one line in your notes: what happened, what you changed. A mistake on a small purchase is cheap. Missing the lesson is expensive.

    Step 7 — When not to use these features at all

    A good setup does not need every feature. Leave these off when:

  • Your plan or region does not clearly offer them, and you cannot confirm the details in the app.
  • You cannot yet explain how you would notice a mistake.
  • The stakes are high and the saving is small. Doing a purchase yourself costs five minutes, while a wrong one costs an afternoon.
  • You share the Bot with others. A shared Bot that can pay or call is a much bigger risk. A team should decide on this as a group, and probably leave it off.
  • You are not comfortable. That is a good enough reason by itself.
  • You lose very little by keeping these three on the red list. Finding, comparing, drafting and summarising are where Bots save most of the time, and none of them requires the Bot to spend, pay or phone.

    Worked Example: Elena buys a lamp, and skips the call

    Elena wants a desk lamp. She has read about shopping features and decides to try, with her defaults written.

    The brief asks for three options under a budget, each with seller, price including shipping, delivery date, return policy and link. It says: do not buy, do not sign in. The Bot returns a table. She opens all three links. One seller has no return policy, and she drops it. The second matches. She asks the Bot to fill a cart with the second option and stop before payment.

    The cart shows the right lamp, but shipping is higher than the table said, and a pre-ticked extra warranty has been added. She would not have seen either if the Bot had paid. She removes the extra, notes the price difference in her checks, and places the order herself on the provider's own page.

    The statement. She checks it on delivery day. It matches.

    The call. She considers asking the Bot to phone the shop about a replacement bulb. She applies the three tests: could she notice a mistake, is it low-stakes, and does the other person know it is a machine. The third is the problem, since the shop is a small family business. She decides to call herself, which takes two minutes.

    She writes one line in her notes: "Bot finds and compares, I buy. Calls: me." That is her default for now. She will review it in a month.

    Common Mistakes to Avoid

    Three habits cause most of the harm with these actions.

    Mistake #1: Letting the Bot pay, or typing payment details into the chat. A charge made without your approval, or a card number stored where you cannot control it, is hard to reverse. Fix: the Bot compares and fills the cart, you press pay, you never type card numbers, passwords or one-time codes into a brief, and you check the statement.

    Mistake #2: Starting with a high-stakes or sensitive call. A Bot on a complaint, a negotiation or an emotional matter can hurt a relationship in two minutes. Fix: start with a short factual call, write the script and the limits, have the Bot say it is automated, follow the rules where you live, and keep sensitive calls human.

    Mistake #3: Assuming the features exist, or work as reported. The reports come from social posts and news sites, and plans and regions differ. Fix: confirm in the app that a feature exists for your plan, date everything you note about it, and keep it off until you can explain how you would notice a mistake.

    Going Further

    Practise the stop point. Run the shopping brief on three cheap items without ever letting it pay. You are testing whether the Bot reliably stops at the cart.

    Write a one-page team policy. If a team shares Bots, write in a paragraph what Bots may and may not do about money and calls. Most teams will say: prepare, never pay, never call.

    Keep a receipt log. For any purchase involving a Bot, one line: what, from whom, how much and whether it matched the brief. After a few months you will know how much to trust it.

    What to learn next. This closes the module on guardrails. If you want to go further, the optional lessons cover common mistakes and fixes, and case studies of what other people do with agents. And the quest on auditing a Bot's report puts the checking habits from this module to work.

    Key Takeaways

    In this tutorial you learned:

  • Shopping, payments and calls are red by default. They are hard to undo, affect other people and are hard to notice when they go wrong.
  • The Bot prepares and you decide. It finds, compares, fills a cart and drafts a script. You pay, and you decide what to say.
  • Shopping: compare, do not buy, ask before paying, set a limit, check the seller.
  • Payments: never type card numbers or codes into chat, press the final button yourself, prefer a limited payment method, check the statement and avoid recurring payments.
  • Calls: the Bot should say it is automated, follow the rules where you live, keep it short and low-stakes, write the script, and keep sensitive calls human.
  • Brief with a hard stop before the irreversible step. Plus a limit, a ban on sensitive details, a report and a stop rule.
  • Know your response to mistakes before they happen.
  • These features are optional and reported. Confirm in the app, and leave them off when in doubt.
  • Before you move on, a challenge. Write your defaults for shopping, payments and calls on one page, and mark each red. Then try only the safest piece: ask your Bot to compare three options for a cheap item, with sources, and not to buy anything. Open every link, and note what you learned.

    Learn AI, after work

    Track your progress, earn XP, and unlock more free tutorials in the AfterWork Academy app.

    Open this tutorial in the app

    More AI tutorials