Most Australian agencies do not sell one thing. A recruitment firm running permanent placements also has a contract book, and possibly an RPO offer sitting alongside both. An MSP selling managed services also sells project work, cyber audits and hardware procurement. An HR consultancy might run investigations, award interpretation and outsourced HR retainers from the same three people.
Each of those offers has a different buyer, a different competitive alternative, and a different vocabulary. The permanent desk is competing against the client's internal talent team. The contract desk is competing against another agency's rate card. Those are not the same conversation, and forcing them through one generic pipeline produces messaging that is technically accurate and commercially useless.
Multiple business contexts means running distinct value propositions from a single sales account, where each context carries its own workflow, competitive alternative and content language.
Why one pipeline breaks when you sell more than one thing
The failure is not dramatic. It is slow. A consultant writes a sequence for the permanent desk, it performs reasonably, and then it gets copy-pasted onto contract prospects with two words changed. Reply rates drop, nobody diagnoses why, and the team concludes that outbound does not work in that segment.
The client who is a warm contract lead and a cold permanent lead is one record with one status, and that status is wrong for at least one of the two relationships.
The second problem is measurement. If your contract desk and your permanent desk share a pipeline, you cannot tell which offer is actually working. Blended numbers hide the desk that is carrying the other one.
What a business context actually contains
A properly separated context is more than a tag on a record. It defines who you are talking to, what they would do instead of buying from you, and how you describe the work.
In recruitment CRM terms, that maps to a desk. In Kolvera, Desks let you define your target clients and have AI match companies automatically against that definition. A permanent construction desk and a contract technology desk are two separate desks with two separate matching criteria, not one desk with a filter applied afterwards.
Each desk learns independently. How Your Desk Learns uses Keep and Pass to teach the desk your taste, and nothing is ever silently thrown away. A company you passed on for the permanent desk might be exactly right for the contract desk, and because the desks are separate, that pass does not contaminate the other context.
Kolvera's Keep, Pass, Confirm and Hide controls operate across three blast radii, so a decision can apply to one desk or reach every desk. Marking something "not relevant" reaches every desk, while ordinary Keep and Pass decisions stay local. This lets one account run several business contexts without cross-contaminating each desk's learned preferences.
Splitting a context into the segments you actually sell
Most contexts are not uniform inside. A technology contract desk might really be four sub-markets: infrastructure, data, security and change. Those buyers do not read the same email.
Sub-Niches split a desk into the segments you actually recruit, so you can filter, tag and pitch each one separately. This matters most for content language. A security contract pitch that mentions clearance timelines and a data contract pitch that mentions warehouse migrations are different documents, even though both come from the same desk.
The Australian Bureau of Statistics reports that professional, scientific and technical services remains one of the largest employing industry divisions in the country, which is precisely why "technology recruitment" as a single context is too coarse to sell against. The segment is enormous and internally varied.
If you are unsure whether a desk is set up sensibly, Review My Desk reads the desk's configuration and hands back findings with one-tap fixes. That is a faster diagnosis than manually auditing why a desk keeps surfacing the wrong companies.
Contexts that run in the opposite direction
Not every business context points from you to a client. Candidate-led selling is its own context with its own competitive alternative, which is usually the candidate staying put or going direct.
Reverse Market Profiles build the candidate-side desk, mapping the employers who would hire a given candidate. That is a different matching logic to a client desk and deserves to be kept separate rather than jammed into the same list.
Float Campaigns support candidate-led outreach. Review the actual profile, attachments and message for identifying information, with appropriate candidate permission; a buyer response does not automatically authorise revealing identity.
Candidate-led and client-led outreach need different messaging. Reverse Market Profiles and Float Campaigns organise candidate-led work, but sharing a profile still requires review of visible information and appropriate permission.
Keeping messaging distinct across campaigns and calls
Once contexts are separated at the desk level, the outbound layer follows. Campaigns run multi-step AI email sequences with variants, tracking and outcomes, so each context can hold its own sequence rather than sharing one. Hot Lists give you curated, tiered collections that feed those campaigns, which is useful when a single context has a small set of high-priority accounts.
Customer calling uses a connected Ringover or Dialpad account on Pro or Scale. Native voice and SMS have separate restricted access. Check the dialler guide; a business context does not grant access to an internal calling pilot.
Where the contexts should still overlap
Business contexts organise work within the records you are permitted to access. Tenant and user-level isolation still apply; a context does not grant access to another tenant or another user's restricted records.
New email enrichment costs 2 credits per valid contact found. Fresh direct-dial and company-line phone finds cost 2 credits; cached company lines cost 1 credit, while an eligible number already on the account or a supported BYOK lookup may cost no Kolvera credits. Availability and plan gates apply. Check the current credit guide before running enrichment.
Use Tasks → Approvals for work that requires approval. Review campaign targeting, copy and sending rules before activation; an active campaign follows its configured rules rather than requesting a separate approval for every AI-generated message.
Practical setup order
Start with the offer that generates the most revenue and build that desk properly, including sub-niches and a run of Review My Desk. Add the second context only once the first is producing matches you would actually call.
Adding contexts before the first one is trained produces several half-configured desks that all surface mediocre matches. Adding them afterwards means each new desk starts from a working model of how your team makes decisions.
You can read more field notes on desk configuration and outbound on the Kolvera blog, or see how other Australian teams have structured theirs on the customers page.
Frequently asked questions
How many business contexts can one account run?
Kolvera does not limit you to a single desk, so you can create a desk per business context and split each one further using Sub-Niches. The practical constraint is your team's capacity to maintain them, not the platform. Most teams start with one well-trained desk before adding a second.
Will passing on a company in one desk affect my other desks?
No. Keep, Pass, Confirm and Hide operate across three blast radii. Ordinary Keep and Pass decisions teach the desk you are working in. Only marking something as not relevant reaches every desk, which is intentional for companies you never want to see anywhere.
Do I need separate campaigns for each business context?
Yes, if the contexts have different buyers or different competitive alternatives. Campaigns support multi-step sequences with variants, so each context can hold its own messaging. Hot Lists let you tier the accounts inside a context and feed them into the right sequence.
Can candidate-led and client-led selling live in the same account?
Candidate-led work can sit alongside client-led Desks. Review the profile, attachments and message for identifying information, with appropriate candidate permission; buyer engagement alone does not authorise revealing identity.
What does it cost to run multiple contexts?
Compare current Kolvera plans using the same billing term, seat requirements and expected usage. Pro and Scale have different allowances and feature gates. Annual rates require annual billing; Monthly plan credits reset each billing period; purchased top-up credits remain available until used.
Getting your contexts separated
If your outbound has flattened out and you sell more than one offer, the cause is often structural rather than creative. One pipeline carrying three value propositions will always produce messaging that fits none of them well.
Book a demo and we will walk through how your current offers would map to desks and sub-niches, including which ones are worth separating and which are close enough to share.