---
title: "Attendance tracking with an AI agent | StudioChat"
description: "Put in your own numbers and compare what one absence costs today across WhatsApp, attendance, Drive and payroll against the same case with an agent."
url: https://studiochat.io/attendance-with-an-agent
locale: en
translations: { es: https://studiochat.io/presentismo-con-un-agente.md, pt: https://studiochat.io/presenca-com-um-agente.md }
site: https://studiochat.io
---

Tool

# One absence with a certificate, end to end

Five numbers of your own: how many events reach payroll a month, how many minutes each one takes, what an hour of the person doing it costs, what share ends in an error and what fixing it on a payslip costs. Below, the same case with an agent: where it goes, what it does at each step and what stays with a person.

One absence with a certificate, end to end

* the agent does it
* a person does it
* always a person

the steps of the case

* the agent does itRead the notice and understand it WhatsApp 
Reads the message as it arrives, tells an absence from a late arrival, and asks exactly one follow up question when something is missing.
* the agent does itRecord the day's event Attendance 
Writes the record into the attendance system the same day it happened, in the format the system expects.
* the agent does itAsk for the certificate and keep asking WhatsApp 
Asks as soon as the absence is recorded, asks again at 24 and 48 hours, and stops asking once it arrives.
* the agent does itRead the certificate and validate it WhatsApp 
Reads the photo: pulls the date, the days prescribed, the practitioner and the licence number, and says on the spot if the image is cropped or illegible.
* the agent does itFile it where it belongs Drive 
Saves it in the employee's folder under the name the company uses, with nobody renaming a file.
* the agent does itArrange the doctor's visit Company doctor 
Calls or messages the company doctor, passes the address and a time window, books the visit and records what the doctor verified.
* the agent does itPass it to payroll Payroll 
Writes the right entry in the right period, which is the stretch where the error gets paid on the payslip.
* always a personDecide whether the absence is justified Attendance 
A person decides this. They arrive with the certificate already read, the visit done and the month's history in view.

Events per month that reach payroll: 300

Minutes one event takes today, end to end: 14.0

Hourly cost of whoever does it: USD 12

Share that ends in an error: 4%

What fixing a payslip error costs: USD 40

Today that is 70 hours a month and 12 events that end badly. Between the time and the corrections, USD 1,320 a month.

With the agent holding 7 of the 7 steps, 3 hours and USD 63 are left.

The difference is USD 1,257 a month, USD 15,086 a year.

And 36% of that difference is not time: it is the errors that stop happening because the figure never gets retyped into the next screen.

Of what a person still does, the heaviest step is: Decide whether the absence is justified.

You set all five numbers. How the minutes split across steps is ours, taken from how it gets done by hand. The one modelling assumption, and the one worth arguing with: an error born of carrying a figure from one system to another by hand falls in the same proportion as those hand-offs stop being manual.

This object is the interactive half of an article: [One absence with a medical certificate crosses four systems and one person](/blog/presentismo-sin-planilla)

## The playbook already exists. We multiply it.

[Talk to us now](https://cal.com/studiochat)

[Book a demo](https://cal.com/studiochat) [Or write to hey@studiochat.io](mailto:hey@studiochat.io)