Lorixen.
EN

Turn customer emails into tasks automatically

Short answer: Give your task tool its own email address, then make sure only real requests reach it: forward by hand for a few weeks, then add rules that send specific senders or subject patterns automatically. Make sure replies in the same thread update the existing task instead of creating a new one, and finish every task by telling the customer it's done. Most task tools (Trello, Asana, Todoist, Microsoft Planner via Power Automate) can do the capture part; the rules, owners and close-the-loop step are where the real work is.

Email is where customer requests arrive and also where they get lost. "Can you change the delivery to Thursday?" sits in someone's inbox under twenty newsletters, gets read, gets forgotten. A task tool gives the request an owner, a due date and a place the whole team can see. The job is getting it there without anyone retyping it.

Step 1: Decide what counts as a task

Before any automation, write down which emails should become tasks. For a hypothetical joinery workshop, that might be:

  • Change requests on an existing order.
  • Quote requests from the website form.
  • Complaints or snagging issues.
  • Supplier confirmations that need a follow-up.

And what shouldn't: newsletters, invoices handled by accounts, general chat. If you can't describe the rule in a sentence, a machine won't follow it either.

Step 2: Find your task tool's email address

Most task tools give each board, project or inbox an address. Trello's email-to-board help is a good example of what to expect:

  • Each board has a unique email-to-board address, and each card has its own address for adding comments by email.
  • The email subject becomes the card title and the body becomes the description; attachments and images in the body are added to the card.
  • You can add labels from the subject line with #labelname and members with their @username.
  • There's an overall size limit of 10 MB including attachments; bigger emails won't create a card.
  • With its summarise option, Trello says AI can condense the title and description and, where applicable, create a checklist and a due date, and it warns the summary might miss information, due dates or action items.

Asana, Todoist and others have their own email features; check each tool's current help page for the address format and what it does with subjects, attachments and replies.

Treat that address like a password. Anyone who has it can add work to your board. If it leaks, Trello lets you reset it from the board menu (the old address stops working).

Step 3: Start by forwarding manually

For the first two or three weeks, have the person who triages email forward qualifying messages to the task address. It feels low-tech, but it shows you:

  • Which subject lines and senders actually produce tasks.
  • Whether the task titles make sense (customer subjects like "Re: Fw: question" don't).
  • How long the tasks take and who ends up doing them.

Tip: when forwarding, rewrite the subject so it reads as an action. "Change delivery to Thu – Order 1043 – Patel" makes a better task title than "Re: Order". In Trello you can add the label in the same line.

Step 4: Automate the obvious ones

Once patterns are clear, automate only those. Two common routes:

Mail rules. Outlook and Gmail rules can auto-forward emails from your website form (fixed sender) or with a known subject ("New quote request") to the task address. Check your email admin settings; some organisations block automatic forwarding to external addresses.

A workflow tool. If you're on Microsoft 365, Power Automate's When a new email arrives (V3) trigger can fire on folder, recipient address, sender, importance, attachments, or words in the subject (the Subject Filter). Your flow then creates a task in your tool of choice, such as Planner. Microsoft makes one point worth following: each plan has a run quota, so put your filters in the trigger's own properties rather than in a later condition, because every run that starts counts against the quota even if the condition then fails.

AI extraction, carefully. Tools that pull out due dates and actions from an email can save typing, but they guess. Trello's own warning that summaries might miss details applies to every tool. Keep the original email attached or linked to the task, and have a person confirm the due date for anything with a promise to a customer.

Step 5: Stop duplicates before they start

Customers reply, forward, and CC colleagues. Without care, one request becomes four tasks.

Trello handles part of this: after a card is created from an email, replies in that thread that include the board address are added to the card as comments rather than new cards, for 7 days. After that, replies create new cards. Other tools behave differently, so test with a real thread.

Practical habits that help:

  • Put an order or job number in the subject when you forward or reply, so a person (or rule) can match it.
  • Use the task's own email address, where the tool offers one, for later updates on the same job.
  • Do a quick weekly sweep for duplicates; merge or archive them.

Step 6: Close the loop with the customer

A task marked done in your tool means nothing to the customer until they hear about it. Add a final step to your task template: "Reply to customer confirming". Better still, keep a few short reply templates ("Your delivery has moved to Thursday 14th") so closing the loop takes a minute. If the tool supports it, a comment-by-email on the card can record what was sent.

Troubleshooting

Emails never arrive in the task tool. Check the address (it may have been reset), your organisation's external forwarding policy, and size limits; in Trello, emails over 10 MB won't create a card.

Tasks have useless titles. Customers' subjects are vague. Rewrite subjects when forwarding, or use a workflow tool to build titles from fields such as order number and customer name.

Attachments show as winmail.dat. That's an Outlook formatting issue; Trello's help lists it as a known troubleshooting topic. Sending in HTML or plain text instead of rich text usually avoids it.

The flow runs too often. Move filters into the trigger properties (sender, subject filter, folder) so irrelevant emails never start a run.

Due dates are wrong. Turn off automatic due dates, or keep them as suggestions a person confirms.

FAQ

Do I need a shared inbox as well?

Not necessarily. Forwarding to a task tool works from individual inboxes too. A shared inbox helps when several people triage, but it's a separate decision.

Can the customer see the task?

Not unless you share it. The task tool is internal; the customer only sees your emails, which is why the closing reply matters.

Is it safe to put customer emails into a task tool?

Treat it like any system holding customer data: limit who has access, don't forward more than needed (strip long threads), and remove old tasks you no longer need.

What if a task needs several people?

Use checklists or sub-tasks inside the one task, rather than forwarding the email several times.

When your team's requests keep slipping through email, we can wire your inbox to the task tool you already use.

Sources

WhatsAppLet’s talk