Instinct is interesting because it puts an action-oriented assistant inside messaging instead of asking users to manage another dashboard. Kyle Balmer demonstrates talking to it through WhatsApp and iMessage, using it to sort priorities, continue projects, prepare bookkeeping, and return only when a decision is needed.
What Instinct Is
Instinct's official site describes a personal assistant that understands what matters to the user, connects to applications and devices, and can be reached by text or phone. It says the service can follow dropped threads, communicate proactively, arrange transport, or book services.
That is a different product category from a chatbot that only returns an answer. The assistant may plan a sequence, inspect connected information, interact with another service, and ask the user only when it reaches a decision or permission boundary. In Balmer's test, that lower-friction messaging interface is the main advantage: the assistant lives where he already communicates.
Evidence boundary: the connected-assistant description comes from Instinct. The WhatsApp, iMessage, project, and bookkeeping workflow details are Balmer's creator test. They do not guarantee identical access, quality, or results for every account.
Watch the Full Walkthrough
Source and credit: Instinct: A Free AI Assistant That Actually Gets Things Done, published by Kyle Balmer | AI with Kyle on 21 September 2026. Balmer states that the video is not sponsored and that he is not affiliated with Instinct.
Choose a Good First Job
The best first task is annoying enough to matter but reversible enough to inspect. Avoid starting with a vague instruction such as "manage my life." Give the assistant a bounded input, expected output, and stopping condition.
| First job | Input | Expected result | Approval boundary |
|---|---|---|---|
| Project triage | A pasted list of open projects. | Keep, pause, or stop recommendations with reasons. | You choose the final status. |
| Priority brief | Today's commitments and deadlines. | A short ranked plan and missing decisions. | No calendar edits without review. |
| Receipt collection | Selected forwarded invoices or a dedicated folder. | A checklist, organized files, and exceptions. | No filing or sending until totals are checked. |
| Option comparison | Clear criteria for an apartment, service, or purchase. | A sourced shortlist with tradeoffs. | You contact, book, or pay. |
| Reply preparation | One email and the outcome you want. | A draft plus any question it cannot answer. | You approve the recipient and message. |
Balmer's own workflow began with accumulated projects and recurring bookkeeping administration. He describes asking Instinct to learn the monthly collection pattern from previous records, locate the relevant invoices, and prepare the next package. That is a sensible recurring workflow only after a supervised run establishes what belongs in the package and how exceptions are handled.
What the Viral Examples Actually Prove
The video shows three third-party reports: Olivia Levine says Instinct pursued contacts to recover US Open footage; Eli Weiss reports a lower FiOS bill; and Tamara Winter describes an apartment search against strict criteria. These examples are useful as task patterns, not controlled evaluations.
- Multi-step persistence: finding the next contact after the obvious route fails.
- Negotiation preparation: gathering plan details and testing available alternatives.
- Recurring search: checking several marketplaces against stable criteria.
- Human handoff: returning a result when judgment, identity, payment, or commitment is required.
Do not generalize the reported savings, turnaround time, or successful apartment search into an expected result. The relevant question is whether the workflow can be defined, observed, and stopped before an unwanted external action.
Use Instinct Files as a Review Surface
Balmer also demonstrates Instinct Files: generated working documents such as lists, itineraries, and comparisons that can be reviewed or shared. This matters because agent work should leave an inspectable artifact. A useful file shows what was considered, what was excluded, which source supports each option, and what still needs approval.
For a project brief, include current status, next action, owner, due date, blockers, and source messages. For bookkeeping, include vendor, document date, amount, currency, destination folder, duplicate status, and any exception. The file should make review faster; it should not hide the steps behind a polished summary.
Climb an Access Ladder, One Step at a Time
| Stage | Access | Useful test | Do not allow yet |
|---|---|---|---|
| 1. Conversation | Only text or voice notes you deliberately send. | Clarify a project and produce a plan. | Account connections. |
| 2. Selected items | Forwarded email, uploaded document, or copied details. | Process one invoice or compare one request. | Whole-inbox browsing. |
| 3. Read access | One connected source needed for the workflow. | Prepare a draft or exception report. | External communication or payment. |
| 4. Draft actions | Create drafts, proposed events, or candidate bookings. | Measure accuracy across repeated runs. | Automatic submission. |
| 5. Narrow execution | Only the approved action type, limit, and destination. | Run a reversible recurring task with logs. | Open-ended authority. |
Balmer notes that a user can forward one email to a private Instinct address instead of connecting the entire inbox. That is a useful least-access pattern. It reduces exposure, although the forwarded message and its attachments are still information provided to the service.
Read the Privacy Controls Before Connecting Accounts
The Instinct privacy policy, revised 26 August 2026, says the assistant may access connected applications, documents, private messages, email, audio, location, credentials, payment information, and health-related information depending on what the user enables. It also states that autonomous features create additional risks, including unintended payments or communications, incorrect output, and misleading instructions from third parties.
The policy says information collected through the service may be used to evaluate, fine-tune, and train its AI models, with an opt-out available in settings. It separately says information received directly from Google Workspace is not used to train or improve AI models. The policy also says disconnecting an integration does not automatically delete information already collected; users must use the relevant workspace or account deletion controls.
A Seven-Day Instinct Pilot
- Day 1: choose one delayed, low-consequence task and define "done."
- Day 2: provide only selected information through chat, a forwarded email, or one document.
- Day 3: inspect factual accuracy, missing context, and whether the result is genuinely useful.
- Day 4: repeat the same task with a new example and record corrections.
- Day 5: test one draft action while retaining final approval.
- Day 6: review connected accounts, training preferences, stored files, and deletion controls.
- Day 7: decide whether to stop, keep the narrow workflow, or expand one permission.
Measure time saved, corrections required, exceptions missed, unwanted actions, and how often the assistant needed clarification. A pleasant conversation is not enough. The pilot succeeds when the output is correct, the access remains proportionate, and the user can see and reverse what happened.
Video Chapters
| Time | Chapter | Time | Chapter |
|---|---|---|---|
| 00:00 | Instinct in WhatsApp | 02:20 | Get an invite |
| 03:32 | How Instinct works | 06:33 | Knowing when to stop talking |
| 07:43 | Projects and bookkeeping | 11:17 | Other user examples |
| 16:20 | Instinct Files | 17:48 | Accounts, data, and privacy |
| 20:55 | Start with less access | 22:07 | Try one job |
Sources and Links
- Kyle Balmer: Instinct - A Free AI Assistant That Actually Gets Things Done
- Instinct official website
- Instinct privacy policy (last revised 26 August 2026)
- Kyle Balmer's Instinct invite page (availability may change)