Skip to main content

Advance Nodes

Khibtiya Afreen
Updated

Table of Contents

Overview

Overview

Below is a list of chatbot nodes available in Sense, along with a brief description of how each node is used within a chatbot flow.

1. Job Match Node

The Job Match node helps candidates find relevant job openings based on their provided information or predefined criteria.

  • Purpose: To display job matches to candidates based on criteria defined by the administrator.
  • Criteria Configuration:
    • Criteria are based on values from "discover" (e.g., worksite options, skills).
    • For Inbound bots, these criteria can be mapped to node variables, meaning the job matches can be dynamic based on a candidate's answers to earlier questions (e.g., matching jobs based on a candidate's preferred worksite or location). 
    • For Outbound bots, we can select both node variable and ATS variable for defining job matching criteria. 
    • For location-based criteria (city and zip), additional result options appear: "Best match," "distance, closest," or "farthest".
  • Display Options:
    • A message can be configured to show when job matches are found (e.g., "We found job matches for you").
    • You can specify the number of matches to display initially (3, 5, 7, or 10).
    • Matches can be displayed with bullet points or numbers.
    • "Show all jobs link": Allows candidates to view more matches beyond the initial displayed number.
    • "Enable job link detail page": Adds a link to the job description page on the client's website for each displayed job.
    • No Matches Available: A configurable message can be shown if no jobs match the criteria, or the option to display the most recent jobs posted by the agency.

2. Live Chat Node

The Live Chat node allows for the transfer of a conversation from the automated chatbot to a human agent.

  • Purpose: To connect a candidate with a real person (a "live agent") for more complex or personalized assistance.
  • Routing Rules: Conversations are routed to specific "queues" (teams of agents) based on predefined rules.
    • Rules can be configured based on ATS variables or node variables.
    • A common use case is to route candidates to different teams based on their location (e.g., Bangalore agents to a different queue than Mumbai agents).
    • A default queue can be set if no specific routing rules are met.
  • Messages: A configurable message can be displayed to the candidate while they are being connected to an agent.
  • Outcomes and Branches: Similar to the Meeting node, the Live Chat node can lead to different branches based on the connection outcome:
    • Success: The candidate successfully connects and has a conversation with a live agent.
    • Failure: The connection was unsuccessful due to an error, agent unavailability, or being outside business hours.
    • Each branch allows for a distinct follow-up flow.
  • Agent Interface: Live agents access these transferred chats under "Conversations" in the left-side menu of their Sense platform. This feature may be enabled via a specific flag.

3. Meeting Node

The Meeting node integrates with Sense Scheduling, allowing candidates to book meetings directly through the chatbot.

  • Purpose: To facilitate meeting scheduling within the chatbot flow.
  • Templates: For inbound bots, static templates are fetched from the meetings team, such as "panel interview," "round robin," or "multi-event". For outbound and pre-screening bots, dynamic templates are also available.

Static template:

Dynamic template:

  • Mandatory Information: For sourcing bots, the candidate's email, name, and phone number must be mapped from existing nodes in the chatbot flow to successfully schedule a meeting. For outbound bots, there’s an option to map it to an ATS variable or Node variable.
  • Customization: Optionally, you can define a different meeting title and details than what is pre-configured in the scheduling template.
  • Outcomes and Branches: After a candidate interacts with this node, the flow can branch into three different paths based on the outcome:
    • Meeting scheduled: The meeting was successfully booked.
    • No available slots: No meeting slots were available.
    • Booking error: An error occurred during the booking process.
    • Each outcome can lead to a different subsequent path in the conversation (e.g., show more information after success, suggest coming back later for no slots, or prompt to try again for an error).

Related articles