Something watching while nobody is

Work does not stop failing at six o’clock; it just stops being noticed. Dutta is on shift continuously, in every timezone, with no rota — and it does more than notice.

The work today

Failure is silent. A job that stops, a hand-off nobody picked up, a queue that quietly stopped draining. None of them raise their hand, and all of them are found in the morning.

Alerting is not watching. A monitor tells you a threshold was crossed inside one system. It cannot tell you that the hand-off between two teams never happened, because no threshold describes that.

The morning starts with archaeology. Before anything can be fixed, somebody reconstructs what happened overnight from logs, timestamps and guesswork.

On-call costs a person their sleep. Usually to perform one restart that anyone could have performed, and occasionally to discover something genuinely worth waking up for.

What Dutta does, in order

ContinuouslyFollows work across the systems it passes through, rather than watching a single queue, so it sees the hand-off that was never picked up.
On a stallActs if the fix is within the mandate you set — restarts, re-routes, chases — and records what it did.
Outside its mandateRaises it with the context already assembled, on WhatsApp, Telegram, Slack, SMS, a voice call or the Dutta app, whichever you already have open.
07:00Reports the night: what moved, what stuck, and what it changed.

What it reads and writes

An AI employee holds scoped credentials — read, write or send, per system — and nothing beyond its mandate. Permission is granted per system, and revoking it takes effect immediately. For this job that normally means:

  • Connected systems — read, to follow work across them
  • Named systems — write, only where you have granted it
  • Email — send, for the reports you asked for

Where a person stays in the loop

Dutta prepares, drafts and flags; a person approves anything with a consequence. You name the checkpoints, and for this job they usually are:

  • Any fix outside the mandate you defined
  • Anything that changes a process rather than restarting one
  • Any action affecting a customer or a payment

Questions

What stops it acting where it should not?

It holds scoped credentials — read, write or send, per system — and nothing beyond its mandate. Permission is granted per system, not per employee, and revoking it takes effect immediately.

How is this different from monitoring?

Monitoring tells you that something crossed a line. An employee owns the outcome: it follows the work across systems, fixes what it is permitted to fix, asks when it is unsure, and tells you what it did.

Do we still need someone on call?

That is your decision, and it is a permissions question rather than a product claim. Dutta is on shift in every timezone with no rota; what it may do unattended is exactly what you have granted it.

The role behind this job

This work is what the Operations employee does on shift. Everything else it handles, and the whole shift it works, is on the role page: an AI employee for operations.

Put it on shift

Pricing is per AI employee on shift; humans are unlimited on every plan. See pricing or tell us the process that eats your team’s week.

Other jobs Dutta takes

Invoice reconciliation · Support inbox · Month-end close · Candidate screening · Weekly reporting