Candidate and client database with AI: ATS and CRM together

A folder stores documents; a database connects people, skills, notes and searches. Before choosing software, define the information needed to find a candidate again: role, experience, location, source and relationship status. A CV remains an attachment to the person rather than their only identity.

In Hice, keep the record and add information over time. You need not wait for a complete CV to record a promising profile. Record what you know and leave unverified information missing: an assumed availability can distort your next shortlist.

Open the LinkedIn profile you want to keep. Open the Hice extension and sign in, then choose to save a candidate. Review the preview: name, role, experience and other available information must belong to the right person. Complete required fields and confirm the save.

The operation concerns one profile at a time and starts with your choice. Browsing LinkedIn does not automatically collect lists. Once saved, the record is in your Hice database: add notes, a CV or a search link without retyping the profile from scratch.

Saving a person and submitting them to a search are different decisions. The database preserves the profile even when the current assignment ends. A search link adds context: which client request you are evaluating them for and what happens next.

Choose the search in the extension when the available context allows it, or complete the link in Hice. Always check the client and assignment. A general note should not replace the relationship: a structured link makes candidates, status and recruitment activities easier to retrieve.

Before searching for new people, consult the profiles you already collected. Use explicit requirements and verify that information remains current. Someone not selected for one assignment may suit another; preserve the reason for the earlier assessment without treating it as a permanent judgment.

Measure the whole process: saved profiles, complete records, contacted people and candidates actually evaluated. Record count alone does not measure database value. AI connected to Hice can help read accessible records, but missing information requires verification or a conversation with the person.

A company is the organization, a contact is a person, and an opportunity represents potential work. Putting everything in one cell makes it difficult to see who you know and which conversation you are following. People change roles, while companies can have several contacts and opportunities.

Hice connects these records. Start with the company, link the contact and add an opportunity when there is a concrete request. The commercial record remains useful before a deal exists: it preserves notes, context and activities without confusing an interesting profile with a qualified sale.

Open the contact's profile, launch the extension and choose to save a contact. Check name, role and company in the preview. Associate the contact with the correct company, using an existing record when available. You can also retain data from a LinkedIn company page. Confirm to save the individual record.

The practical benefit is less copying while retaining your review. If the source has no email or phone, saving does not automatically enrich those fields. Your first commercial activity may be completing the relationship and recording why the contact matters.

A record without a next step becomes another forgotten archive. After saving, add the research context, assign an internal owner and define an activity. Link an opportunity when there is a request; otherwise avoid inventing a value or closing probability.

Ask ChatGPT or Claude connected to Hice to prepare a briefing or proposed update from your notes. Specify that it is a draft and review the fields before confirming the write. Preparing a message does not mean the assistant has sent it.

Create or open your Hice account and use the extension package intended for your browser. Sign in through the extension, open a LinkedIn profile and try one save. Verify that the record appears in the correct workspace and that your user has permission to create that record type.

Package availability does not mean every browser uses the same installation method. Follow the instructions for the channel supplying the extension. If you cannot find an official link for your environment, ask Hice for it rather than installing an unrelated package with the same name.

Chrome and Edge use packages for the Chromium environment. Install the version distributed for your chosen browser, enable it and make its button accessible. After signing into Hice, open a profile and verify that the panel shows a coherent preview before saving.

If evaluating the extension for a team, also try a user with limited permissions. Seeing the button is not a complete test: create a candidate or contact, retrieve it in the database and check that saving the same profile again does not create a duplicate.

Firefox uses its own package and authorization flow. Follow the distributed version's instructions and grant the permissions needed for the extension to work on LinkedIn and Hice. Then try an open profile, checking the preview and save.

If the panel does not launch, verify that the extension is enabled in the browser profile you are using and that Hice sign-in is complete. A private window or company policy may require different configuration; do not confuse a browser restriction with missing profile information.

Safari uses the package intended for Apple's environment and activation in Safari extension settings. Follow the Hice distribution path for your device: uploading a Chrome package is not sufficient. Check site permissions and then try saving a profile.

Do not infer iPhone or iPad support from availability for Safari on Mac. Installation, device and site access should be checked against the distributed package. The operational criteria remain the same: a readable preview, an explicit user choice and a record retrievable in the Hice workspace.

Brave, Opera and Vivaldi also document support for Chromium extensions. This lets you evaluate a compatible package, but does not replace testing your Hice version in your browser.

Verify sign-in, preview, saving and record retrieval. For a team, also check company extension policies. Browser engine compatibility and distribution of a Hice package should be verified together; separate pages repeating the same instructions for every brand are unnecessary.

Hice checks record identity and can reject a new save when it detects a duplicate, for example the same LinkedIn profile or an email already recorded. Matching names need attention: identical names do not prove that two records describe the same person.

When a warning appears, find the existing record and check company, source and contact details. Complete that record rather than changing the name to bypass the check. When evaluating software, examine how duplicates are identified and handled rather than assuming every incomplete identity can be recognized.