A lead's reply lands in their rep's inbox, not the shared one
Three Make scenarios watch a mailbox, match each sender to a CRM lead and forward the email to the rep who owns it, and keep a first-name column filled for personalised outreach.
Where this applies
Sales teams that share one mailbox but work leads individually, and want a lead's reply to reach the rep who owns that lead.
- runs in each forwarder, no errors
- 441
- polling, working hours only
- 30 min
- business lines, one forwarder each
- 2
The problem
When leads reply to a shared mailbox, the reply is seen by whoever opens it first, and the rep who owns the relationship is the last to know. The fix is not to give everyone the inbox, but to deliver each reply to the person it belongs to.
That needs a reliable link between an email address and a CRM record, and a rule for who the owner is that does not have to be re-decided on every email.
What we built
Watch in working hours
The scenario polls the mailbox every thirty minutes, Monday to Friday, 08:00 to 18:00, up to a hundred messages a run. Mail that arrives outside the window is simply picked up on the next run.
Match the sender to a lead
It looks the sender's address up on the leads board's email column, and an iterator walks the matched lead's owner column. Nothing is parsed from the body and no lead is created: it only recognises a lead that already exists.
Read the owner, do not choose it
The rep is whoever the board says owns the lead. The scenario resolves each owner's name and email from the CRM, with an ignore handler so a team or a deleted user is skipped rather than stopping the run, and forwards the original message to them. Choosing the owner is a separate step done upstream.
One forwarder per business line
A second business line has its own board and so its own copy of the same scenario, with its own mailbox connection, rather than a branch inside the first.
A first-name column, without a loop
A small webhook scenario fills a first-name column on a lead from the first word of its contact name, for personalised messages. It writes to a different column from the one it watches, so it cannot re-trigger itself, and it checks the name exists first.
The outcome
Each forwarder has 441 runs and no errors. Operations barely exceed runs (450 and 441), which means most polls find no mail from a known lead.
The first-name scenario is built but has not yet fired in production.
Where it stops
If the sender is not on the board, or writes from a different address, nothing happens and nobody is told. A lead with no owner is not forwarded, a team as owner is skipped, a lead with several owners is forwarded to each, and several lead items with the same email cause one forward per item. The second line's forward step has not yet been exercised. The first-name scenario has not been tested on leading spaces or single-word names.
Built with
- Make.com
- monday.com
- Microsoft Outlook
Patterns used
- Match sender to record
- Read the owner, don't choose it
- Working-hours polling
- Write a different column
Page copy drafted with AI assistance. Skofi is accountable for it. Editorial policy
Have something shaped like this?
If any part of the above resembles a problem you are living with, a short call is the fastest way to find out whether it is the same problem underneath.
What happens on the call
- 15 minutes, no deck
- We map the process on the call
- A written scope, or an honest no