I've been using Snoooz extensively for email categorization and had a couple of ideas that I think could make it even more powerful. 1. Learn from manual categorization It would be great if Snoooz could learn when users manually move an email to a different label or folder. For example, if I repeatedly move emails from a particular sender into the same category, Snoooz could recognize that pattern and either: automatically categorize similar emails in the future, or suggest creating or updating a rule based on those corrections. This would allow the categorization system to improve over time instead of relying solely on manually configured rules. 2. Learn from category corrections Similarly, when a user changes an email from one category to another, it would be helpful if Snoooz treated that as feedback and used it to improve future categorization—not just learn from edits to AI-generated drafts. 3. Better guidance for prompts and rule hierarchy A guide or best-practices section for writing prompts would be incredibly helpful. Since rules are processed by priority, I've noticed that prompts or rules created for one category can sometimes be overridden by higher-priority rules. While this is expected behavior, it can make troubleshooting difficult. It would be useful to have: Best practices for writing prompts. Examples of effective prompts. A clearer explanation of rule hierarchy and evaluation order. Warnings when a newly created rule is likely to conflict with or override an existing one. A preview or testing tool that shows which rule would match an email and why. 4. Automatically mark processed emails as read It would be helpful to have an option that automatically marks an email as read after Snoooz has successfully categorized it, moved it to the appropriate folder, or completed the selected automation. I think these improvements would make Snoooz much easier to configure, especially for users managing many categories and complex workflows.

Could you please add OpenAI-Compatible Provider in BYOK (custom AI model) ? OpenAI-Compatible setup (baseURL + API) is currently the AI Industry standard for BYOK. Why does this matter? Freedom of Choice: Users are able to use their current AI Providers (you name it OpenRouter, Google Studio, Together AI, DeepInfra, LLM Gateway...) No Reliability Trade-off: It’s a standard "plug-and-play" format, without degrading performance Future-Proofing: Avoid be tied to a single provider’s roadmap.

An external system pushes context into Snoooz before a reply is generated — giving users control over what data enriches email responses

It would be amazing to enrich replies by sending inbound emails to an API external datasource, gathering context and then returning the information for a highly customised email response.

There are some times where an email may come from the same sender (e.g. events@heartbeat.chat), but the sender NAME might be different (in this example, the community’s name will be different, and that will be the Sender name). We should be able to filter rules by Sender Name for instances like this

We receive many leads from our Facebook ads, web forms, and 3rd party services. Would be incredibly helpful to draft and send a new email based on the information in the email with the lead’s information. Here is an example of what we receive now, we’d like to draft a new, separate email using the name, email address, and additional details from the lead: Subject: New FB Lead New Lead submitted From your Facebook Ads Campaign! Name: Bob Builder Email: bobthebuilder@example.com Phone: (555) 555-2975 Project Zip: 12345 What type of fencing materials are you looking for? Aluminum How soon do you need fencing materials for your project? 1-2 months Thank you!

Actually at account level - would be better at workspace level like a data source, so you can have different shops under one account and data is protected for workspaces which answer only non-customer questions (e.g. HR, general)

There should definitely be the option to “run” a rule that we just created on our existing mailbox so it even replies to previous emails that match the rule requirements.

I would like to export all my analytics and logs in bulk

Please can you join Albato and consider adding the webhooks triggers that will allow information to be sent so management of receipts and evidence including attachments we receive to be extracted and stored elsewhere . Albato is very good and still adding more and more apps to its list . Albato is on app sumo.

Have you heard of Wellybox? It is a software that is dedicated to extracting receipts for expense purposes. Can you create a rule within snoooze so only receipts are displayed in a separate tab with a filtering ability by the vendor. Can you create a webhook that allows this to be a function even if we have to automate it? Welly box was in App Sumo btw.

1) When using a template to respond to an automatic email it keeps the old subject from the original email. The subject is often a generic admin subject like “you have a new user”. Can the templates have an option to have a subject inserted that “replaces” the subject line in the email that it is being used to respond to? 2) Sometimes emails come in to an admin email address and you want to reply from your named email address to make it more personal. Can the “from” email address be an option to add in the rules so we can select the email address we want it to go from? Thank you

