Table of Contents
The following are common terms and actions used in competitor platforms and how they are mapped to Paradox’s common terms.
Common terms
Common Terms in Competitor Platforms |
Paradox Translation |
|---|---|
|
Collect Forms
|
Event Registration Forms |
| Staff |
|
| Kiosk Mode | Kiosk Mode |
|
Paradox Native Application |
| Candidate-Facing App (could house event agendas) | Candidate’s My Schedule Landing Page |
| Folders/Tag |
|
| Talent Pipeline |
|
| Evaluation Form | Evaluations (created in Surveys) |
|
Sequential Interview Scheduling |
|
Follow-Ups
|
Campaigns / Segment Creation
|
| Campus/Organizations Profiles | Campus Profiles |
| Event Fields | Custom Planning Fields |
|
Event Management Dashboard Event Dashboards |
Analytics & Reporting Dashboards - Embedded Dashboards |
| Event Expenses | Event Budget & Expenses (feature within Custom Planning Fields) |
| Campaigns | Campaigns |
| QR Code Check-In → Collect Form | Event Registration Form (completed by scanning a system-generated QR code) |
|
|
|
|
Common actions
Common Action in Competitor Platforms |
Paradox Translation |
|---|---|
| QR Code Check-In → Collect Form | Scan system-generated QR code or complete a conversation → Event Registration Form |
| Launch Kiosk Mode on a user's device to collect student information. | Launch Kiosk Mode on a user's device to collect student information. |
|
Use spreadsheet forms to collect student information at the event. Collect student information on a piece of paper. |
|
|
Event Attendees collect resumes from students at campus-related events.
|
|
|
Event Attendees require the ability to evaluate students through the Events Mobile App.
|
Career Fair Mode - Selecting an Evaluation. |
|
|
| Checking in a student at a booth or an event. |
|
|
Follow-Ups
|
Campaigns / Segment Creation
|
|
When a job is created and managed within the same system, users can invite students who they met at an event to apply to a job from the platform.
|
|
|
Within the event, users can send mass communications (typically email communications) to students who they met at an event.
|
Within the event, the user can filter the event inbox based on candidate attributes and use the Mass Action - Send Message action to send mass communications to students in the event. |
|
Users can send mass communications (typically email communications) to students who are in the client’s CRM.
|
|
|
Users can manually add an individual student to a folder within the system CRM.
|
|
|
Users can, at mass, add students to a folder within the system CRM.
|
|
| Users can manually add a tag to students. | Manually add an attribute value to the profile (editable attribute value on the Candidate Profile). |
|
Users can, at mass, manually add a tag to students.
|
|
| Batch Resume Uploads in the event and within the CRM. |
|
| Attach candidate to an event. |
|
|
|
|
|
|
Tag Along Events
|
|