Identify important emails and prepare the next response
A busy inbox is not necessarily a well-managed inbox. Customer enquiries, invoices and internal questions require different next steps. I help Swiss SMEs and independent professionals structure recurring inbox work: classifying messages, identifying responsibilities and preparing draft replies. This concerns your operational inbox, not newsletters or bulk email campaigns.
Discuss your workflowChoose a clear starting point
Useful candidates are defined message types with known owners, such as new enquiries, scheduling requests or questions about active projects. Together, we agree what counts as urgent and which cases always need a person. Personal, legal and financial matters require different boundaries from a routine acknowledgement.
From an incoming message to a proposed action
An authorised message is the starting point. The workflow identifies details such as the request, deadline, customer context and missing information. Agreed rules suggest a category or responsible person. A draft can draw on approved information; if that information is missing, it prepares a question rather than inventing an answer.
Example using fictional data
One message, one reply ready for review
Not a client case study or a real project result. All details are fictional.
Message “Could you move the workshop to next week? Please confirm whether there would be any additional charges.”
Classification Category: date change · owner: project lead · unresolved: available date and any rescheduling charges. The message alone does not justify a commitment.
Reply draft · not sent
Thanks for your message. We will check availability for next week and whether rescheduling would involve any charges. We will then send you a specific option. The change is not confirmed yet.
Your approval → output The responsible person checks the calendar and agreed terms, adds the confirmed details and approves the reply for sending. This example sends nothing.
If ownership is unclear The message stays open for manual review. It is not automatically forwarded, deleted or answered with a binding confirmation.
Permissions and approval come first
Before implementation, I establish whether access concerns a personal or shared mailbox and which folders are needed. Reading, creating drafts and sending are considered separately. Technical access is not blanket permission to process every message or perform any available action.
Replies containing commitments, payment details, contractual matters or other sensitive information require human approval. Deleting messages, forwarding to external recipients and changing account details do not silently become part of the workflow. Incoming email text and links are not treated as instructions to extend permissions or disclose other information.
Outputs and handling uncertainty
Depending on the agreed scope, outputs may include categories, tasks or draft replies. Uncertain classification, missing information or a technical failure sends the case to a visible review list. The message must not simply disappear. We define what is logged and who handles failures as part of the operating arrangements.
Connecting Outlook or Gmail depends on the account type, administrative approval and available interfaces. We also review storage locations, external processing, retention and attachment handling beforehand. There is no blanket promise that every existing email environment can be supported without changes.
Begin with one message category
A pilot can start with one described category, clear responsibilities and anonymised examples. We assess whether drafts are useful and whether exceptions remain visible. Where a request leads to a proposal, a separate proposal workflow may be appropriate. A reporting workflow can be considered if you need an overview of cases awaiting attention.
Which emails take up the most time?
Describe one recurring message type and how you currently handle it. An anonymised description is enough for the first conversation.
Discuss your inbox workflowFrequently asked questions
Will emails be sent automatically?
The workflow described here produces drafts for review. Sending is connected only with explicitly agreed approval. Particularly sensitive responses remain the responsibility of a person.
Does the workflow need access to the entire mailbox?
Not necessarily. I check whether a limited folder, a shared mailbox or another restricted access arrangement is sufficient. The options depend on your provider and administrative policies.
What happens to confidential attachments?
Attachments are not automatically processed without limits. Permitted file types, necessary contents, storage locations and external services must be agreed first. Unclear cases are held for review.