Automated Titan Email Inbox Routing and Handoff
Every morning, WebRun opens your Titan inbox, reads new messages to judge whether they belong to sales, support, or billing, logs each one as an Airtable record with the assigned teammate, and adds it to a shared Notion handoff log so nothing sits with the wrong person.
How do I route Titan inbox messages to the right teammate?
WebRun checks your Titan inbox every morning for new messages and judges whether each belongs to sales, support, or billing. It logs the handoff to Airtable with the assigned teammate and adds it to a shared Notion log, so every message reaches the right person without sitting unclaimed.
- New messages get routed to the right department the same morning
- Every handoff is logged in Airtable with a clear owner
- A shared Notion log shows which messages are still unclaimed
Built for small business owners · support teams · agencies · office admins
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
titan.emailin a real browser with your saved login - no setup, no API keys. -
1
Titan - read and classify new messages
- Open the Titan inbox and check new messages
- Judge whether each one is a sales, support, or billing matter
- Note the sender and a one line summary for each
Done when Every new message this run has a suggested department and owner.
-
2
Airtable - log the assigned handoff
airtable.com
WebRun opens Airtable to log the assigned handoff. - Add a record for each message with the sender, summary, and assigned teammate
- Tag it by department
- Leave it open until the assigned teammate replies
Done when Every routed message this run has an Airtable record.
-
3
Notion - post it to the shared handoff log
notion.so
WebRun opens Notion to post it to the shared handoff log. - Add each new handoff to the shared Notion log
- Group entries by department
- Note which ones are still unclaimed
Done when The shared handoff log shows every message routed this run.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it reply to the customer in Titan?
No. WebRun only reads and routes messages. Replying to the customer stays with whichever teammate picks up the handoff.
How does it decide which department a message needs?
It reads the message for signals like billing questions or support issues and routes it to the matching department, rather than guessing from the subject alone.
What if a message needs more than one department?
It routes to the department that looks most relevant and notes the overlap in the summary, so the assigned teammate can loop someone else in.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.