# Recruitment agencies CRM | Practical customer journeys | 121 > Plan a respectful recruitment agencies CRM journey with practical ownership, consent, escalation and clear boundaries around sensitive decisions. For recruitment agencies, the useful unit of work is a respectful customer or member journey with explicit consent, escalation and human judgement. This design avoids turning sensitive context into an automated decision. Consider this practical starting point: a client briefs a vacancy while candidates arrive from several sources with different consent and availability. A configured CRM can keep the contact, context, owner and next action together, while the business still decides which qualified recruiter reviews fit, conflicts, consent and the appropriate next step. ## A visible person-centred enquiry from start to finish Fictional Northstar Recruitment example. It demonstrates an operating pattern for recruitment agencies, not a customer result, professional recommendation or promise that every capability is included. ## Capabilities explained ### Companies Groups people and related information around an organisation rather than treating every person in isolation. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Helps business-to-business teams see contacts in the context of the company they work for. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Contacts Stores a person or lead with contact details, activity, ownership and related records. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Gives a team one place to understand who a customer is and what has happened. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Opportunities Represents a potential sale or deal linked to a contact, value, owner and pipeline position. **How it works:** Tracks a potential deal, stage, owner or task using configured pipeline and record rules. **Why a business would use it:** Shows which customer conversations are active commercial work rather than general contacts. **Limitations:** Pipeline position is only reliable when users and workflows update it consistently. **Human responsibility:** A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status. ### Custom fields Adds structured fields to supported record types so a business can capture information it actually needs. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Replaces important notes and spreadsheet columns with searchable, reusable data. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Conversations inbox Brings supported connected message threads into a shared operational inbox. **How it works:** Handles an eligible customer interaction through a configured inbox, number or connected channel. **Why a business would use it:** Helps a team see the customer history and coordinate replies from one working view. **Limitations:** Delivery, message types, geographic coverage, approval and charges vary by channel and provider. **Human responsibility:** A person must own sensitive conversations, failed delivery and any situation outside the approved script. ### Tasks Creates assigned, dated and optionally recurring actions against contacts or opportunities. **How it works:** Tracks a potential deal, stage, owner or task using configured pipeline and record rules. **Why a business would use it:** Turns the next step into owned work instead of leaving it inside notes or inboxes. **Limitations:** Pipeline position is only reliable when users and workflows update it consistently. **Human responsibility:** A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status. ## What recruitment agencies actually need the CRM to hold Northstar Recruitment is a fictional example used to make the workflow concrete. The aim is not to reproduce a sector package, but to show the minimum useful context for a team that needs keep client and candidate relationships distinct, assign activity and prevent important follow-up being buried in individual inboxes. ### The customer situation Imagine a client briefs a vacancy while candidates arrive from several sources with different consent and availability. Northstar Recruitment records the customer’s own account before interpreting it. For this recruitment agencies team, that prevents a short message from becoming a confident but unsupported category, price or promise. ### The working record The useful record contains client organisation, hiring contact, vacancy reference, candidate contact, source, consent, recruiter, current administrative stage and next action. At Northstar Recruitment, those fields must help a person respond, decide or understand the next handover; extra detail collected merely because a field exists adds risk and maintenance. ### The ownership question Northstar Recruitment names the recruitment manager or another responsible colleague against the next action. The Northstar Recruitment shared view is useful only when the team can tell who must act, by when, and what happens if that person is unavailable. ### The decision that stays human A person decides which qualified recruiter reviews fit, conflicts, consent and the appropriate next step. On this recruitment agencies journey, CRM presents records, reminders and history without turning incomplete information or silence into approval. ## Move the recruitment agencies conversation without losing context A workable starting journey for Northstar Recruitment is Vacancy or candidate received → Details and consent → Recruiter review → Interview coordination → Outcome and follow-up. For recruitment agencies, each change should mean something observable to the team and customer rather than acting as a decorative pipeline label. ### 1. Capture vacancy or candidate received For Northstar Recruitment, capture starts with the source, the customer’s words and enough contact detail to reply. The first response should set a realistic expectation and ask only for information needed now; it should not imply that which qualified recruiter reviews fit, conflicts, consent and the appropriate next step is resolved. ### 2. Establish details and consent Northstar Recruitment asks the owner to check duplication and fill the smallest important gaps. Keep client and candidate relationships distinct, assign activity and prevent important follow-up being buried in individual inboxes becomes the operating goal, rather than sending every recruitment agencies enquiry through one sequence regardless of context. ### 3. Record recruiter review At Northstar Recruitment, the team records the human decision, its basis and the promised next action. If information is missing, the request names it and its reviewer; if work should stop, a clear reason is more useful than leaving this recruitment agencies record open indefinitely. ### 4. Complete interview coordination and outcome and follow-up For Northstar Recruitment, later stages preserve the customer commitment, operational handover and outcome. Its recruitment agencies team closes or defers work deliberately, records why, and gives future follow-up a date and purpose instead of keeping an undifferentiated list of old leads. ## How Northstar Recruitment could use the pattern in a normal week This example uses fictional people and activity. It demonstrates how a configured CRM might support a recruitment agencies team while keeping account availability, detailed configuration and service scope subject to agreement. ### The first response Northstar Recruitment receives the initial enquiry described above. The record is assigned to the recruitment manager, the customer receives an acknowledgement that matches the actual response process, and the owner sees the missing information and a dated action rather than a vague notification. ### The awkward case The same week, an automated rule that could unfairly infer suitability or reject a person from incomplete or sensitive information. At Northstar Recruitment, the ordinary sequence pauses while a person reviews the context and records the decision. For this recruitment agencies workflow, the failure route matters because automation should expose exceptions rather than quietly continuing. ### The handover evidence At each handover, Northstar Recruitment keeps the source, time, owner, status change and next commitment. Northstar Recruitment attachments or sensitive details remain only where the approved design permits them. A completed recruitment agencies task proves that an action was recorded, not that the underlying judgement was correct. ### The weekly view The team reviews records missing consent or ownership, interviews awaiting confirmation, client feedback overdue and inactive records due for retention review. For recruitment agencies, those measures prompt investigation rather than promise performance. They help Northstar Recruitment only when stages are updated consistently, exceptions remain visible and someone corrects stale or misleading records. ## Keep the recruitment agencies workflow useful after launch The safest recruitment agencies design is modest: a small number of meaningful fields, an owner, an observable next action and a review rhythm. Northstar Recruitment would test the ordinary path and the exception path before relying on either. ### Professional and operational boundary The CRM may organise records and communication; people remain responsible for fair assessment, lawful processing, reasonable adjustments and employment decisions. ### Exception handling An automated rule that could unfairly infer suitability or reject a person from incomplete or sensitive information should be visible to a named person. Northstar Recruitment needs a stop, escalation or manual route so that delay, missing data or unusual circumstances do not produce an inappropriate automatic message. ### Access, data and communication Use the minimum information required for this recruitment agencies journey. Confirm Northstar Recruitment roles, channel consent, retention, export access and connected suppliers in the customer’s own account. Keep sensitive or formal recruitment agencies records in the approved system for their purpose rather than copying them into CRM notes. ### Review rhythm Northstar Recruitment reviews the workflow daily for active interviews and weekly for every open vacancy and candidate follow-up. The Northstar Recruitment review checks a representative journey, stale records, failed actions, user access and whether fields still support a real decision. Any material recruitment agencies change should be tested before it reaches ordinary customer communication. ## Frequently asked questions ### What is the most useful first CRM workflow for recruitment agencies? For recruitment agencies, start with one common enquiry from capture to a recorded outcome: Vacancy or candidate received → Details and consent → Recruiter review → Interview coordination → Outcome and follow-up. Keep Northstar Recruitment’s first version narrow enough that the team can name the owner, test exceptions and see where a customer is waiting. ### What should recruitment agencies avoid automating? The CRM may organise records and communication; people remain responsible for fair assessment, lawful processing, reasonable adjustments and employment decisions. Recruitment agencies should also avoid automatic follow-up where consent, urgency, safety, suitability, a complaint or a vulnerable person needs a considered response. ### Which information belongs in a recruitment agencies CRM record? Use information that supports the current relationship and next action: client organisation, hiring contact, vacancy reference, candidate contact, source, consent, recruiter, current administrative stage and next action. At Northstar Recruitment, detailed or sensitive information is not collected simply because a custom field exists, and an authoritative professional or operational record is not duplicated without a defined reason. ### How should a recruitment agencies team know the workflow is working? Review records missing consent or ownership, interviews awaiting confirmation, client feedback overdue and inactive records due for retention review. Then inspect examples behind the figures. For recruitment agencies, a dashboard can expose patterns but cannot prove service quality, causation or correct professional judgement without reliable data and human review. ## Related CRM pages - [/crm/solutions](https://121.direct/crm/solutions) - [/crm/demo](https://121.direct/crm/demo) - [/crm/features/customer-management](https://121.direct/crm/features/customer-management) - [/crm/features/conversations](https://121.direct/crm/features/conversations) - [/crm/guides/crm-governance](https://121.direct/crm/guides/crm-governance) - [/crm/solutions/recruitment-agencies](https://121.direct/crm/solutions/recruitment-agencies) - [/crm/solutions/education-training](https://121.direct/crm/solutions/education-training) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.