Productivity

Scheduling Agent

Proposes times it can actually stand behind, and books nothing

Version 3Published Sep 2, 2026
ProductivityExtractclaude-sonnet-5Read-only · auto8 hard rules5 handover rulesResult
8hard rules
Things it must never do, enforced in every run
5handover rules
Conditions where it stops and gives the work to a person
7output fields
A structured result, not a paragraph you have to re-read
≤4steps per run
Bounded work: at most 3 tool calls, enforced by the runtime

Read-only by design. This agent has no path to sending, spending, publishing or committing anything. Where that limit is the product, removing it would remove the reason to trust the output.

Live wiring for version 3. Tool nodes are the capabilities this agent is registered to call — nothing else can run.

Overview

Scheduling tools either book — and eventually book over something they could not see, at a cost greater than the time they saved — or they send a link and hand the work back to the person you were trying not to inconvenience.

This proposes. It reads the availability and constraints you supplied, applies the rules that actually matter — working hours in each participant's own timezone, the buffer people need between calls, the days someone has said they do not take meetings — and returns a small number of slots that work for everyone it can see.

What makes it usable is the second half: it states exactly what it could not see. A calendar it was not given, a timezone nobody specified, a participant whose availability is unknown. A proposal that admits its blind spot can be judged; a confident one that turns out to be wrong costs an apology and a reschedule. It books nothing and sends nothing.

Benefits

No double bookings

Because it never books, and never claims a slot is held.

The back-and-forth, gone

Without pushing the work back to the other side.

Fewer awkward invites

Nobody asked to join at 6am their time.

What it does

  • States what it could not see

    A calendar it was not given, a timezone nobody stated. A proposal that admits its blind spot can be judged.

  • Timezones per participant

    Working hours are local. 9am for you is the middle of someone's night, and that is the commonest error.

  • Respects the rules people actually have

    Buffers between calls, no-meeting days, the hour nobody should be asked to give up.

  • A few good slots, not thirty

    Thirty options is not helpfulness, it is the decision handed back to the recipient.

  • Flags what makes a slot fragile

    Back-to-back with something else, or resting on availability that was inferred rather than given.

  • Books nothing

    It proposes. Putting something in someone's calendar is a commitment a person should make.

What this changes

What this changes about your week

It takes over
The back-and-forth of finding a time that works across timezones.
Done today by
Everyone, several times a week.
How often
Every meeting that involves more than two diaries.
Typical manual effort
Six messages and two days for one 45-minute call.

Why Productivity in particular. It states what it could not see. Assistants that book eventually book over a calendar they were not given, and the recovery costs more than the scheduling ever saved.

  • Runs unattended

    Started by you or by an event, and it finishes on its own. Nothing waits for someone to be at a desk.

  • The same standard every time

    The two-hundredth item is held to the bar the first one was. Consistency is the part people cannot sustain.

  • It cannot act on its own

    Scheduling Agent has no path to sending, spending or committing. That limit is why its output is safe to act on.

How it runs

This agent runs server-side through the PROMIVO runtime. Each run is logged step by step and every tool call is permission-checked before it executes.

  1. 1InputValidated against the agent input schema
  2. 2Modelclaude-sonnet-5 with automatic fallback
  3. 3Toolsextract_structured_data
  4. 4PermissionsRuns READ actions automatically; anything higher waits for approval
  5. 5OutputStructured result matching the output schema
  6. 6LoggingTokens, duration and every step recorded

Demo

Demo dataIllustrative sample output, abridged.

Input

{
  "purpose": "Kick-off",
  "participants": [],
  "durationMinutes": 45
}

Output

{
  "escalate": true,
  "proposals": [
    {
      "startsAt": "2026-09-09T13:00:00Z",
      "worksFor": [
        "Ehab",
        "Anna",
        "Marcus"
      ],
      "localTimes": [
        "16:00 Istanbul",
        "15:00 Berlin",
        "09:00 New York"
      ],
      "unknownFor": [],
      "fragileBecause": ""
    },
    {
      "startsAt": "2026-09-10T08:00:00Z",
      "worksFor": [
        "Ehab",
        "Anna"
      ],
      "localTimes": [
        "11:00 Istanbul",
        "10:00 Berlin",
        "04:00 New York"
      ],
      "unknownFor": [],
      "fragileBecause": "04:00 for Marcus. Offered only because you asked for a second option that day."
    }
  ],
  "disclaimer": "Slots are proposals from the calendars and constraints supplied. Nothing has been booked, held, reserved, cancelled or moved, no invitation has been sent, and availability that could not be seen is stated rather than treated as free.",
  "couldNotSee": [
    "Priya's calendar was not supplied. Any slot involving her is unverified, and she is marked required."
  ],
  "draftMessage": "Three options below — none of them are held, so tell me which works and I will send the invite.",
  "escalationReason": "A required participant's availability is unknown, so no proposal can be relied on.",
  "rulesThatEliminatedSlots": [
    "Tuesday 14:00 UTC worked for everyone but falls in Anna's stated no-meeting block."
  ]
}

Requirements

Integrations

No integrations required.

Before you start

  • Participants and their availability
  • Constraints — timezones, hours, no-meeting rules
  • Requires the Starter plan or higher

Use cases

A meeting across timezones

Slots that are civilised for everyone, not just the organiser.

A panel or a committee

The few windows where five diaries actually overlap.

Rescheduling

What genuinely still works after something moved.

Pricing

Starter

Billed monthly through your PROMIVO subscription. Cancel at any time.

Runs consume your plan allowance for agent executions and tokens. See plan limits

FAQ

Why will it not book?

Because booking assumes it can see everything, and it cannot. A tool that books over a calendar it was not given costs more than the scheduling it saved, and it always eventually does.

Does it connect to my calendar?

It works from the availability you supply or that a connected calendar returns. Whatever it was not given, it reports rather than assuming free.

Will it email the participants?

No. It gives you the slots and the wording. Sending is yours.

Reviews

Reviews open once customers have run this agent.

Need this agent to work differently?

Tell us what to change and our team will scope a customised version for your business.

Customize this agent