Draft an account support email

What you can get

Reaches your accounts Creates or changes things in accounts you connect, with your approval.

1. It does

   • Uses only the support context and mailbox you choose to share or connect.
   • Prepares correspondence; no message is sent without your explicit approval.
   • Does not change account details or treat a support reply as confirmation of a completed change.

2. It stops and asks

   • Before sharing context: remove passwords, one-time codes, and unrelated personal information.
   • Before sending: verify the recipient and approve the exact message.
   • After a reply: distinguish what support says from an account change you have independently confirmed.

3. You approve

   • Review and explicitly approve each outgoing message
   • No authorization to change account settings or share credentials

Derived from this task's own brief and steps, not from the source.

Editorial, not from the source

The source case

On 2026-10-08, I retrieved Jim Kennedy Ph.D (@drjimbokennedy)’s original X post. He reports finding an old phone number in his OpenAI account that should not have been there, asking Instinct to handle contacting OpenAI, and allowing it to use his email. He says Instinct showed him drafted emails, an OpenAI reply arrived within 24 hours, and Instinct sought clarification more than twice before giving answers that made him comfortable. The post does not show the correspondence or establish that the phone number was removed. This is one person’s report, not a run reproduced by this directory.

A public report by someone outside this library. Not independently reproduced here.

What you need

Editorial, not from the source

How to try it

Editorial, not from the source

1. State the account issue, what you already know, and what you want support to clarify. Share only the relevant context; omit passwords, one-time codes, and unrelated personal details.
2. Ask for a short draft that separates confirmed facts from questions, and have it show the recipient and exact message before anything is sent.
3. Check the recipient, account identifiers, and wording yourself. Correct any detail that is guessed or unsupported by the material you supplied.
4. Approve the message explicitly before sending. Review each reply and ask for clarification where needed; treat the summary as a report of what support said, not proof that an account change occurred.

Open Instinct to try it. That is the product's own site; this guide is not part of it.

Limits and confirmation points

• The source is a personal account, not a saved email thread: it does not show the drafts, the replies, or whether the old phone number was removed.
• A support reply may be automated, incomplete, or about the wrong account. Verify any claimed correction in the service’s own account settings.
• Do not share passwords or one-time authentication codes. Email access and sending depend on what your own account has connected and authorized.
• Nothing in the report establishes that every support issue can be resolved this way; this page has not independently tested Instinct.

Editorial, not from the source

• Before sharing context: remove passwords, one-time codes, and unrelated personal information.
• Before sending: verify the recipient and approve the exact message.
• After a reply: distinguish what support says from an account change you have independently confirmed.

Editorial, not from the source

The draft includes a detail you did not provide

Remove it and ask for a revised draft that labels unknowns as questions rather than filling them in.

Support replies without answering the main question

Ask for a short list of the unanswered points and approve a focused follow-up.

The reply says a detail was changed

Check the account’s own settings before treating the change as complete.