Rover AI

Overview

Rover is Leadline's built-in AI assistant — purpose-built for hiring teams to execute tasks, answer questions, and run multi-step workflows directly within the platform using plain language. Rover is not a generic chatbot. He is a platform-integrated assistant that takes action inside Leadline on your behalf.

What is Rover?

Rover is Leadline's AI assistant, built exclusively for internal hiring teams and HR staff. He lives inside the Leadline platform and helps users accomplish tasks — from answering product questions and generating content to executing complex multi-step workflows — all through plain language conversation.

Rover is action-first. When you tell Rover to do something, he does it — asking only for what he genuinely needs and nothing more.

Why Does Rover Exist?

Rover exists to make the Leadline platform faster and more accessible for hiring teams. Rather than requiring users to navigate menus, fill out forms, or learn the platform manually, Rover allows users to accomplish tasks by simply describing what they need in plain language.

Rover exists to:

Reduce time-to-action — tasks that would take several clicks and form fills can be completed with a single prompt
Lower the learning curve — users can interact with Leadline without needing to know where every feature lives
Scale hiring operations — agentic workflows allow teams to accomplish in seconds what would otherwise take hours of manual work
Surface information quickly — users can ask Rover questions about the platform, candidates, or positions without leaving the conversation

What is the Difference Between a Basic Flow and an Agentic Workflow?

Rover supports two types of requests — Basic Flows and Agentic Workflows. Understanding the difference helps set the right expectations for what Rover will do and how long it will take.

Basic Flow A Basic Flow is a single request with a single outcome. Rover takes one action on one object and returns a result. These are fast, immediate, and scoped to a specific task.

Examples:

"Rewrite the job description for my Foreman position"
"What are the required fields when creating a position?"
"Send a reminder to John Smith to complete his application"

Agentic Workflow An Agentic Workflow is a multi-step sequence where Rover takes a series of coordinated actions across multiple objects to complete a compound task. These involve planning, executing multiple steps in order, and reporting on the result. Rover will always summarize the plan and ask for your confirmation before beginning an Agentic Workflow.

Examples:

"Here are 10 job requisition documents — create a position in Leadline for each one"
"Find me all candidates with 3+ years of construction experience who applied to my Tampa positions in the last 30 days"
"Create positions for each of the roles in this spreadsheet, assign them to the Construction workflow, and publish them"

Who Has Access to Rover?

All Leadline users have access to Rover regardless of their role or permissions. However, what Rover can execute on a user's behalf is still governed by that user's assigned role and permissions — Rover cannot perform actions that the user themselves does not have permission to perform.

→ See 125 - User-Permissions for more information on user permissions and how they affect what Rover can do on your behalf.

→ See 124 - User-Roles for more information on user roles and access levels.

Where Do You Access Rover?

Rover is accessible from the Rover AI tab within the global navigation.

→ See 101 - Platform-Links for the direct link to the Rover chat interface.

Who Configures Rover?

Rover is configured and maintained by Leadline. Users do not configure Rover directly. However, Company Administrators can influence what Rover can access and act on by configuring user roles, permissions, workflows, and other platform settings in the Admin Hub.

→ See 102 - Admin-Hub for more information on platform configuration options that affect what Rover can do within your organization.

What Basic Flows Does Rover Support?

Rover supports Basic Flows across the following areas of the platform. For each area, Rover can answer questions, generate content, and execute individual actions:

Positions

Create a Position
Generate or rewrite a Job Description
Update Position Details
Publish, Unpublish, Close, or Archive a Position

Submissions

Find a specific candidate or submission by name or criteria
Move a submission to a different workflow stage
Share a submission with another user
Export a submission

Candidates

Search for candidates by name or criteria
View a candidate profile
Send an email or SMS text to a candidate
Update candidate status or tags

Application Forms

Generate application form questions for a position
Add or remove questions from an application form

Communications

Send an individual or bulk email or SMS text to candidates
Send a meeting scheduling link to a candidate

Reporting

Pull a standard report
Answer questions about reporting metrics

Product Questions

Answer any question about how Leadline works, what fields are required, how a feature is configured, or where something lives in the platform

What Agentic Workflows Does Rover Support?

Agentic Workflows are multi-step sequences that Rover can execute on your behalf. Rover will always present a plan and ask for your confirmation before beginning any Agentic Workflow.

Bulk Position Creation from Documents Upload one or more PDF or Word documents containing job requisitions or position details — Rover will parse each document, map the content to the appropriate position fields, present a summary for your review, and create the positions in Leadline upon confirmation.

Candidate Search and Surface Describe the type of candidate you are looking for using plain language — Rover will search the database, apply the specified criteria, and return a list of matching candidates for your review.

Note: Additional Agentic Workflows will be added as Rover's capabilities expand. refer to this document regularly for the latest information on available workflows.

What Can Rover NOT Do?

Rover is purpose-built for hiring operations within Leadline. The following are outside of Rover's current scope:

Actions outside of Leadline — Rover operates exclusively within the Leadline platform and cannot access external systems, websites, or third-party tools unless a supported integration is configured
Actions the user does not have permission to perform — Rover cannot bypass user roles or permissions. If you do not have permission to delete a submission, Rover cannot delete it on your behalf
Candidate-facing actions — Rover is an internal tool and does not interact directly with candidates or take actions on behalf of candidates
Admin Hub configuration — Rover cannot make changes to settings configured within the Admin Hub — such as user roles, billing, or organization settings. However, some features that are accessible outside the Admin Hub can still be configured through Rover. For example, Rover can help configure Workflows through the Workflows page, but cannot make changes to Workflows from within the Admin Hub.
Financial or billing actions — Rover cannot access or modify billing information
Anything not yet trained — if Rover has not been trained on a specific task or feature, he will let you know and direct you to the appropriate resource

125 - User-Permissions — Learn about user permissions and how they affect what Rover can execute on your behalf 124 - User-Roles — Learn about user roles and access levels within Leadline 102 - Admin-Hub — Learn about platform configuration options that affect Rover's capabilities within your organization 101 - Platform-Links — Direct link to the Rover chat interface

Rover AI

On this page