7. Everything in Action

Sandbox vs Production End-point

There are two integration endpoints from a Partner perspective. Notice that the Fountain User (Customer) will not use the Sandbox endpoint to do any testing. Users will only use the Production end-point to create a Fountain workflow. Thus, it is of utmost importance that the Production endpoint works perfectly for a better User experience.

Selecting Correct Partner Options

Partners may have many packages. Each package may provide a service that is different than other packages. When setting up rules, please select the proper package from the Stage Option Type dropdown menu.

Configuring Partner Stage Rules

Users configure rules in Fountain that control the movement of the applicants. Partner Stage is no exception. One great benefit of the partner stage is, it allows users to configure rules to move applicants forward or drop them from the funnel. Rules can be created using Partner Status, or Partner Details. Depending on your implementation you can set up the rule to move the applicant through the funnel.

For example, if you've implemented the Partner Status, the rule in the Partner Stage will be something like this:

📘

Partner Status, Rules, and Fountain Sign Off

Applicant Experience

This section describes the experience of an applicant during the application process. There are two different experiences an applicant will go through depending on the integration.

iFrame Experience

For the iframe integration, the applicant will remain in Fountain's workflow with the partner portal embedded within an iframe. You should be able to enter necessary data in the iFrame. Once all data is entered properly, you should automatically move to the next stage configured in the Workflow Editor. To ensure the integration is working properly, you should see the updated Partner Status from your system showing up on in the Applicant Table.

👍

Recommended

We recommend iframing for the best applicant experience.

If there are security policies preventing an embedded iframe, redirect to the partner, then back to Fountain for the applicant to continue their application is available. Please reach out to partners@fountain.com to enable the redirection.

Asynchronous Experience

If the integration was built only to exchange information between Fountain and the partner system, then applicants will not see a partner web portal as they go through the application process. Everything happens in the background. To ensure the integration is working properly, you should receive the Partner Status on the applicant to indicate the exchange of data between Fountain and partner system.

📘

Data Exchange

The asynchronous experience is rarely preferred. It's meant as a data-exchange.

The applicant shouldn't need to take any additional action (consent, data collection, etc). If needed, prefer the iframe (or redirect) experience.

Recruiter Experience

Now that you've completed the journey as an applicant, it's time to verify whether everything is working as expected. As a recruiter using the Fountain System, there are four major things to check:

Partner Status label Updating Properly

After the applicant has gone through the whole application process, a recruiter wants to ensure that he is seeing the updated Partner Status label on the applicant. This might seem trivial but it plays a major role in managing applicants in the Fountain system. Imagine hiring 10,000 applicants a month.

Rules Working Properly

The Partner Status label and the Partner Stage Rules go hand in hand. When the admin is trying to configure the workflow they want to move Applicants to the correct stages of the Fountain funnel automatically.

Partner Details Displaying Properly

If you are using Partner Details to share additional information on applicants, the details should show up in the Applicant Profile.

  1. First click on an Applicant to go to Applicant Profile
  2. Then click More [Partner] Details button to view pop-up modal.
    1. It should contain all additional details in a bulleted format. If you are sharing any additional links on the Partner Detail, they should show up accordingly.

Redo Button Working Properly (If Implemented)

If you've implemented the Redo functionality, the Applicant should move to the original stage they were on when the Redo button is clicked. The Applicant will get an email with a link to redo the stage. Upon clicking the link, they will land in the stage. The applicant will go through the application process for that stage as usual. For the Redo button functionality, the status labels should be reset to Null. All Status Labels will be tagged by treating the applicant as a new applicant.