timezest

Book a TimeZest scheduling request for a technician against a PSA ticket

List TimeZest bookable resources — agents, teams, and appointment types

Produce a TimeZest scheduling pipeline report grouped by lifecycle state and resource

List recent TimeZest scheduling requests, grouped by state

Find stale TimeZest scheduling requests still waiting on a customer to book

Use this agent when reporting on the TimeZest scheduling pipeline — grouping requests by lifecycle state, finding stale requests waiting on customers, measuring booking conversion, and producing a dispatch-queue view across agents and teams. Trigger for: scheduling pipeline, TimeZest report, stale requests, stuck bookings, scheduling queue, booking conversion, requests waiting on customer, TimeZest dashboard, scheduling backlog. Examples: "Show me the TimeZest scheduling pipeline for today", "Which scheduling links have been sent but not booked?", "What's our booking conversion rate this week?", "Audit stale TimeZest requests and tell dispatch who to chase"

Use this agent when working with the link between TimeZest and a PSA — building correct associatedEntities payloads for ConnectWise / Autotask / Halo, auditing scheduling requests for missing or wrong PSA associations, reconciling TimeZest bookings against PSA tickets, and choosing pod vs generate_url trigger modes. Trigger for: PSA association, link to ticket, ConnectWise integration, Autotask integration, Halo integration, associated entities, pod workflow, reconcile bookings, orphan scheduling request. Examples: "This booking didn't show up on the ConnectWise ticket — what went wrong?", "Audit our recent TimeZest requests for ones missing a PSA link", "Should this request use pod or generate_url?", "Reconcile last week's TimeZest bookings against their Autotask tickets"

Use this agent when booking a technician against a PSA ticket through TimeZest — resolving the right agent or team, picking the correct appointment type, creating the scheduling request with the PSA association, and confirming the customer booking link was issued. Trigger for: book a tech, schedule a technician, send a TimeZest link, create scheduling request, book against ticket, TimeZest dispatch, schedule onsite, schedule remote session. Examples: "Book a remote session for the customer on ConnectWise ticket 88421", "Send a TimeZest link to the customer on Autotask ticket T20240199", "Schedule an onsite visit with Maria for Halo ticket 5567", "Get the customer on this ticket scheduled with whoever's available on the network team"

Use this skill to resolve the right bookable resource in TimeZest before creating a scheduling request — listing agents (individual technicians) and teams (round-robin / shared availability pools), fetching detail for a named resource, and deciding when to book an agent versus a team.

Use this skill when working with the TimeZest MCP tools — Bearer token authentication, the navigation pattern, scheduling-request payloads that carry PSA associated_entities (ConnectWise / Autotask / Halo ticket IDs), and the polling-only update model (no webhooks).

Use this skill to pick the correct TimeZest appointment type for a scheduling request — listing the appointment types configured for the tenant, reading each type's duration, and matching the type to the work described on a ConnectWise / Autotask / Halo ticket.

Use this skill to wire a TimeZest scheduling request into a PSA — building correct associatedEntities entries for ConnectWise, Autotask, or Halo tickets, choosing between the pod and generate_url trigger modes, and diagnosing bookings that completed but never updated the PSA ticket.

Use this skill to query TimeZest's combined resource pool — the unified list of agents and teams available for scheduling — when you want a survey of everything bookable before drilling into a specific agent or team, or when the dispatcher has not named a resource.