Overall Satisfaction with Jobscience
Jobscience is the primary CRM for our company. Upper management has full access to everything, and below are the specifics for each position:
- Recruiters use it to add candidates, upload resumes, log activity and submit candidates to positions.
- Account Managers use it monitor the status of candidates per job orders for each client.
- Recruiting Coordinators use it to create prospects, add contacts, delete candidate/client files and merging files and create packets for candidates.
- Dashboards: Jobscience allows each end user to have dashboards that are tailored for their position, and you're able to create several different dashboards.
- ActionGrid: This is a function we use within Jobscience that allows us to filter our settings to match candidates to available positions.
- Packets: We create packets with Jobscience via Conga that allow us to highlight crucial information for candidates.
- Logging activity: Their simple features allow us to keep track of every candidate record from many years ago.
- Resume: This feature allows us to see each resume for candidates. However, there are many times where we experience error messages.
- LinkedIn: This allows us to see the candidate's LinkedIn page as well, but we receive errors messages for this as well.
- Packets: Jobscience allows us to create packets via Conga, but sometimes there's a disconnect between Jobscience and Conga, giving us error messages.
- Logging information: Jobscience helps us keep track of every placement we've had.
- Prospects: Jobscience allows us to create prospects and gives us reminders to follow up with potential clients.
- Candidate data: Jobscience has endless storage for candidate profiles, allowing us to add 40K+ resumes.
We use Jobscience to add candidates, upload resumes, and have certain fields such as Name, Location, Compensation Details, Non-compete Details, Packet highlights, and of course the Resume field, all of which are required in order to create a packet to submit to our clients. These packets are created using Conga ActionGrid, so Jobscience allows us to input all the information, and it would be great if we could create a packet directly through Jobscience, but we require Conga ActionGrid, as that is then used in Adobe PDF to create the final packet.
Although Jobscience has features that could use more work, it is well suited for many scenarios, and I would definitely recommend it to my colleagues. The biggest benefit that I see with Jobscience is that, regardless of your job function, you are able to tailor the features within Jobscience, whether you are using it for sales activity or recruiting purposes.