Skip to main content

3.3 Opportunities and the candidate automation agent

Automate the sending of matching orders to candidates

Pål Torgersen avatar
Written by Pål Torgersen
Updated over 2 weeks ago

What is the candidate automation agent?

The candidate automation agent lets you “set and forget” job notifications for an individual candidate.

Say you talked to a candidate on the phone, who informed you that they will be available in three months. Then it's quick and easy to find the candidate in Globus and configure alerts or auto-sending from that date. Once it’s configured, Globus watches for new orders that match the candidate’s preferences and either:

  • Sends them automatically to the candidate (SMS/email/portal), or

  • Notifies you when a new matching job becomes available, allowing you to act quickly.

This builds on the existing Opportunities tab on the candidate profile, where you already see all active orders that align with the candidate's preferences.



How to activate the candidate agent

  1. Open the candidate page and search for the candidate.

  2. Open the candidate profile (click the "Profile" button on hover or "View profile" in the side-panel).

  3. Click the tab: “Opportunities”.

On this tab, you’ll see a list of matching orders. Here you configure two parts:

  1. The filter for which orders should be considered

  2. The automation rules for how and when to send/notify



Step 1 – Set up the opportunity filter

The filter defines which orders Globus should monitor for this candidate. It's always recommended to be more detailed to avoid spamming the candidates, which can cause them to unsubscribe.

Filters that should always be added so the automation behaves safely:

  • Order status = Active
    Only open/active orders are sent to the candidate.

  • Create date (from) = Today's date
    Only orders created from today onwards will be included. This prevents old active orders from being sent out when you turn the agent on.

  • Role = Candidate’s role(s)
    Default roles from the candidate profile, but you can add or remove roles if they are open to more/fewer.

Optional filters (fine-tuning)

Use additional filters to reflect the candidate’s preferences better:

  • Location + distance
    For example “Oslo within 30 km” if the candidate only wants nearby jobs.

  • Customer(s)
    Limit to preferred customers or exclude ones the candidate does not want.

  • Schedule (from date)
    For example, “from 1 January” if the candidate is only available from that date. And only orders containing periods or shifts that overlap the set date will match.

As you adjust the filter, the matching orders are displayed below, allowing you to visually confirm that the filtering is correct before enabling the automation.

All available order filters can be used; a full overview is available here.


Step 2 – Configure the automation rules

When you’re happy with the filters, click “Set up automation”.

Here you decide what the agent should do when a new matching order appears.

1. Choose the automation mode

You have two main options:

  • Notify me when there is a match
    Globus monitors the filtered orders and alerts you whenever something matches the candidate’s preferences, instead of sending directly to the candidate.

  • Auto-send to candidate
    Matching jobs are automatically sent to the candidate (SMS, email, or both) using your set template (can be customized per candidate). It is also possible to publish the orders to the candidates' portal without email or SMS notifications.

Use “notify me” if you want to test the setup or keep tighter control for high-priority or sensitive roles.


2. Set the schedule (how often it should run)

You control how frequently Globus checks for new matching orders and triggers the automation. Typical options include:

  • Every minute (near real-time)

  • Hourly

  • Daily at a chosen time

  • Weekly on selected weekdays and at a specific time

The time you set is indicative – messages may be sent from that time, depending on overall system volume.

3. Decide what is sent and via which channel

Within the automation setup you can decide:

  • Channels

    • SMS

    • Email

    • Or both

    • Publish to portal

  • Information to include in the message
    For example: customer, location, dates, role, and the candidate’s personal link to view and respond to the opportunity in their portal.

This keeps candidates informed and engaged, and lets them respond quickly to jobs that fit their preferences and availability.

4. Limit the number of orders per day

To avoid spamming candidates, you can set a maximum number of orders per day that this automation is allowed to send.


Example:
“Maximum 5 orders per day per candidate” – if there are more matching orders, Globus will stop sending once the limit is reached for that day.

Beware that the Daily limit is the number of orders sent, not the number of emails/sms sent. If you have the schedule set to every minute, usually only one order was received since last checking, so one email/sms would usually just include one order. In this case, most probably 20 emails/sms will be sent.

With daily/weekly the emails/sms will include up to 20 orders.


Tips and best practices

  • Start narrow, then expand
    Begin with a tight filter (for example, on location, role, and specific customers). If the candidate wants more, you can widen the segment later.

  • Use ‘notify me’ when testing
    First, run the agent in “notify me” mode. When you see that the notifications are relevant, switch to auto-sending.

  • Align with candidate preferences
    Use the candidate’s profile to store their preferred locations, clients, roles, and availability – this makes it much easier to set up meaningful automations.

  • Respect communication and consent rules
    Make sure the candidate has agreed to receive SMS/email, and use your email preference tools to manage unsubscribes and types of communication.

With the candidate automation agent, Globus takes care of tracking and sending relevant jobs – so you can focus more on building relationships with candidates and customers.

Did this answer your question?