Support inbox and Stripe sales alerts

Add as many mailboxes as you like in a project's settings, such as info, support and sales, each marked general, sales or support. Google, Microsoft, Yahoo, iCloud, Zoho and Fastmail have presets, or you write the IMAP and SMTP servers yourself. Both servers are tried before a mailbox is kept, and its password stays in the Windows Credential Manager or the Mac Keychain. Built, and tried so far only against a test mail server.

The mail of every project in one column of its own, split with sales above and support below or mixed, and ordered by priority or by date. Each row shows a priority percent and the reason in your language. Each project card shows how many sales and support emails are still unanswered, and a click shows only that project's mail. Built, and seen so far only with demo mail in a trial studio.

Each email is read once by Claude Code with your own subscription, or by Codex where Claude Code is not installed. The model gets no tools and keeps no session, and it gives the email a kind, a sales or support tag, an urgency and a one-line reason. Text a reader cannot see is removed first, and a mailbox with AI reading switched off is never sent to a model. Built, and the real Claude Code has not yet read real mail.

Promotions, notices and spam are moved to a folder named AigoPilot on the mail server, never deleted, and come back with one press of “a person sent this”. One model decides (Claude Code, or Codex where Claude Code is not installed), and when AI reading is switched off a rule on the message headers decides instead. Built, and not yet tried on a real mail server.

Each email shows the original, a translation into your language and a suggested reply that draws on what the product does and how you have answered before. You edit it and send it from the same place.

An answer always goes out from the mailbox the email came to, never from another, and its copy in the sent folder is checked afterwards. Built, and proven so far only against a test mail server.

A mailbox that fails two tries in a row, or stays down for ten minutes, turns red with the server's own words and raises an alert, so you know before your emails start bouncing. Tested, and not yet seen on a real mailbox.

A customer emails your product's support address to say something is broken. AigoPilot can take that report to a coding session in the right project and bring the fix back as a reply in the customer's own language. Email comes first. Telegram and the chat on your own website will follow.

Before a report gets anywhere near a coding agent, an AI reads it against a long checklist. It looks for text written to give an AI orders, requests for keys, passwords or customer data, requests to run a command, open a link, push, deploy or delete something, anything that goes beyond fixing the reported fault (a backdoor, a change to payments or licences), hidden or encoded text, risky attachments and the usual tricks of social engineering. You get a verdict of clean, suspicious or hostile, with every finding quoted from the email. The agent never takes the customer's words as instructions. It gets the bug restated as plain facts, and the customer's text only as data. A report marked hostile needs a second, explicit confirmation from you before anything can start.

Then it is your call:

• The report shows up with a “Fix it” button. You can add a note of your own, for example where you think the fault is, and it goes to the session together with the customer's problem.
• The agent is the one you last used in that project, or the one you use most there: Claude Code, Codex or Grok. You can pick another.
• The model and the effort are chosen by AI from how big and how hard the problem looks. You can change both.
• One click opens the session in that project, on whichever of your computers the project lives. It reproduces the fault, fixes it and runs the tests. Plan mode is on by default, so you approve the plan before any code changes. The session never pushes, deploys or sends anything by itself.

When the fix is done, AigoPilot drafts a reply to the customer in the language they wrote in, based on what actually changed. You read it, edit it if you want and send it. If you have set a date for the project's next update, the reply says the fix will be out around then. If not, it says the fix comes with the next update.

When several customers report the same fault, their reports go into one session. The small differences between them are merged into one complete description, so the agent sees every detail once. Each customer still gets a reply of their own, in their own language.

Nothing starts without your click, so no session opens and no tokens are spent behind your back.

Support to fix is part of AigoPilot itself and comes with every plan at no extra cost, so it is not one of the paid plugins. Being built now.

Keep leads in one list, follow up on time and move each conversation toward a sale.

New sales, revenue and balance for each product, read with a restricted Stripe key and compared day by day, week by week and month by month. Several products and several Stripe accounts are supported.

A strong alert when sales drop, a softer one when they grow, and a warning for patterns that look wrong. A restricted Stripe account or a card-testing attack alerts you even during quiet hours.

When a customer's payment fails, a follow-up email is drafted for you to check and send.