No-Show Response

What you can build

• Text the late employee from When I Work punches

  times::punch is watched per shift. When none arrives inside the tolerance, a Twilio SMS is proposed to the employee, and the reply is attached to the manager's alert in Slack.

  With When I Work, Twilio, Slack

• Keep an occurrence log for 7shifts locations

  time_punch.created events are matched to shifts by user and business date. A confirmed no-show is appended as a row in Google Sheets with the shift, the minutes, the outreach, and the manager who confirmed.

  With 7shifts, Google Sheets

• Write the note to Deputy

  A Timesheet webhook filtered on IsInProgress marks who has started. For everyone else past tolerance, the operator proposes the outreach and, on the manager's confirmation, a Journal entry on the employee.

  With Deputy, Microsoft Teams

• Poll QuickBooks Time where there are no webhooks

  Timesheets with on_the_clock=yes are read each cycle against schedule events. The tolerance is set with the poll interval in mind, and each proposal shows the time of the read it relied on.

  With QuickBooks Time, Slack

Requirements

• A time and attendance connector that shows clock-ins: When I Work, 7shifts, Deputy, Connecteam, QuickBooks Time, Homebase, or Dayforce
• A scheduling source for who is due when; usually the same system
• Twilio for SMS, or Slack for direct messages, to reach the employee; Slack or Microsoft Teams for the manager
• Per site and role: the tolerance in minutes, the manager to alert, and where occurrences are recorded

Authentication

Has no credentials of its own to carry. Shifts and punches are read, and messages sent, through the connectors you bind, under the scopes those connectors hold.

Limits

• A no-show is declared by the manager, not the operator. Until then the state is no clock-in after the tolerance, and the message says so
• Where the time system has no push events, as with QuickBooks Time or Homebase, detection waits for the next poll; set the tolerance accordingly
• It sends nothing to an employee with no number or Slack account on file; the manager alert names who could not be reached
• Twilio SMS fees are billed to your account; each outreach proposal shows the number it will send to

Questions and answers

What does the manager approve?

Two things, separately. First the outreach: the message text and the number or account it goes to. Then the occurrence: once the manager marks the shift a no-show, the record proposed for the journal or log, and any cover offer that follows.

What record is left?

For each shift: when the tolerance passed, the message sent and its delivery status, any reply, the manager's decision and when they made it, and the journal entry or log row written with a link back to the shift.

Will it contact an employee on its own?

No. A message goes out only after a person approves it. The operator also never marks anyone absent; a missing punch stays not clocked in until a manager says otherwise.