Group messages by job, project, cargo or voyage. Track everything from start to finish - even across teams.
▶️ Watch: Mastering Transaction-Based Workflows
What Is a Transaction-Based Workflow?
In a Transaction-Based model, your inbox reflects a shared operational unit, such as a job, port call, or project. Each message is connected to a broader process, and the job tag is the key.
This model is perfect when:
- Multiple roles contribute to the same transaction
- Teams need full visibility from start to finish
- Work must be tracked and handed over seamlessly
“We have a job tag for every voyage, and our operators subscribe to the job tags for their voyages. This means they only have to read messages about their ships, and when I need to check progress, I just click the Tag and I can see everything from fixing to finance all in one place.”
- Operations Manager using Stream
How It Works
These teams use job tags and tailored Live/Saved Searches to surface relevant work and maintain a shared source of truth.
Search or Tool | Purpose |
---|---|
Focus (Live) | Surfaces important tagged messages for the user (their “to watch” list) |
Comments (Live) | Displays all messages where the user has been tagged in a comment |
Safety Net (Live) | Catches untagged or non prioritised messages to prevent gaps |
Everything Else (Saved) | Identifies messages that can be safely archived using Tidy |
To Do (Saved) | Shows all followed messages - acts as a basic personal task list |
Powered by Important
This way of working is powered by a feature called Important. A message is marked as Important if:
- It has a Job Tag you’re subscribed to - this can be done manually, or automatically via an integration with your system of record
- It includes a contact you’ve marked as Important
- You’re following the message directly
This automatically builds your ‘to-watch’ list, surfacing only what truly matters to you.
The Flow
- Triage your inbox
→ OpenFocus
to see priority messages
→ Decide: is this relevant to me or my transaction?
→ If not: archive it
→ If yes: follow the message and continue - Assign visibility
→ Ensure the correct Job Tag is applied
→ If not tagged, apply one
→ @mention a teammate to assign ownership where needed - Subscribe to the right Tags
→ Manually subscribe to the job tags of transactions you’re involved in by following this guide
→ CheckFocus
to confirm you're subscribed
→ If your team uses an integration (e.g. IMOS or GAT Ship), tag subscriptions may happen automatically when you’re assigned in your system of record. - Monitor gaps
→ CheckSafety Net
for untagged messages
→ Apply a Job Tag to any messages that need it - Declutter and clean up
→ Go toEverything Else
→ Use Tidy to archive non-priority messages in bulk
Try It Now
- Apply a Job Tag
- Subscribe to a Job Tag
- Check your
Focus
for messages associated to that Job Tag - Look in
Safety Net
for untagged messages
What’s Next?
Once your Tags and Searches are working for you, it’s time to build collaboration into your daily habits:
➡️ Collaborate with Your Team →
Comments
0 comments
Please sign in to leave a comment.