Hours come back to your team
Work that is repetitive, rule-based and high-volume is where automation pays, and it is found by measuring the process you run today.
AI email triage for shared inboxes
An inbox mixes sales requests, client questions, supplier messages and automated notices. Norml builds an AI email triage workflow around the categories your team uses. We connect the selected mailbox, test the classification rules against representative messages and route the result to a named owner. Unclear messages stay visible for review.
A few clients we’ve worked with
What we do
Sort incoming email into agreed categories and owned queues, with an explicit route for ambiguous messages and a record of each routing decision.
What an automated step is actually worth.
The expensive mistake is automating the wrong step convincingly. The value is real, and it comes from measuring the process before building anything.
Growth stops adding headcount
When the routine path runs itself, the next increase in volume does not need another person watching a queue.
The output can be checked
An automated step nobody can verify is a liability, so the review point is part of the design rather than something bolted on later.
Give incoming messages a clear destination
The starting scope uses Gmail, n8n and Claude. We agree which messages the model can read and which label or internal queue each category should produce.
- Solution
- Automations
- Tools
- Gmail, n8n, Claude
- Trigger
- A new message arrives in an included Gmail mailbox, or a team member selects a message for classification.
- Outcome
- Apply the agreed category, record its evidence and route the message to an owned queue; retain uncertain or failed items for review.
Categories your team can explain
Define categories such as new enquiry, existing client, supplier and needs review. Include representative edge cases and decide whether one message can belong to several categories. Explicit sender or account rules can take precedence over a model suggestion.
Labels and internal ownership
Map accepted classifications to Gmail labels and an agreed owner queue. Keep the original message and thread reference available. Classifying a message does not grant permission to forward its contents to a different mailbox or external service.
Uncertain messages and repeat events
Configure a visible fallback for unmatched, conflicting or invalid results. Retain the message ID and processing result so another trigger does not repeat the same handoff. Later replies receive their own assessment when the conversation changes.
Client reviews
Read our reviews on Clutch ↗“Norml Studio's professionalism and responsiveness were impressive.”
“They were proactive in suggesting improvements we hadn't considered.”
“They delivered what they said they would, on time.”
“They focused on how to make our daily operations easier, not just on building features for the sake of it.”
“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”
“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”
Define the inbox boundaries
Approved mailbox access
Identify the mailbox, included folders or labels, account owner and permitted data. Exclude personal mail and attachments unless they are explicitly included. We verify the supported connection before relying on a shared-inbox setup.
An accountable review queue
Assign someone to ambiguous messages and routing failures. Define urgency using your operating policy. A model-generated confidence number cannot establish reliability without evaluation against labelled examples.
Separate sorting from sending
This workflow categorizes and assigns work. Reply drafting, sending, deletion, spam removal and automatic archiving require separate rules. The first release can leave all source messages in place while the team reviews classifications.
Test the categories before routing mail
Label representative messages
Your team categorizes examples, including messages with several requests and categories that are easy to confuse. We use these examples to define expected behavior.
Build and inspect the route
Connect the mailbox and model, map allowed labels, and record the chosen category with its source. Unmatched output must reach review instead of being discarded.
Check failures and corrections
Test repeated events, a new reply, invalid model output and an unavailable destination. Confirm that a reviewer can correct the category and resume the missing handoff.
The people who do this work.
No account layer between you and them. These are the Norml specialists this work runs through.
Max Tymoshyn
Founder & Architect
Artur Tsitou
DevOps & Backend Developer
Petr Savenok
Full-Stack Developer
Let's chat
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Max TymoshynFounder & Architect
Get startedRelated services.
Email triage questions
Can this work with Outlook as well as Gmail?
Outlook requires its own connection and checks for folders, categories and mailbox permissions. We scope the same sorting job around the supported account route; a working Gmail flow does not establish Outlook compatibility.
How does the workflow handle an uncertain message?
It puts the message into an agreed review route with the source link and classification result. The owner can choose the category. We test uncertainty rules with examples instead of assigning an arbitrary accuracy threshold.
Will AI delete or reply to messages?
The described scope keeps source messages and performs internal classification and routing. Deletion and customer replies are excluded. Any later action needs its own permission, review and failure rules.
Can existing mailbox rules stay in place?
Yes, after we identify which rules run before or after the workflow. Conflicting labels and competing assignment rules need one owner. We check whether a human correction should prevent further automatic changes.
Bring examples of messages, your current categories and the people responsible for each queue. We will define the sorting rules and the cases that should stay with a person.