Routing Inbound Vendor Emails to the Right Team (Without a Middleman)
The slowest part of handling vendor emails is often not the reading — it's figuring out who should see it. A simple routing table, agreed once, removes that step and gets relevant pitches to the people who can decide.
The usual flow — and its cost
- The form notification hits info@ or the office manager.
- Someone reads it and decides whether it's a pitch and who it's for.
- They forward it to whoever they think owns it (sometimes wrongly).
- That person decides — or forwards again.
Three people and two forwards per pitch is common. Pitches with no obvious owner simply die in the inbox.
Build a routing table
| Category | To (decides) | CC (stays informed) |
|---|---|---|
| Hiring, training, HR tools | HR | Head of HR |
| Software, security, IT services | IT | — |
| Ads, web, social | Marketing | Comms |
| Office, facilities, perks | Operations | — |
| Finance, insurance, funding | Finance | CEO |
| Anything else | General inbox | — |
Keep To for the decision-maker and CC for people who just need to know. Too many CCs and nobody replies.
Define the fallback and the fix
- Fallback: one owner for anything that matches no category. Review it monthly and add categories as patterns appear.
- Wrong team? Agree that the recipient re-routes it directly (or back to the fallback) and the table gets corrected.
Make ownership visible
Without a signal, two people reply or nobody does. A shared list, a status field or simply a “taking this” reply in a chat thread prevents both.
Route complete information, not raw emails
Forwarding a vague pitch just moves the back-and-forth to someone else. Ideally the pitch arrives with who it's for, what it solves, rough pricing and references already filled in.
Notify where people actually look
Teams that live in Slack or Microsoft Teams will see a channel message faster than an email. Team-specific review points are covered in how different departments should evaluate pitches.
FAQ
How do I split To and CC?
To is whoever decides. CC is for people who only need visibility. Keep CC short.
What if a pitch is routed to the wrong team?
The recipient re-routes it or returns it to the fallback owner, and you update the table.
Is routing worth it for a small company?
Yes — even with few teams, naming an owner per category stops pitches from getting lost.
Summary
Agree a category-to-team table with To for the decider and CC for visibility, name a fallback owner, and define how misroutes get fixed. Route complete information, make ownership visible and notify people where they work.