Bosun, by GTM Cloud · Convert · Pre-release
Salesforce lead routing you can test before it runs
Bosun routes leads, cases and any record with an owner through ordered rules, round robin pools, territory tables and lead-to-account matching. Every assignment can be explained, and a bad run can be put back.
Status: Pre-release. Bosun is built and install-tested, and it’s in pilot. It isn’t publicly listed yet.
You know this one
A rep stops you at the coffee machine. “I swear the round robin skips me.”
You open the routing. There’s an assignment rule, a flow that bumps a counter field, and a spreadsheet someone updates when people go on vacation. Nobody remembers who built the last two.
You can’t prove she’s wrong. You can’t prove she’s right either, because nothing ever wrote down why a lead went where it did. So you say you’ll look into it, and she nods the way people nod when they’ve heard that before.
Salesforce lead routing, with the reasons written down
Bosun decides who owns a record. You write ordered rules, each with conditions and a target: a user, a queue, a pool, the account’s owner or a territory. Pools share work by round robin, weight or fewest open, with caps, time away and business hours.
A new lead from an existing customer is matched to the account by email domain, website and name, linked, and sent to that account’s owner. Before any of it runs, you test one record or a whole list. After it runs, the log says which rule matched and why.
The bosun is the crew member who assigns the work on deck. Same job, with a log.
See it first. Take it back. Keep the receipt.
| Preview | Undo | Prove |
|---|---|---|
| Test one record or a whole list and see who would get what, before anything is assigned. | Put back one assignment or a whole run; records moved by hand since are left alone. | A log line for every assignment: the rule, the reason, from and to. |
What you get
Test before it runs
Test a record shows each rule evaluated and who would get it. A bulk preview shows the whole distribution first, without using anyone’s turn.
Fair turns, with real-life rules
Round robin, weighted or fewest open. Caps stop a full plate getting fuller, and time away and business hours skip the people who aren’t there.
Leads that meet their accounts
A new lead is matched to an existing account by email domain, website and name, linked, and sent to the account’s owner.
A bad run you can put back
Every assignment keeps the previous owner. Put back one record or a whole run. Records someone has since moved by hand are left alone and listed.
The answer to “why not me?”
The log says which rule matched, and who was skipped and why. Managers can stop guessing.
Any object with an owner
Leads and cases route as they’re saved. Everything else, your own objects included, routes from a Flow action, a button or a bulk run.
How it works
- Build a pool. Add members, weights and a cap. People record their own time away.
- Write the router. Add rules in order, each with conditions and a target, and name a fallback.
- Test it. Run Test a record and a bulk preview on last month’s leads.
- Switch it on. Turn on the entry you want: on save, from a Flow, or on demand.
Two readers, two reasons
If you’re the admin
Routers, pools and territory tables are metadata you edit in the app and deploy like anything else. Each entry point has its own off switch, and a routing error never blocks a save unless you choose that.
If you’re the one signing off
Slow or unfair distribution loses deals and good reps. Bosun gives every lead an owner in the same moment and shares work by rules the team can read. Operations can change routing without holding their breath.
Today, and with Bosun
| Today | With Bosun |
|---|---|
| Assignment rules, a formula and a spreadsheet | Ordered rules, pools and territory tables in one place |
| A rule change tested in production | A preview on real records before a change goes live |
| Leads from customers treated as strangers | Leads matched and sent to the account’s owner |
| A leaver’s records moved by hand | One run to reassign, and one to undo it |
Where it’s strong, and what to know first
We’d rather you find the limits here than after you install.
Where Bosun is strong
- Preview a routing change on real records before it goes live
- Round robin, weighted and fewest-open pools, with caps, time away and business hours
- Lead-to-account matching that sends a customer’s new lead to the account’s owner
- Undo for a single assignment or a whole bulk run
- A plain-language reason for every assignment
- Works on any object with an owner, including your own
Good to know before you install
- Version 1 assigns the owner only. Account teams, opportunity teams and territory-management assignments aren’t set.
- Matching is by email domain, website and normalized name. It doesn’t follow account hierarchies in version 1.
- Your own objects route from a Flow action, a button or a bulk run, not automatically on save. A package can’t add a trigger to an object it has never seen.
- It doesn’t reassign when a response time is missed, and it doesn’t schedule meetings.
Questions people ask
Can Bosun run beside our assignment rules?
Yes, though one should win per object. Bosun’s Health Check tells you when a native assignment rule is active on an object Bosun routes, and which runs last.
What happens if routing fails?
The owner stays as it was, the failure is logged with the reason, and the save goes through. You can choose to block the save instead.
What if a rep is away?
They record their own time away, or a manager does it for them. They’re skipped, the skip is logged, and you decide per pool whether they get make-up turns when they’re back.
Does Bosun replace Omni-Channel?
No. Omni-Channel pushes live service work to agents. Bosun sets record ownership. They can sit side by side, and Bosun doesn’t touch Omni-Channel. Live work pushed to an agent stays Omni-Channel’s job.
How do I set up round robin lead assignment in Salesforce?
Assignment rules can’t take turns or see who’s away, so you build a pool in Bosun: members, weights and a cap. Write a router with ordered rules and a fallback, preview it on last month’s leads, then switch it on.
How do I route a new lead to the existing account owner?
Bosun matches the lead to an existing account by email domain, website and normalized name, links it, and routes it to that account’s owner. Matching doesn’t follow account hierarchies in version 1.
Works well with
- Portage: load a list with every row checked first, then preview and run a bulk assign.
- Sounding: ownership is one of Sounding’s ten checks, so you can measure your data before and after a routing change.
- Sluice: for the duplicates that remain, find and merge them with an undo.
Bosun is part of the Convert stage of the lead-to-renewal map. Untangling a messy routing setup? Our Salesforce services team can work through it with you. Every app installs by itself. None needs another.
Built on the platform
- Native to Salesforce. Rules, pools and territories are Custom Metadata, and the log is records in your org.
- Every entry has an off switch, and nothing routes until you turn one on.
- Doesn’t touch Omni-Channel, and tells you when a native assignment rule is also active.
- Four permission sets: Admin, Manager, User and Read Only.
Bring the rule nobody dares to change
Bosun is built and in pilot, and it isn’t publicly listed yet. Join the pilot: we model your current routing with you, and you help shape version 1.