This Article Solved My Issue

Recruiting: Using Commands with Echo

Describes commands in the Echo feature in Recruiting.

OVERVIEW

  • Our idea: Simple tasks should take only seconds. With Echo, you can change the status of candidates, capture interview feedback, and approve jobs and offers using email with no login required.
  • We’re always looking to make hiring simpler, smarter, and safer. Echo is the simple and smart answer to busy hiring managers and executives that don’t have time to log in to their applicant tracking systems.
  • With Echo, your managers keep the recruiting system up-to-date just by responding to email.

Note: Recruiting also uses the Echo option to record replies sent to Recruiting emails directly on a candidate's Newsfeed. For details about this functionality, see Echo All Emails - Set Up Email Responses to Flow Back into Recruiting.

HOW COMMANDS WORK IN ECHO

There are two parts to an Echo response:

  • Comment: When someone replies to an Echo email, it is saved as a comment on the job or candidate.
  • Command:
    • Recipients also can include command tags in their reply (optional).
    • Command tags ask Recruiting to take action on the recipient’s behalf.

ECHO COMMANDS

These Echo commands can be placed (include the hashtag symbol #) anywhere in the response as long as they are above the line, please put your response above this line:

  • #phonescreen: Recruiting changes the candidate's status to Schedule a Phone Screen.
  • #interview: commands Recruiting changes the candidate's status to Schedule an Interview.
  • #approve: commands Recruiting approves the Job/Offer.
  • #deny commands: Recruiting denies the Job/Offer.
  • #private: Recruiting stores your response as a private comment. This can be used in conjunction with any other statuses.

Note: At this time there is not a Pass command. For OFCCP compliance, you must provide a Reason for Non-Selection when passing on candidates. Replying #pass does not keep our customers in compliance, so we have not implemented this command.

USING COMMANDS EXAMPLES

Example 1:

  • Mark Manager receives a Review Request email and wants to phone screen the candidate.
  • One of your recruiters sent Mark and Review Request email. Mark thinks the candidate looks good and wants his recruiter to schedule a phone screen, here’s how:
  • Mark Responds: This candidate looks great. Please #phonescreen right away.

Example 2:

  • April Approver receives an Offer Approval Request and wants to Deny it
  • Let’s say April thinks the salary is too high for this candidate. Denying the offer is easy.
  • April Responds: #deny (this salary is way over budget)

Example 3:

  • Frank Feedback is asked to provide feedback after a Phone Screen.
  • Frank Phone Screened one of your candidates at 4:00 PM yesterday. Based on your settings, Recruiting asked Frank for feedback at 5:00 PM the same day. Frank liked the person and wants you to schedule an interview.
  • Frank Responds: This candidate was really great. Let’s bring him in for a round of interviews with the team. #interview

SPECIAL CONSIDERATIONS

You can send an Echo email to anyone, even people that are not users. For example, if you request interview feedback from non-users their responses will still be saved to Recruiting.
Commands from non-users are ignored. Only Recruiting users can execute commands. So, if you send a non-user a Review Request and they respond with #phonescreen, Recruiting will ignore the command.
Redundant Commands are ignored.
  • Recruiting ignores commands that would have no effect.
  • Some examples of commands that are ignored include (this is not a complete list):
    • #interview when the candidate is in the schedule interview stage
    • #phonescreen when the candidate is already in the schedule phone screen stage.
    • #approve for a job that has already been approved.
Commands that move a candidate or job backwards in the process are ignored.
  • Recruiting errs on the side of safety and ignore commands that might have deleterious effects and Recruiting does not move a candidate backwards in the process and does not close jobs that have already been activated.
  • Some examples of commands that would be ignored (this is not a complete list):
    • #phonescreen when the candidate is in the interview stage will be ignored
    • #interview or #phonescreen for a candidate in the offer stage will be ignored
    • #deny for a job or offer that has already been approved will be ignored
Approval and Denial of Jobs/Offers can be commanded only by Approvers.
  • Scenario: You carbon copy (CC) a Recruiting User on a Job Approval Request but they are not one of the job’s approvers.
  • If this person responds with #approve or #deny, Recruiting ignores that command (the response is saved as a comment in the job’s history, but the action is ignored).

05/10/24 282 views


Give feedback about this article
Give feedback about this article
Our articles update frequently. Please be aware of this before printing.
Back to Top ↑