Skip to main content

Communicating with Applicants in Engage

Reach the right people, without duplicate conversations getting in the way

Engage lets you message applicants directly through submittal chats, DMs, and channels. Who you can loop into a conversation depends on job assignments and permissions. If an applicant is already in another active conversation, Engage handles that automatically so you don't create duplicate threads.

When an Applicant Is Already in Another Conversation

If you try to message or add an applicant who's already active in a different conversation, Engage shows a takeover confirmation rather than letting two conversations run at once:

  • You're not currently in the existing chat:

    • Different submittal → you'll see a notice that the applicant is already in an active conversation for a different job.

    • Same submittal (regardless of phone number) → you'll see a notice that the applicant is already in an active conversation with the current participants. This gives you a chance to cancel and reach out to those participants directly before deciding to close their chat and start a new one.

    Best Practice
    Before proceeding with a takeover, consider reaching out to the current participants first — they may already be handling the applicant's request, and closing their chat will end that conversation.

    If you do proceed, nothing is lost. The original recruiter can start a new conversation with the applicant at any time, and the full history of every past conversation remains available:

    1. Chat with the candidate to get to the chat page

    2. Click the panel pull tab on the upper right-hand side to show the Submittal/Job quick reference tabs (see below)

    1. Click on the applicant's Submittal

    2. Go to the Activities sub-tab

    3. Find the relevant Engage Conversation entry and click into it to view the complete message history

  • You're already in the existing chat:

    • Same submittal, different phone number selected → you'll be notified the applicant is in a conversation using a different number, and proceeding will close the current chat and start a new one with the selected number.

    • Same submittal, same phone, no new participants selected → you're redirected straight into the existing conversation, no confirmation needed.

    • Same submittal, same phone, new participants selected → you'll see a notice that any selected participants will be added to the existing conversation.

If you proceed with a takeover, the applicant's current chat is closed, and a new one is created. The activity log reflects who closed the previous chat and who created the new one. This same behavior applies if you reach an applicant through a Sendout QuickLink and they're already in a conversation elsewhere.

You can mention an applicant in a chat even if they were previously removed from it.

Parent/Child Visibility (RPO Configuration)

Note: This section is for account configurers only. Please disregard if you are otherwise.

When this permission is granted to a recruiter, they'll see parent company recruiters assigned to the job as available options when starting or mentioning someone in a submittal chat, DM, or channel. Without the permission, parent recruiters won't appear at all — for that user, visibility is limited to child company employees and contacts with access.

Contacts (external, non-employee users) never see parent recruiters, regardless of this permission or job configuration — that visibility is tied exclusively to the recruiter-side permission and doesn't extend to contacts under any setup.

Did this answer your question?