Team Email Rules That Everyone Will Follow
Deploy shared inbox logic across your team without fighting adoption.
You built a triage system that works for you, but your team ignores it or applies it inconsistently. Every person invents their own labels, filters break when someone leaves, and clients get duplicate replies.
That is the gap this drop closes. It is a operations skill built for Gemini, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Operations managers rolling out email automation to teams of three or more.
How it works
The skill file does five things, in this order.
1. Document the current chaos. Ask Gemini to interview you about how each team member currently handles shared inboxes and spot conflicts.
2. Build the standard rule set. Generate folder structures, naming conventions, and filter logic that accommodate everyone's genuine needs.
3. Create the one-page playbook. Turn the rules into a visual decision tree that shows exactly which emails go where without reading paragraphs.
4. Write the migration checklist. Generate step-by-step instructions for each person to archive old labels, apply new ones, and test on their actual inbox.
5. Draft the weekly audit prompt. Build a recurring Gemini check that flags when someone creates rogue labels or skips standard replies.
What comes back
A documented system, a one-page visual guide, and a weekly compliance check that runs in five minutes.
The mistake to avoid
Launch with two people first, not the whole team. Fix what breaks before you scale, or you will spend the next month in Slack threads defending the new system.
Running it
Save the prompt as a Gem so it is reusable, or paste it into Gemini with your files attached. If the task touches Sheets, Docs or Gmail, run it from the Workspace side panel so it can read the file you already have open.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
You are helping me deploy a shared email triage system to a team.
Our team size: {number_of_people}
Shared inboxes we manage: {inbox_names_and_purposes}
Current problems: {specific_complaints_or_duplications}
Tools we use: {email_platform_and_any_integrations}
First, interview me to understand how each person currently handles these inboxes. Ask one question at a time about their labels, filters, response templates, and pain points.
Once you have enough detail, create:
1. A unified folder and label structure that works for everyone
2. Naming conventions that prevent confusion
3. Filter rules written in plain language that I can implement in {email_platform}
4. A one-page visual decision tree showing which emails go where
5. A migration checklist for each team member to move from their current setup to the new one
6. A weekly audit prompt I can run in Gemini to check if anyone is creating non-standard labels or skipping agreed processes
Format everything so a new hire could follow it without asking questions. Flag any rules that depend on judgment calls and suggest how to make them objective.