Skip to content

Shifter alone

  • Requests, shifts and availability
  • Reports in Shifter, separate from your ATS and payroll

Shifter with Dashly

  • Requested hours next to deployable hours, by region and role
  • The same definitions as for your other systems

What you see with it

  • Fill rateFlex workforcefilled shifts ÷ requested shifts
  • Growth per clienthours this period ÷ hours in the same period last year
  • Last-minute shareFlex workforcerequests less than 48 hours before start ÷ all requests
  • Skills matchrequests with suitable available candidates ÷ all requests
  • Expired but scheduledshifts with an expired mandatory certificate
  • Rest period breachesComing soonshifts that breach the Arbeidstijdenwet

What Dashly collects

  • Requests and shifts
  • Scheduled deployment
  • Availability
  • Dropouts and no-shows
  • Rosters and rest periods

How it connects

You pick Shifter from the connections and connect it yourself through the marketplace. Dashly collects the data on a schedule, with history, so you no longer need to export anything. Dashly AGI sets up the rest: the model, built on your definitions, and the checks.

For each connection you see its status and how fresh the data is. If something goes wrong, you see it.

Together in your model

Other systems in this group: Flexwell, Planworks

Shifter
Group
Planning
Setup
Dashly AGI
Price class
Connection · See pricing
Works with your own AI
Claude, ChatGPT, Copilot

Foundation

One foundation under all your connections.

All your systems, once

ATS, scheduling, payroll, HR, accounting and CRM in one place. Every client, candidate and employee exists once.

Your AI uses the same definitions

Every connection feeds into the Workforce Intelligence Model, with fixed formulas. The same calculation everywhere, also in Claude, ChatGPT or Copilot.

Set up by Dashly AGI

Digital colleagues connect, model and check. Only when the numbers match your own figures does it go live.