September 29th, 2023




We as a consultancy are growing so we are constantly looking for new people to join our team. Even if innovation is at our core, the digitalization of the recruitment process appears to be tricky for us. I guess it is challenging for any smaller organization, where there is only one recruiter in place, and the workload is not big enough to implement and maintain a dedicated recruitment system.

In this article, I illustrate how Formstack for Salesforce can facilitate this process. Formstack is a powerful productivity solution that can be used for different industries and scenarios. The use case described below is just one of many possible applications of their product named Formstack for Salesforce. I am not going to teach you how to set up the recruitment process or how to build a data model[1] in Salesforce. Rather I want to showcase the capabilities of the solution, using the example of a small company (up to 20 employees) that has a Salesforce org.

The recruitment process that I am going to cover includes the following sub-processes:

  • Job application
  • Interviewing a candidate
  • Job offers
  • Collecting employee information and start of onboarding
  • Challenges

    The challenges faced before implementing Formstack were as follows:

  • Lack of data centralization, standardization, and visibility. The recruiter keeps notes on candidates in both the LinkedIn Recruiter platform and the job board, so the information about applicants can be duplicated. Founders miss an overview of the application pipeline; and the fact that each job board service applies different status names or tags also doesn’t help.
  • There is no historical data on interview feedback available. After some time, it becomes difficult to remember why a candidate was rejected or placed on hold. The recruiter doesn’t have an overview of all the interview feedback thus missing an opportunity to learn from it and to make her search more precise.
  • A large amount of manual work for the recruiter. A job offer is drawn up each time by simply changing the existing template, which is not only time-consuming but also an error-prone action. All job offers that are sent out are buried in the recruiter’s email box so when it is time to create a job contract, all involved parties must refer to the email trail. All documentation pertaining to the candidate is saved in cloud storage such as SharePoint which could also be a time-consuming exercise.
  • A candidate or alternatively, a future employee might find the process of completing Word documents for onboarding timewasting; in addition, it is potentially a duplication of data that is already known to the company.
  • All forms are stored on SharePoint, so it is not easily or quickly accessible. In this case, an employee would have to manually update the document, and send it to the recruiter, so the outdated version can be replaced with the newer updated version.
  • Job application

    In the Formstack app in Salesforce I have created a form named Developer application. A form means that a user fills in some fields and the data entered is saved somewhere. In this case, applicants will fill in data about themselves such as name, contact details, motivation, salary expectations etc. This data will end up in Salesforce on the Contact and Job application records.

    Form settings. The form consists of fields, so the question is which fields should show up on my form? This depends on where I want to save the data obtained from the form. I want this to be saved in Contact and Job application records, therefore, the objects are specified in the form settings. There are other settings available such as which page to show after submission of the form and how to save the submission file in Salesforce. There is also a possibility for an applicant to save a form and return to it later by clicking a link in their email.

    Form builder. Next, I want to put together my form by choosing the fields and the order in which they should appear. As you can see, it is a drag-and-drop experience. I can add sections to my form, rename the labels, and add default values and placeholder text.

    Not only can Salesforce object fields be added, but I can also add special buttons, such as File upload, Payment, Signature, Image, and Captcha.

    Fields in the form can behave according to the given logic. For example, if an applicant chooses a location country different from the Netherlands, the question “Are you ready to relocate to the Netherlands?” becomes visible and required.

    I can style and brand the form as much as I like by changing fonts, adding background images, etc. It can easily be saved as a template for future use.

    Publish options

    I want this form to be publicly available so for a publish option I can use either embedded code or a link. Note that the link is static and will remain the same even if I change the form.

    Form submission

    I am publishing the link on the company website, job boards, LinkedIn, and the recruiter and I are patiently waiting for the first submissions. The recruiter can track submissions by navigating to the Submission Dashboard in the Formstack app. All submissions, even failed ones, are visible here. It will also show why a submission has failed. If I click on the Recordsign, I am taken to the Salesforce org, where I can see the record that this form has created.


    At this point, we are enjoying these business benefits:

  • The data is centralized in Salesforce and all stakeholders can keep track of applications in real-time; one platform, hence a smoother user experience.
  • The recruiter saves time by having the exact data she needs without looking for such information in applicants’ CVs or asking applicants personally; therefore, she can qualify applicants faster and better without reaching out to them.
  • Types of data that applicants are asked to provide can be easily configured and reported on.
  • An applicant has a good impression of us since the application form is branded and conveys the company’s spirit.
  • It is magical for me, how an external user who probably doesn’t even know what Salesforce is, can still create records directly in Salesforce by simply filling in the form published on the internet. No duplication of work, and no need to manually transfer the data, it just allows users to complete the forms and the record miraculously appears in Salesforce.

    Feel free to reach out to us if you want the same magic to happen in your org! We are certified Formstack partners, and it is our pleasure to let you free from mundane tasks so you can spend more time on things you love!

    This is all for now! In the next part, I will show you how to create a form that will update a specific record in Salesforce. We’ll show you how an interviewer captures interview feedback using forms. Stay tuned!

    Gauhar Kassymbek
    Gauhar is a passionate Salesforce consultant specialising in customer service and recruitment domains. She holds an MBA degree, so she feels comfortable in the business analyst role too. Gauhar is from Kazakhstan and lives now in Amsterdam.

    [1] If you’re still interested, the custom objects created in Salesforce to meet the requirements of the solution are

  • Job
  • Job Application (junction object between Contact and Job)
  • Interview Feedback and Job Offer, both related to the Job application