​

Can Parsli parse to Leads?

 

No. It's not because we couldn't build it, it's because we don't think it was a good idea. In short, Leads are not people records. They are accounts, opportunities, and contacts all wrapped up in one spreadsheet-like object that has numerous workflows surround it that are not advantageous for recruiting processes.

​

Rather than bringing in candidates as Leads, use Accounts, Record Types and other segmentation values like picklists to create separation between candidate types. If you want to create workflow, build it directly on the Contact record (which can be customized per record type) or add it to your application workflow.

​

​

How do you search for candidates with specific skills?

 

This is important. After all, the reason you are parsing the resume is to find it later, right? We specifically built Parsli to work effectively with native Salesforce search. Our recommendation is to create Contact listviews that are filtered on attributes that bring the total number of Contacts to less than 2000 people (max) and then you can run full boolean searches in the listview search and find any skill that is in the resume.

​

For companies with a data warehouse or advanced search capabilities via AppExchange tools like Kona Search or Textkernel, we can also parse skills, education, and employment into their own objects/records. 
 

​

Will resumes that are already uploaded into Salesforce be available to see in the Viewer? Or would we have to add the resume again?

 

You will be able to see their resume right away (yay!) but the data won't be filled since they haven't gone through the parsing process yet.

​

If you do want to parse existing resumes as part of a migration OR if they are already in Salesforce, we have pre-built tools to parse in the existing resumes. Pretty cool.

 

Does the resume viewer work with both Attachments and Files?

 

Yes. It plugs right in and aggregates both types of documents. 

​

Can Parsli parse LinkedIn profiles?

 

Yes. The only caveat is that LinkedIn changes their formatting all of the time, so it's possible that their changes will temporarily break the ability to parse profiles over time. 

 

How does Parsli handle duplicates?

 

Two ways: First, we match on email addresses. Email addresses are great unique identifiers. Second, if the email doesn’t match and/or isn’t present, we look to your custom duplicate rules. Our app will provide a list of potential duplicates (with links to the records) when you upload a resume that matches a duplicate rule. 

 

Is it hard to set up?

 

No. It’s easy. For real. I have been in IT a long time and almost every app claims to be easy to implement, which makes me reflexively roll my eyes. I just can’t help it. “Yeah right! I am sure it is easy... just like running a marathon.” This one is actually easy.

 

Let me be specific about the steps: Download the managed package (2 min), Add candidate account and candidate record type in setup (3 min), add parser and viewer to Contact Lightning page (5 min), add Parsli fields to contact page layout (10 min if you mess around), add parsing to Home page and Lightning App (5 min). Optional: set up multiple emails for email-to-parse

 

Anything beyond what is listed above is extra-credit work (creating parsing reports, adding automation to the parsing object, creating listviews with the new Parsli fields, etc).

 

Can you view Word resumes in the viewer?

 

Yes. The only exception is that certain Docx resumes can’t render. This is due to the limitations in Salesforce and only applies to a small subset of files, but we want to mention it since I am sure it will happen.

 

What is the difference between parsing from the home page/utility bar and parsing on the candidate’s record directly? 

 

The only difference is that we don’t run duplicate rules or email matching when parsing from the contact directly. In either case, we will never overwrite critical information on an existing record, such as first and last name. 

 

Can it parse scanned PDFs?

 

No. Scanned documents are essentially pictures. Our tool (and all others currently available) doesn’t have the ability to extract data from a picture. We have aspirations to create this capability in the future, but it is not a trivial undertaking.

 

What kind of support does Parsli have?

 

This is something that we are passionate about. There is nothing more frustrating than bad support, and bad support seems to be the norm these days. 

 

When you reach out to us we will take a personal interest in helping you resolve your issue. Need to jump on a screen share? Let’s do it. Just need a quick response to your email? We will communicate clearly so you can get the answer you need and move on in your day. You found a bug? We will fix it as soon as we can and communicate updates with you in the meantime. Want to talk about football? We will only talk to Vikings fans. Just kidding… sort of :)

​

​

What would happen if we decided the tool wasn't for us at some point? Would we lose the data that we had entered?

 

No. You would retain all of your data, however the Parsli-specific custom fields would have to be replicated in your system so you could migrate the data to your own custom fields. This would likely be a 1-to-1 mapping exercise and wouldn't be a big deal for an admin to complete. The Files (resumes) that were uploaded and standard field data like “Name” and “Email” would all stay in your system and wouldn’t need any migration. None of the data is stored outside Salesforce and you own all of it