Guide
Instinct AI problems: what users report going wrong
This page collects Instinct AI problems that users have described in their own public posts, sorted by the kind of thing that went wrong. The site has no connection to Instinct, and we haven't reproduced any of these failures ourselves. Each report links to the original post, says what it leaves out, and sits next to checks you can run so the same thing is less likely to catch you. Nothing here tells you how often Instinct fails; it tells you where people have been caught out so far. Checked against the linked posts as of 16 October 2026.
Checked against the official pages listed at the end, 2026-10-16. Instinct Tasks is an independent guide, not Instinct.
Instinct AI problems at a glance
The most costly reports are about money that never moved. Two users say a payment failed and Instinct didn't tell them, and one of them came home to the power off. Other posts describe sites that push the agent out or ask for something only a person can supply, a Monday reminder that didn't arrive, and answers that came back empty or too sure of themselves. The common thread is that the user found out late, from the outside world rather than from Instinct.
This page sticks to things not working. For what Instinct can access, its training default and how it handled a reported data leak, read our Instinct AI review.
How we collected these
We searched public posts on X for people describing their own experience with Instinct, the assistant at instinct.com, and kept the ones where the writer says what they asked for and what happened. That left nine posts published between 21 August and 8 October 2026. We dropped posts that retell someone else's story, and posts about other products that share the name.
Treat this as a small, self-selected sample. People post when something goes badly or very well, so a list like this can't measure a failure rate, and none of these accounts has been checked against Instinct's own records. Where a post gives a cause, we say whose explanation it is. Where it doesn't, we say the cause is unknown rather than guess. We found no public response from Instinct to any of the reports on this page.
Payments that failed without a warning
@kishansripada posted on 8 October that they came home to their power shut off "because my instinct forgot to pay my electricity bill." That's the whole report. It doesn't say what Instinct was told to do, whether it had the utility login, or why the payment didn't go through, so it doesn't prove Instinct was at fault rather than the payment method or the utility's system.
@benspringwater wrote on 28 September that they used Instinct to order bagels for their son's birthday, and the store hadn't received the order when they arrived. In their words, "my credit card failed (issue with agentic purchases) and Instinct didn't report it to me." They say they were late for the party and switched assistants for the time being. The post names no shop or amount and shows no decline message, and whether Instinct ever saw an error is unknown.
@terryangelos described on 21 August a bike helmet purchase that stalled at checkout: the merchant used ShopPay, which recognised their email and wanted confirmation, and the agent "was stuck in a loop and didn’t know how to ask for verification." No order went through. They also say the agent vault "stored my CVV against card-network rules"; we haven't checked that claim, and the post doesn't show the vault.
Why it happens: the bagel post blames card failures on agentic purchases in general, and the helmet post blames a confirmation step the agent couldn't hand back to the user. Neither is confirmed by Instinct, and the electricity post gives no cause at all.
- Our suggestion: ask for a confirmation number or receipt in the same reply as the purchase, and treat "done" without one as not done.
- Our suggestion: for anything with a deadline (a bill, a pickup, a party order), ask Instinct to message you if a payment fails, and check the merchant or bank app yourself the day before.
- Our suggestion: keep autopay with the utility for essential bills instead of making an agent the only thing standing between you and a shut-off.
- Our suggestion: if a checkout uses ShopPay or a similar saved-wallet login, expect a code or prompt that only you can approve, and tell Instinct up front to stop and ask you when that happens.
Sites that block the agent or need a human
Some sites don't let an agent finish. @Graham_Tonkin posted on 2 October that Instinct tried to set up a glass repair quote and appointment with Safelite, "got booted and denied from the website" and asked him to carry on with Safelite's own bot. @kuap wrote on 21 September that Instinct struggled with a refund form; when they stepped in, the instructions asked for two photos but the form allowed one attachment, which they called a "Sort of anti-agentic captcha."
@emilylai listed, on 16 September, a run of moments when testing several assistants was "more annoying than helpful". Two involve sign-up walls: Instinct sent them "a captcha code to do myself", and it set up accounts for them, then, when it "can’t get past verification", left them to reset the password and add it to the vault by hand. The post doesn't name the services, so we can't tell which checks stopped it.
Why it happens: the posts point at the sites (a bot block, a form that contradicts its own instructions, captchas and verification steps). Whether a given site blocks Instinct on purpose isn't stated in any of them.
- Our suggestion: for bookings with sites known to push bots away, ask Instinct to find the slot and the details, then book it yourself. If the business takes bookings by phone, you can also have it call instead.
- Our suggestion: when it hands you a captcha or a verification code, that's the expected stopping point; finish that step yourself and tell it to carry on.
- Our suggestion: after it creates an account, log in yourself once and confirm the password and recovery email are ones you control.
A reminder that didn't arrive, then a claim that it did
@Anubhatps posted on 3 October that they asked Instinct to remind them on Monday to pay some bills. "It did not do anything for 5 days!" When they asked why, they say it claimed it had sent an iMessage, which they call a lie. The post had a screenshot we couldn't capture, so we don't have Instinct's exact reply, and it doesn't say how the reminder was meant to reach them or whether any bill ended up late.
Why it happens: unknown. The post doesn't give a cause, and "lied" is the author's word for a reply that didn't match what they saw.
- Our suggestion: set a test reminder a few minutes out before you rely on one, so you know which channel it uses and that it arrives.
- Our suggestion: for anything that matters, keep a second alarm in your own calendar or phone. Get reminded before a registration renewal is a low-stakes way to try reminders first.
- Our suggestion: if it says it sent something, look for it in the app it named (Messages, your inbox) rather than taking the reply as proof.
Answers that came back empty or too sure
@AnnikaSays asked Instinct, with Gmail connected and no other direction, "What did I do in Chiang Mai and what did I like?" On 21 August they reported that Instinct "couldn't find anything." They add that the trip was eight years ago and they knew it was a long shot, and they call the whole test n=1. It says little about how Instinct handles recent mail.
@kaushikimmadi wrote on 30 September that Instinct "failed to efficiently do a simple task for me: get me from point A to point B", with the texts attached. We captured only the opening of the post, not the screenshots or the write-up it introduces, so we can't say what the wrong turn was.
The same list from @emilylai includes Instinct "being over confident in it’s answers when all it did was stop at the first listicle on top of google", then calling the first item on that list the best. Another item on that list, calendar events mixed up across time zones, happened with three assistants in one Slack channel, so it can't be pinned on Instinct alone.
Why it happens: none of these posts gives a cause.
- Our suggestion: for old email, give it a name, a sender or a rough year to search for instead of an open question.
- Our suggestion: when it recommends "the best" of anything, ask where that came from and how many sources it compared.
- Our suggestion: for directions, check the route in a maps app before you leave. Instinct's answer is a starting point, not navigation.
Doing more than you asked with your email and card
Two posts describe Instinct reaching further than the user expected. @emilylai lists it "being overly aggressive with scanning my emails unprompted", without saying what it read or what it did with it. And @terryangelos, as noted above, says the agent vault stored their card's CVV. Neither post shows harm coming from it, and neither one is confirmed by Instinct.
- Our suggestion: connect Gmail only when a task needs it, and say in the request which messages it may open.
- Our suggestion: ask Instinct what card details it has saved, and remove what you don't want kept. Our how-to guide covers wording that puts approval points into a request.
- Our suggestion: if you want to know what it holds about you, submit a data access request.
Low-stakes tasks to test it on first
Questions about Instinct AI problems
Why is Instinct AI not working for me?
We can't diagnose a single account, and Instinct publishes no status page we could find. In the posts we collected, the failures came from a few places: payments that failed quietly, sites that blocked the agent or asked for a captcha or verification code, a reminder that didn't arrive, and searches that came back empty. If it stalls, check whether it's waiting on a step only you can do.
Does Instinct tell you when a payment fails?
Not always, by two users' accounts. One says a card failed on a bagel order and Instinct didn't report it; another came home to the power off after a bill went unpaid. We haven't reproduced either. Ask for a receipt or confirmation number with every purchase.
Can Instinct make up that it did something?
One user says Instinct didn't send a Monday reminder and then claimed it had sent an iMessage. The post doesn't show why. Check the app it names instead of trusting the reply.
Why do some websites block Instinct?
Users describe Safelite's site booting the agent, a refund form that contradicted its own instructions, and captchas and verification steps it handed back. The posts don't say whether the sites block Instinct on purpose, and we found no statement from Instinct about it.
Are these problems common?
We can't say. This is a small set of public posts from people who chose to write about a bad experience, and we haven't tested any of them. It shows what can go wrong, not how often.
What should I do when Instinct makes a mistake?
Fix the real-world part first: call the shop, pay the bill, rebook. Then tell Instinct what went wrong and ask it to confirm with a receipt or a link next time. For anything with a deadline, keep your own backup reminder.
Sources
- @kishansripada on X — power shut off after Instinct didn't pay an electricity bill; 2026-10-08; first-hand post, not reproduced
- @Anubhatps on X — Monday bill reminder never came, then Instinct said it had sent an iMessage; 2026-10-03; first-hand post, not reproduced
- @kaushikimmadi on X — failed to give efficient point A to point B directions; 2026-09-30; first-hand post, not reproduced
- @benspringwater on X — card failed on a birthday bagel order and Instinct didn't report it; 2026-09-28; first-hand post, not reproduced
- @Graham_Tonkin on X — Safelite's site booted the agent from a glass repair booking; 2026-10-02; first-hand post, not reproduced
- @kuap on X — refund form wanted two photos but allowed one attachment; 2026-09-21; first-hand post, not reproduced
- @emilylai on X — captcha handed back, account verification, unprompted email scanning, overconfident answer; 2026-09-16; first-hand post, not reproduced
- @terryangelos on X — bike helmet checkout stuck in a ShopPay verification loop; CVV stored in vault; 2026-08-21; first-hand post, not reproduced
- @AnnikaSays on X — couldn't find an eight-year-old trip in Gmail; 2026-08-21; first-hand post, not reproduced