Most owners I talk to spend the first hour of the day doing a job they'd fire anyone else for doing that slowly. Open the inbox. Skim. Star something. Archive four newsletters. Forget to answer the one lead that actually mattered. Repeat at lunch.
It's also the easiest hour in your business to hand to AI right now. Over the past couple of weeks the tools finally got good enough to do it.
Fluxmail showed up on Product Hunt as "self hosted email for AI agents and applications." It hooks your real Gmail, Outlook or IMAP mailbox up to Claude, ChatGPT or anything else that speaks MCP. Inbox Zero relaunched as a full email app and took the number one spot on Product Hunt on October 18. And Littlebird's October 23 update lets a routine run "when something happens in Gmail, including when you send an email."
So the pieces exist. The danger is giving it full access on day one. Below is how I'd set it up so it saves you the hour without emailing your biggest client something weird at 11 p.m.
The permission ladder
Every inbox tool now asks some version of the same question: what is this thing allowed to do? There are really only four rungs, and you climb them one at a time.
Rung one: read. It can search and read mail. It can't change anything. This is where everything starts, and honestly it's where a lot of the value already lives. "What did the roofing supplier say about the October invoice?" is a read job.
Rung two: organize. It can label, archive, star and move mail. Mistakes here are annoying but reversible. A misfiled email is still in your account.
Rung three: draft. It writes replies and leaves them in your drafts folder. You read, edit and send. This is the rung that saves the most time per week.
Rung four: send. It sends without you. This one stays off for two weeks minimum, and for anything client facing I'd leave it off for good.
Fluxmail is built around this idea. Its docs describe full access, read and write, and read only profiles, and connections set up without permission options default to read only. You can also limit a client to specific mailboxes. Use that. Give the AI your sales@ inbox, not your personal one where your accountant and your kid's school both live.
My rule: an agent climbs one rung per week, and only if it made zero mistakes on the rung below. I don't care how smart it looked on Tuesday.
Sort the mail into four piles
Before you install anything, decide where mail goes. Every small business inbox I've ever looked at breaks into the same four piles.
Money. Invoices, receipts, payment notices, bank alerts, payout reports.
Leads and customers. Anyone asking about buying, booking, pricing, or complaining.
Vendors and partners. Suppliers, contractors, your software companies, the agency you hired.
Noise. Newsletters you never read, cold pitches, notifications, "just following up" from someone you've never met.
Pile four is usually 50 percent or more of the volume. Pile two is usually under 10 percent and it's where all the money is. You're building this to shrink four and protect two.
Write the rules in plain English
Inbox Zero takes rules the way you'd explain them to an assistant. Their own examples include forwarding receipts to your accountant and labeling them processed, and archiving newsletters after a week unless they're starred. It works with Gmail, including Google Workspace, and Outlook. The email app itself is free, and AI plans start at $20 a month or $18 a month billed annually, per their pricing page. It's open source too, so if you've got a technical person who likes self hosting, that's on the table.
Here's the rule set I'd paste in, one rule at a time. Swap the brackets.
Rule 1, Money: If an email contains an invoice, receipt, bill, statement or payment confirmation, label it "Finance", archive it, and forward it to [[email protected]]. Never reply to these. Rule 2, Leads: If someone who isn't already a customer asks about pricing, availability, a quote, booking or a service we offer, label it "Lead", star it, and draft a reply using the Lead Reply guidelines. Don't send. Rule 3, Unhappy customers: If a customer mentions a refund, a complaint, a cancellation, "disappointed", or a deadline we missed, label it "Urgent Customer" and leave it in the inbox. Don't draft a reply. I'll handle these myself. Rule 4, Vendors: If the sender is a supplier, contractor or software company we pay, label it "Vendor" and archive it unless it mentions a price change, a contract, a renewal or a delivery problem. Those stay in the inbox. Rule 5, Noise: Newsletters, promotions and notifications get labeled "Read Later" and archived. Cold sales pitches from people I've never emailed get labeled "Cold" and archived. |
Look at rule 3. The AI doesn't touch angry customers, and I'd keep it that way even if the tech were perfect. Customers can tell when an apology came from a machine, and an angry one is already halfway out the door.
Then give the drafter its guidelines. Inbox Zero says it drafts in your voice based on your past mail and lets you add context like pricing and policies. Fill that context in properly, because a draft with the wrong price is worse than no draft.
Lead Reply guidelines for [Company Name]: Answer the question they asked in the first sentence. If they asked for a price and we have a set price, give it: [list your standard prices]. If the job needs a quote, say so and offer two specific times for a 15 minute call this week: [your booking link]. Keep it under 120 words. No "I hope this email finds you well." No exclamation points. Never promise a date, a discount or a scope we haven't confirmed in writing. If unsure, write [CHECK] in the draft so I see it. Sign off as [Your Name], with my direct phone number: [number]. |
Last thing in Inbox Zero: run the bulk unsubscriber on day one. It shows every sender you're subscribed to with how often they email and how often you open them. Anything you opened less than 10 percent of the time goes. It's oddly satisfying.
FROM THE AI NEWSROOM The AI Workflow Blueprint The exact systems behind everything in this issue. The audit sheets, the routing logic, the templates and the review cadences, built out step by step so you can copy them straight into your own stack. One time, forty seven dollars. Get the Blueprint for $47 |
Let Claude or ChatGPT read the whole mailbox
Rules handle what's coming in. The second job is asking questions about what's already there, and that's where Fluxmail fits.
Fluxmail gives agents a long list of verbs: search, read, draft, reply, forward, send, schedule, archive, move, label. It covers Gmail, Google Workspace, Microsoft 365, Outlook.com and plain IMAP. The self hosted Personal plan is free for one member and three mailboxes, and there's a hosted cloud version if you don't want to run anything yourself. The maker says email bodies aren't stored and metadata is encrypted at rest. That's their claim, so read their policy before you connect a mailbox with client data in it.
The install is a terminal job (npm install -g fluxmail, then fluxmail setup), so if the words "Node.js 22" scare you, hand this part to whoever set up your website. Once it's connected to Claude with the read only profile, you can start asking it real questions about your business.
Search my inbox for every invoice or receipt from September. Make a table with vendor, date, amount and whether it's already been forwarded to [[email protected]]. Flag anything that looks like a duplicate charge. Find every email I sent in the last 14 days that asked a question or sent a quote and hasn't gotten a reply. List them oldest first with the recipient, subject and one line on what I asked. Pull every email from [Vendor Name] in the last 6 months that mentions price, rate, surcharge or increase. Summarize what changed and when. |
If you only run one of these, run the second. Most small businesses I see have plenty of leads and lousy follow up, and the proof is sitting right there in the sent folder.
Run those three in Claude or ChatGPT once a week, same morning, and save the answers in one doc. After a month you'll have a running record of who owes you a reply and which vendors keep creeping their prices up. Nobody on your team is keeping that list today. I'd bet on it.
Log every lead reply in HighLevel automatically
Here's where most setups leak. A lead replies to your email, you answer it, and the CRM never hears about it. Three weeks later nobody knows whether that person is warm, cold or already a customer.
This takes about 30 minutes in Make.com, and it plays nicely with the "Lead" label from rule 2.
Trigger: Gmail, Watch Emails. Set it to watch the "Lead" label only. Not the whole inbox.
Go High Level (LeadConnector app), Search Contacts. Search by the sender's email address.
Router. Path A if a contact was found, Path B if not.
Path B: Create a Contact. Name, email, and set the source field to "Inbound Email".
Both paths: Add a Note to the Contact. Paste in the subject, the date and the first 500 characters of the email body.
Both paths: Create a Task. Assign it to whoever owns new leads, due tomorrow, titled "Reply check: [subject]".
Those module names are straight from Make's HighLevel LeadConnector app docs, so you won't be hunting for them. Run it once against your own test email before you turn the schedule on.
Step 6 is the one people skip and shouldn't. The task gets closed when someone actually replies. If tasks are piling up, you know where your follow up is dying, and you know it before the lead goes cold instead of after.
One more HighLevel note. Their LeadConnector MCP server now lets Claude and ChatGPT read and even build workflows in your account through OAuth, no token juggling. It's powerful, and it asks for a lot of permissions. For this week, keep using Make for the plumbing and keep MCP for asking questions.
Set the follow up routine that fires when you hit send
The newest trick I'm using comes from Littlebird. Since the October 23 update, a Routine can run on a Gmail event, including the moment you send an email. Littlebird's own example is summarizing your promises after you send a proposal. You build Routines by describing them in Chat, so you can paste this in almost word for word.
Create a Routine that runs every time I send an email from [[email protected]] to someone outside [yourcompany.com]. If the email contains a quote, a proposal, a price, or a question that needs an answer, do three things: 1. Write down any promise I made in the email (a date, a deliverable, a callback) in one line each. 2. Remind me in 3 business days if the recipient hasn't replied, with a suggested two sentence follow up. 3. If I promised something by a specific date, remind me the day before. If the email is a simple thank you, a scheduling reply, or internal chatter, do nothing. |
Keep the "do nothing" line. Without it you'll get a reminder every time you send "sounds good," and you'll turn the whole thing off by Thursday.
Littlebird also added Pipedrive, folk, Streak and Microsoft Teams in that same update. If your pipeline lives somewhere other than HighLevel, check the connectors list before you build anything custom.
The one setting to leave off
Auto send. Every one of these tools can do it, or will soon, and every one of them will offer it to you during setup with a nice friendly toggle.
Leave it off for two weeks. Here's why. In week one, you're going to find out that your rules are a little wrong. Rule 2 will catch a vendor asking about pricing on their side. Rule 5 will archive a newsletter that was actually a client's announcement. The drafter will quote last year's rate because it found an old email. None of that is a disaster when it's sitting in drafts. All of it is embarrassing when it's already sent.
So for two weeks, you keep a simple log. Every draft you send unchanged gets a check. Every draft you edit gets a note on what you changed. If after two weeks you're sending more than 90 percent of a category untouched, that category can move up a rung. Appointment confirmations and "here's the link you asked for" replies usually get there. Quotes, apologies and anything with money in it usually don't. Leave those with a human.
Want proof the setup is paying off? Turn on Rize for those two weeks and look at how much time you spend in your email client before and after. Your gut will tell you it's working either way. The tracker gives you an actual number.
What this looks like when it's working
Take a three crew roofing company. Before: the owner opens Gmail at 6:30 a.m., spends 50 minutes sorting, misses a quote request buried under supplier promos, and finds it Thursday.
After: Inbox Zero has already archived the promos and forwarded the material invoices to the bookkeeper. Two lead replies are starred with drafts waiting. Make has dropped both into HighLevel with a task for the office manager. The owner asks Claude, through Fluxmail, which quotes went out last week without a reply, and gets a list of three. He sends the drafts, edits one, and he's out of the inbox by 6:50.
That's 30 minutes back every morning, which adds up to more than 120 hours a year. And this time the quote request got answered the same morning, which is worth more than the hours.
FROM THE AI NEWSROOM The AI Business Accelerator For operators who would rather build it with someone than build it alone. The full stack, installed alongside you, with the decisions made in the room instead of guessed at. Ninety seven dollars. Join the Accelerator for $97 |
This week
Pick one inbox to start with. Your sales or shared inbox, not your personal one.
Sort a week of mail into the four piles by hand so you know what your rules need to catch.
Install Inbox Zero, paste in the five rules and the Lead Reply guidelines, and run the bulk unsubscriber.
Build the Make scenario that logs "Lead" emails into HighLevel with a next day task.
Set up the Littlebird routine that fires when you send a quote or proposal.
Put a reminder on your calendar two weeks out to review your draft log before you even think about auto send.
Jordan
The AI Newsroom | Practical AI for people with a business to run.