Automated Missive Conversation Assignment
Every few minutes, WebRun checks Missive for conversations sitting unassigned, assigns each one to the right teammate based on topic, creates a Trello card to track the follow-up, and posts a heads up in Microsoft Teams so nothing waits unclaimed.
How do I assign unassigned Missive conversations automatically?
WebRun checks your Missive shared inbox every few minutes for conversations sitting unassigned, assigns each one to the teammate who owns that topic, creates a Trello card to track the follow-up, and posts a heads up in Microsoft Teams. No conversation waits unclaimed, and the actual reply to the customer stays with a person.
- Unassigned conversations get an owner within minutes
- Every handoff is tracked with a Trello card
- The team sees new assignments in Teams without checking Missive
Built for Support teams · Shared inbox teams · Small agencies · Operations teams
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
mail.missiveapp.comin a real browser with your saved login - no setup, no API keys. -
1
Missive - find unassigned conversations
missiveapp.com
WebRun opens Missive to find unassigned conversations. - Open Missive and filter the shared inbox to unassigned
- Read each conversation to judge its topic
- Assign it to the teammate who owns that topic
Done when Every unassigned conversation has an owner.
-
2
Trello - create a follow-up card
trello.com
WebRun opens Trello to create a follow-up card. - Open the follow-up board
- Create a card for the conversation with a link back to Missive
- Assign the card to the same teammate
Done when A tracked Trello card exists for every newly assigned conversation.
-
3
Microsoft Teams - post the handoff
microsoft.com
WebRun opens Microsoft Teams to post the handoff. - Open the team channel
- Post a short heads up naming the conversation and the new owner
- Link to both the Missive thread and the Trello card
Done when The team has been notified of every new assignment.
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
Does WebRun reply to the customer in the conversation?
No. It only assigns the conversation to a teammate. Replying to the customer is still done by that teammate inside Missive.
How does it decide who owns a conversation?
By reading the topic of the conversation and matching it to the teammate who normally handles that kind of request.
What if a conversation is already assigned?
WebRun only touches conversations that are still unassigned, so anything already claimed is left alone.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.