DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to sort and answer your support inbox on a schedule with Dontbemichael

Connect a support mailbox, give it to a team member, and have it sort new mail hourly.

Credentials. The mailbox app password is stored encrypted on your computer, so use an app password with only the access you need and never paste it into a shared file or chat.

Who it is forA shop or service owner whose support@ inbox fills up faster than one person can answer it.

The problemCustomer emails sit unread, and a single shared inbox gives no clear owner for each message.

The outcomeA Customer Support team member that sorts new mail on a clock, answers within your chosen send setting, and tells Michael what needs you.

What you need first

  • A Mac or Windows computer
  • A Claude plan you already have, or an Anthropic API key
  • Your business name, kind of business, owner name and headquarters address
  • An app password for each mailbox you want the team to use

Steps

  1. In Settings, open Connections, then Mailboxes, and add the support mailbox with its app password.
  2. Wait for the login test to pass, which the app runs before it saves the mailbox.
  3. Open the Customer Support team member's Access tab, choose Add a mailbox, pick it, and choose Watch the inbox.
  4. Set Can send, Send on approval or Draft only for that mailbox.
  5. Add a schedule such as Check the support inbox every hour, with a focus area for each run.

Prompt for your agent

Using the repo agentvivekkumar/dontbemichael, connect the support mailbox <support mailbox address> and assign it to the Customer Support team member with Draft only sending. Report how many new messages were sorted in the first run. Verify that the mailbox shows as watched by that team member on its Access tab.

Caveat. The README says Outlook and Microsoft 365 are not supported yet, so this only works for the providers the app lists such as Gmail, iCloud, Yahoo, Zoho or another IMAP mailbox.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page