both were also on appsumo and are calendly alternatives

Would it be possible to automatically mark the email as "read" (e.g. on Gmail) after auto-replying to it using Snoooz? Because currently the emails remain marked as "unread" and it's difficult to see which emails have received a response already. Maybe that could be added as an option under the rule’s 'Then' actions?

Because Gmail has parent and child labels, but it requires all of those labels to be applied to a single email in order to fully use this feature. So I hope it’s possible to add support for multiple labels. Thank you!

It would be great to have a dark mode option for the main Snoooz dashboard/sites interface. This would help reduce eye strain, especially when working at night or in low-light environments, and provide a more consistent experience with other tools that already support dark themes.

It would be great to know somewhere which fields are being injected into the context window when running it through each category. For example, are the mail headers included? Are the recipients, sender and subject details referenceable? I’d like to create quite specific rules to pick out spam/junk/phishing emails, but I don’t know if I can instruct it by saying things like: Apply this label if the email falls under one or more of these cases: Phishing or impersonation Requests for passwords, MFA codes, recovery phrases, or one-time codes Requests to “verify”, “confirm”, “unlock”, or “restore” an account via a link EXCEPT where the sender domain matches the service that is being requested. Sender claims to be a bank, government agency, delivery service, or platform but: The sender domain does not match the claimed organization The email uses generic greetings like “Dear customer” when the sender should know the recipient’s name Urgent security warnings combined with a call to action Coercion or pressure tactics Artificial urgency: “act now”, “last chance”, “account will be closed today” Threats of loss, penalties, suspension, or legal action without proper context Emotional manipulation: fear, panic, shame, or guilt as the primary motivator Spam or affiliate marketing behavior Affiliate-style language: “make money fast”, “passive income”, “guaranteed returns” Get-rich-quick schemes, crypto pumps, trading bots, or financial promises Cold outreach selling SEO, marketing, lead generation, or web services Obvious mass-sent emails unrelated to any prior interaction Abusive or inappropriate content Sexual content, explicit imagery, or sexually suggestive messaging Harassment, insults, aggressive language, or intimidation Scam-style romance or relationship manipulation Other cases may include a mismatch of intent in the subject vs email body.

Your AI is smart 😊. I would love to see the possibility that based on variable input “ordenumber” or “sending mailaddress” in the email from a customer, the AI would search in a table (Google sheet?) and extract output variables connected to the variable input. For this I would like to see the opportunity to: Connect a Snoooze workspace to an external database eg Google sheet URL X Define the input variable field from incoming mails (like sending mailaddress or ordernumber in body of mail) Have AI retrieve output variable from the connected external database… And use that output string in their mail response. This is the usecase I am trying to solve: about 30% of my emails are related to “when will my order be delivered?”. Right now I manually lookup the order and it’s track&trace code and then externally check the status of the T&T code and paste that output in a standardized response. Am looking for ways to automate this. I don’t see an issue in collecting all this info and putting the targeted output string together in an external database like Google Sheet. Would love to see the possibility that Snoooze can basically vertical lookup in the database to extracty output of data X based on input data Y. Hope that is clear enough 🙄? If not, feel free to contact me.

Can you add the option in rule setting: “when email has label X” than action Y. This would be handy to better trigger the correct AI response based on the customer journey stage the email is in.

I would like to copy / paste and edit exisiting keywords. That’s not possible yet: I have to type them all again if I want to add a keyword with slightly different content. For example: Keyword 1 = I accept the discount of 15% Keyword 2 (to be added) = I accept the discount of 30%…I would like to copy /paste from 15% and then change 15 to 30% Same approach when I accidentally make a spelling mistake….I would like to edit existing keyword. At this moment I have to delete the misspelled keyword and add a new one to the rule. Minor thing, but when you use a lot of keywords in rules it is getting annoying…