Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

    English (US)
    MX Spanish (Mexico)
    CA French (Canada)
    US English (US)
    • Home
    • Daily Processes
    • Candidate Profile
    • Candidate Summary Builder
    • Multi-Application feature

    Multi-application use cases

    Written by Lindsey Stanifer

    Updated at August 19th, 2026

    Contact Us

    If you still have questions or prefer to get help directly from an agent, please submit a request.
    We’ll get back to you as soon as possible.

    Please fill out the contact form below and we will reply as soon as possible.

    • Getting Started
      Setting up your calendar Managing your alerts Additional Settings
    • Daily Processes
      Candidate Inbox Candidate Profile My Calendar/Calendars Browser Extension My Jobs Approvals Engine Manual and Common Scheduling Practices Form I-9 processes Troubleshooting Forms & Offers
    • Candidate and User Engagement
      Campaigns Conversation Builder Surveys Channels Talent Community Voice Web Management Analytics & Reporting Data Privacy Career Sites
    • Management Tools
      Job Management Scheduling Security Journeys Content Management System (CMS) Multiple Brands Workflows Users, Roles and Permissions Data Feeds Location Management Lookup Tables Assistant Messaging Company Information Client Setup System Attributes Integration Center
    • Contextual AI
      Knowledge Training Library
    • Conversational Events and Campus
      Conversational Events Campus Events
    • Employee Communications
      Communications App Employee Management
    • Release Notes
      2025 2026
    • Workday Feature Descriptions
    + More

    Table of Contents

    Use cases Use cases based on candidate entry points Regular conversations Campaigns Chat-to-Apply Events Conversational ATS Integrations Manually added WhatsApp

    Multi-application logic identifies when candidates return and complete multiple engagements/applications with your organization.


    Use cases

    • Users are able to easily view and manage their returning candidates' data and perform necessary actions on individual conversations/ applications.
    • Candidates are able to easily navigate their engagements with your AI Assistant as they build a history with an organization.

    Use cases based on candidate entry points

    Regular conversations

    Desired outcome:

    • If the candidate is a returning candidate, after the process of being verified, the candidate will have one profile in the CEM with a dropdown to access the multiple conversations.
    • The selection of a conversation should display the details of the conversation.

    Enable re-apply in regular conversations:

    For regular conversations, there needs to be a prompt along with the “Thank you” message that allows the candidate to submit interest in another job group/ location.

    1. If on widgets/ landing sites:
      • If the response is Yes, then the conversation will restart from the screening question (Area of Interest). The candidate's contact information will be saved and used for the new application.
      • In the CEM, a new conversation will appear but will be nested within the main candidate's profile.
    2. If on SMS (short code engagements):
      • If the response is Yes, then the conversation will restart from the screening question (Area of Interest). The candidate's contact information will be saved and used for the new application.
      • If the candidate resets the conversation by typing New or the short code keyword, your AI Assistant should kickstart the verification process by sending a code. (Name or email verification)
     
     

    Campaigns

    Desired outcome:

    • If the candidate is a returning candidate, after the process of being verified, the candidate will only have one profile within the CEM. A dropdown will show multiple conversations.
    • The selection of each conversation should populate with the details of the new conversation.
    • If it's a .csv upload, duplicate candidates need to be identified and merged with the candidate's profile. However, will have a unique conversation ID.

    One-time campaign & drip campaign types:

    If the campaign is a:

    • Conversation type, then the system will always create a new conversation ID. Use the same logic as the regular conversations.
    • Scheduling type, then the system will always create a new engagement.

    How to identify and act upon multiple conversations with candidates:

    For campaigns candidates can be created in 2 ways:

    • CSV upload – In this process, if the candidate in the file matches an existing candidate, then the same logic of tagging the candidate’s profile will apply. Each interaction will have a unique conversation/engagement ID. They will show as nested conversations for the main profile.
    • Using the candidate pool – In this process, since the campaign is sent to the existing candidates in the system, the profile ID will remain the same and a new conversation ID will be created.
      • Note: Either case they will show as nested conversations for the main profile.
     
     

    Chat-to-Apply

    Desired outcome:

    • For non-integrated solution:
      • The candidate should be able to search for a new job and apply after applying for a job.
      • The second Apply Now action results in redirecting to the job application page.
    • For integrated solutions:
      • Only handle one application submission

    To re-apply with chat-to-apply:

    1. Within the same session: A candidate applies within 60 minutes of applying with your AI Assistant.
      • For integrations, if you are using multiple Chat-to-Apply conversations, the second application will go directly to the screening. questions.
    2. A new session: A candidate applies after 60 minutes of inactivity.
      • Your AI Assistant will proceed with the verification process by requesting the candidate's name and contact information. Upon verification, your AI Assistant will proceed with the screening question.

    Note: For integrations with their own verification process, it is important to discuss how the second conversation's information will pass through to your integrated ATS.

     
     

    Events

    Desired outcome:

    • For all event types, the event inbox should only show the candidates who have completed an event conversation. If the candidate starts a new interaction within the same event, the Candidate Profile ID (re-apply will be applied) will remain intact; however, a new interaction ID (new conversation) will be created.
    • The new interaction will show as a new selection in the Candidate Profile dropdown within the event inbox.
      • Note: The event inbox will display only the event interactions. All other interactions submitted by the candidate will be visible in the main inbox.

    To re-apply:

    • The candidate can register for different events hosted by the client via a landing page or SMS.
    • Within an event, the candidate can be scheduled for only one active interview session.
     
     

    Conversational ATS

    Desired outcome:

    • The largest use case for hire is identifying a returning candidate. After the process of being verified, the candidate will have one profile within the CEM with a dropdown to access multiple conversations,
    • The selection of a conversation should display the details of the conversation.
    • The job search conversation will only appear on the Job Details page. Therefore, there will not be a Chat-to-Apply use case, as each interaction will automatically create a new Candidate ID but will retain the Candidate Profile ID.

    To re-apply:

    • The only way a candidate can re-apply to a job is by searching and applying for the job via the career site or texting the keyword to the short code number.
      • Note: Users will only be able to view the conversations that they have permission to view.
     
     

    Integrations

    • If the integrated ATS is SuccessFactors, then your AI Assistant will not send a verification code.
    • If the integrated ATS is not SuccessFactors, then your AI Assistant will send a verification code. 
     
     

    Manually added

    Desired outcome:

    • When a candidate is manually created in the CEM, and their the email matches with an existing candidate, then  the user will be prompted to confirm the merger of the candidate's two profiles.
      • Upon confirmation, a new Candidate ID will be created, but the profile ID will be inherited from the primary profile.
      • If the user disregards, then a new Candidate Profile ID and a new Candidate ID will be created.

    To re-apply:

    • The only option is to manually add the candidate to CEM.
     
     

    WhatsApp

    Desired outcome:

    • Identify duplicate candidates.
    • Decide next steps for the candidate.
      • Note: At any point in time, the candidate can be hired for only one role.

    To re-apply:

    • The WhatsApp Phone number will always be unique per candidate.
    • Verification is possible. However, the code itself is sent via SMS (longcode).
    • Business WhatsApp phone numbers can be used to chat with multiple candidates.
     
     
    conversational ats integrated ats

    Was this article helpful?

    Yes
    No
    Give feedback about this article

    Related Articles

    • Multiple job locations for standard jobs
    • Create a multi-location job
    • Additional Details for multi-location jobs: Adding and using a job data package
    • Multi-Application: Customize the application selector

    Copyright 2026 – Paradox.

    Knowledge Base Software powered by Helpjuice

    Expand