Instinct AI assistant: features, pricing, and access

What is Instinct?

Instinct's official site describes a personal assistant that can use connected apps and devices through texts or calls. The homepage now directs visitors to an official sign-in page; eligibility and onboarding need to be confirmed there.

For someone comparing assistants, the useful question is how a request becomes a completed task. An answer might tell you what to do next. A delegated task also needs the right account, permission to act, a result you can inspect, and a way to recover when something changes. Those are the parts to examine during onboarding.

How to get started with Instinct

On September 20, 2026, the homepage linked to app.instinct.com/login. It no longer displayed the waitlist or member-invitation wording recorded in our earlier review. Treat a sign-in screen as the start of an access process: reaching it is not evidence that a new account can immediately use the assistant. This guide cannot determine an individual account's eligibility or position in a queue.

Prepare a short description of what you want to delegate before you connect accounts. For example: ‘I want help identifying personal follow-ups that need a reply this week.’ That is specific enough to discuss required access, yet leaves you room to approve the actual messages yourself.

Keep setup details tied to the official account flow. An invitation should help you reach that flow; it should not require sending someone your email password, payment credentials, or a sign-in code. If an access page or message is unclear, return to the official domain and use its support route.

Pricing, phone number, and iMessage: what remains unconfirmed

No subscription price or universal assistant number was published on the reviewed homepage. It did not name the assistant's messaging transport. Textanai therefore uses a general Text label. Ask which channel and phone region your account supports, and inspect the price presented before accepting a paid plan.

Instinct's terms describe possible paid features and separately document SMS sign-in codes and waitlist messages. An authentication text does not establish which transport powers an ongoing assistant conversation.

Budget for the whole workflow when you compare products. A subscription, a usage allowance, and a purchase arranged through another service are different costs. Before authorizing a task, decide which of those costs you are accepting and what amount should trigger another confirmation. A missing public price is a question to resolve, not a reason to assume the product is free.

Read the data controls before connecting your accounts

The August 26 privacy policy describes access to linked Google Workspace services, including Gmail, Calendar, Drive, Docs, Sheets, Slides, and Tasks. It distinguishes Google Workspace API data, which it says is not used to train or improve models, from other information. For other information, a training opt-out applies going forward, with a safety-review exception.

The policy also distinguishes disconnecting an integration from deleting information already indexed from it. It points users to the Workspace area for deletion controls. Review those settings while setting up access, so you know where they are before you need them.

Write down the smallest information set that would support your first task. A calendar question may require availability; it does not automatically require your entire document collection. If the permission screen bundles more access than you expected, check whether that scope is necessary for your planned use. Evaluate the actual controls offered to your account rather than assuming a conversational request changes an underlying permission.

A useful first-week plan if you receive access

Start with a task whose result you can verify quickly: a list of outstanding personal commitments, a proposed schedule, or a draft reply. Give the assistant a deadline, an explicit boundary on what it may change, and a definition of done. Review the result in the source app before increasing the scope.

Track practical friction as well as success. Count how often you have to repeat context, correct a name or time, or explain that an action was premature. Keep tasks small enough that these corrections teach you something. A polished conversation is useful, but the decision to delegate more should come from accurate outcomes and understandable controls.

• Day one: establish one task and the account access it needs.
• Next: try a correction, a changed deadline, and an instruction to stop.
• At the end of the week: keep workflows that saved effort after review time is included.

What this guide verifies

Textanai rechecked the official product page, privacy policy, terms, and sign-in destination on September 20, 2026. We did not test an Instinct account. Capability descriptions above are attributed to the publisher; the setup plan is our editorial guidance. Consult the linked sources again when you join, because access and account terms can change.