These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Recruitment CRM
- Features
- Client accounts
Client accounts
Keep each hiring client's identity, contact and eligibility decision together.
OverviewActive client accounts×
Recruitment CRM · Client accounts
New
Active client accounts
Accounts
| Name | Code | Contact name | Eligibility note | Organization | |
|---|---|---|---|---|---|
| Account 401 | CDE-776 | Contact 499 | EN-182 | ORG-1281 | |
| Account 399 | CDE-628 | Contact 156 | EN-727 | ORG-9293 | |
| Account 872 | CDE-241 | Contact 736 | EN-223 | ORG-1689 | |
| Account 390 | CDE-435 | Contact 195 | EN-425 | ORG-4868 | |
| Account 570 | CDE-354 | Contact 390 | EN-361 | ORG-2363 |
6 of 6 records
Account 401Accounts · ACC-24239
CodeCDE-776
Contact nameContact 499
Eligibility noteEN-182
OrganizationORG-1281
What you can do
Begin with an eligible client
The account is the client side of a hiring opportunity. It carries a name, code, contact name, address and eligibility note within an organization. A Relationship Owner uses it to identify who requested the work; an App Administrator maintains the client record. The active flag gives the team a clear starting point when it decides which clients may receive new attention.
A returning client may ask about a new operations role. The owner can find the existing account by code, read its contact and eligibility note, then open an opportunity against that account. The new request has its own subject, owner and expected close date, while earlier opportunities remain tied to the same client. This keeps a change in hiring need from becoming a duplicate client account.
How the work is organized
- Client identity. Use the account name and code to identify the hiring organization in conversations and imports.
- Eligibility. Read the active flag and eligibility note before an owner accepts a new hiring request.
- Organization scope. Keep the account under the correct organization so its opportunities and mandates have the right context.
What to agree during setup
Agree who can create and update accounts, how a client code is chosen, and what the eligibility note should say when an account needs review. Decide whether the contact name is a primary hiring contact or a shared client desk. Keep that convention consistent: the account has a contact name, while the activity history sits against opportunities. If a client has several hiring requests, create an opportunity for each and retain the shared account identity.
Set a simple rule for inactive accounts. Before an owner starts a fresh opportunity, the App Administrator should check the reason for the inactive flag and update the account only after the business decision is made. The owner should confirm the organization on the account and opportunity, especially when a recruitment team operates for more than one organization.
Check the handoff on an actual case
Take a client with an existing account and a new position request. Ask the App Administrator to confirm the code, contact name and eligibility note. The Relationship Owner creates an opportunity linked to that account and records the first call. The Sales Manager should be able to trace the opportunity back to the correct account when reviewing the mandate. Repeat with an inactive client to make sure the team resolves eligibility before progressing. Check that a second request uses a second opportunity under the same account.
What your team sees
- Active client accounts — Hiring clients ready for account review, with the contact and eligibility note beside the name.
- Open hiring pipeline — Open requests show the client account beside the owner and current stage.
Follow the work through
Start with client intake, then follow the request into mandate review. Confirm ownership and access in roles.
What it keeps track of
Data model- Accounts
- Client hiring accounts eligible for recruitment opportunities
- Organizations
- Client and internal organizations that own recruitment records
- Opportunities
- Client hiring opportunities tracked through the recruitment lifecycle
Who uses it
Permissions- App Administrator
- Maintains client accounts and organization details.
- Relationship Owner
- Selects the account for an opportunity.
- Sales Manager
- And Auditor inspect the client context when reviewing outcomes.
Set up Recruitment CRM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.