The client asks this to see if you can think systematically about email management, not just react to today's inbox, and if you can translate abstract tools like filters and labels into a real daily workflow.
Structure your answer around the inbox categories the client actually deals with, then name the specific Gmail or Outlook feature you would use for each. Show you ask the client one or two clarifying questions before building the system, to reflect their habits.
Start by saying you would not build anything until you have asked the client two clarifying questions: which emails they must personally read versus which they only need to be copied on, and whether they prefer a zero-inbox daily close or a weekly triage. Then explain that you would create a small set of top-level labels, never more than five or six, because too many labels become as chaotic as the inbox itself. For recurring senders, you would build a filter for each known sender domain that automatically applies a label like Vendors or Clients, and you would skip the inbox for bulk newsletters by sending them straight to a Newsletters label with a filter that also marks them as read. For invoices, you would use a filter that catches the words invoice, payment due, or the client's billing domain, apply an Invoices label, and then set a second rule that forwards anything containing overdue to a separate flag or star so it never gets buried. For meeting requests, you would rely on the calendar invitation feature itself, but also create a Meetings label that catches the phrases calendar invite or RSVP, so the client can see all pending requests in one place. Explain that you would review the filters monthly with the client, because senders change and labels that no longer serve a purpose should be deleted. Finally, say plainly that you would start with a pilot week, tracking which emails still slip through, then adjust the filters based on what you actually see rather than guessing.
Some candidates say 'I will use folders and filters po' without explaining which ones or why, which feels generic. Instead name the exact labels and filters, for example, 'I will create an Invoices label with a filter for the keyword payment due, and a Newsletters label for all bulk senders.' Avoid Taglish like 'kaya po kasi walang structure' when explaining.
Situation
While supporting a consultant who subscribed to dozens of industry newsletters and received daily invoice and meeting traffic, I noticed their inbox grew by 150 unread messages every week despite regular manual sorting.
Task
I needed to design a low maintenance system in Gmail that would automatically separate actionable client messages from informational emails without hiding anything important.
Action
I interviewed the client for 15 minutes to learn which senders they actually read and which they only skimmed. I created five main labels: Action Needed, Invoices, Meetings, Newsletters, and Reference. I set up filters for the client's three most frequent client domains to automatically apply the Action Needed label and skip the inbox, then created separate filters for invoice keywords like 'invoice' and 'payment due'. Meeting invites were already tagged by Google Calendar, but I added a filter that applied the Meetings label to any message containing 'meeting invite' or 'calendar update'. For newsletters, I created one filter per major sender that archived and labeled them as Newsletters, so they never clogged the inbox. I then set up a weekly digest folder review reminder for the client.
Result
Within two weeks the client's unread inbox count dropped from 150 to under 30 daily, and they could see immediately which messages required a reply. The system required only 10 minutes per week to maintain.
An inbox system works only if it matches how the individual client actually reads and responds to email, not a generic template.
Write your own answer, then get instant AI feedback graded against:
Get AI feedback on your answer — free.
3 free AI-graded answers + 1 free mock interview, no card needed.
Sign Up FreeAlready have an account? Log in
Sign in to join the conversation.
No answers shared yet — be the first to show how you'd approach this.
Prioritizing a Full Inbox
Administrative Virtual Assistant
Onboarding Call Question Checklist
Administrative Virtual Assistant
Resolving Double-Booked Time Zones
Administrative Virtual Assistant
Decoding Client Shorthand Fast
Administrative Virtual Assistant