ConnectWise PSA Scheduling
Overview
A schedule entry is a forward booking of a member's time against a service ticket, project ticket or sales activity. It is not a record of work done: that is a time entry (connectwise-psa-time-entries). Dispatchers create entries; technicians later log time against the same ticket.
Anti-triggers
- Logging hours already worked — use
connectwise-psa-time-entries (cw_create_time_entry, cw_update_time_entry).
- Customer self-booking links — use TimeZest (
timezest-scheduling) if the MSP runs it.
MCP Tools
| Tool |
Tier |
Purpose |
cw_list_schedule_types |
read |
Type IDs; use the S (Service) type for a service ticket |
cw_list_schedule_statuses |
read |
Status IDs such as Tentative or Firm |
cw_search_schedule_entries |
read |
Bookings, by conditions such as member/id = 147 and dateStart >= [2026-09-22T00:00:00Z] |
cw_search_members / cw_get_member |
read |
Resolve the technician's member ID |
cw_create_schedule_entry |
write |
Book time: objectId, typeId, memberId, dateStart, dateEnd required |
cw_update_schedule_entry |
write |
Move, re-assign, firm up or mark done |
Workflows
Book a technician on a ticket
cw_get_ticket to confirm the ticket and its company.
- Resolve the member with
cw_search_members. The member is never defaulted; confirm who is being booked.
cw_list_schedule_types (Service type for a service ticket) and, if the user named one, cw_list_schedule_statuses.
- Check the member's existing bookings for the window with
cw_search_schedule_entries.
- Convert the requested local time to UTC, then
cw_create_schedule_entry with objectId (the ticket ID), typeId, memberId, dateStart, dateEnd, and optional statusId, whereId (On-Site, Remote, ...), name.
- If the booking is refused as a conflict, show the overlapping entry and let the user pick another time, or explicitly approve a double booking; only then retry with
allowScheduleConflictsFlag: true.
Who is booked tomorrow
Work out tomorrow's start and end in the user's time zone and convert both to UTC. Then cw_search_schedule_entries with conditions: "dateStart < [<end UTC>] and dateEnd > [<start UTC>]", so bookings that start today and run into tomorrow are included, ordered by dateStart asc, then group by member.
Reschedule
Find the entry with cw_search_schedule_entries, confirm the new time, and cw_update_schedule_entry with the new dateStart/dateEnd.
Gotchas
- Dates are UTC.
'2026-09-22T02:00:00Z' is 10:00 in Perth. Always convert and echo the local time back to the user.
- Conflicts are refused by default. Set
allowScheduleConflictsFlag only when the user explicitly wants a double booking.
- Reminder IDs have no list endpoint; read a
reminderId off an existing entry with cw_search_schedule_entries.
- A booking is not billable time. Closing the ticket without a time entry bills nothing, however many schedule entries it has.
1---2name: connectwise-psa-scheduling3description: >4 ConnectWise PSA schedule entries through Conduit: booking a member's time5 against a service ticket, project ticket or activity6 (cw_create_schedule_entry), finding and moving bookings7 (cw_search_schedule_entries, cw_update_schedule_entry), schedule types and8 statuses, UTC date handling, and the difference between a booking and a time9 entry.10when_to_use: >-11 When booking, moving or reviewing technician time on the ConnectWise PSA schedule (dispatch).12 Use when: schedule a tech, book an engineer, dispatch, schedule entry, calendar connectwise,13 who is booked tomorrow, reschedule appointment, or on-site visit connectwise.14metadata:15 source: https://skillmd.com/skills/wyre-ai/connectwise-psa-scheduling16---1718# ConnectWise PSA Scheduling1920## Overview2122A schedule entry is a **forward booking** of a member's time against a service ticket, project ticket or sales activity. It is not a record of work done: that is a time entry (`connectwise-psa-time-entries`). Dispatchers create entries; technicians later log time against the same ticket.2324## Anti-triggers2526- **Logging hours already worked** — use `connectwise-psa-time-entries` (`cw_create_time_entry`, `cw_update_time_entry`).27- **Customer self-booking links** — use TimeZest (`timezest-scheduling`) if the MSP runs it.2829## MCP Tools3031| Tool | Tier | Purpose |32|------|------|---------|33| `cw_list_schedule_types` | read | Type IDs; use the `S` (Service) type for a service ticket |34| `cw_list_schedule_statuses` | read | Status IDs such as Tentative or Firm |35| `cw_search_schedule_entries` | read | Bookings, by `conditions` such as `member/id = 147 and dateStart >= [2026-09-22T00:00:00Z]` |36| `cw_search_members` / `cw_get_member` | read | Resolve the technician's member ID |37| `cw_create_schedule_entry` | write | Book time: `objectId`, `typeId`, `memberId`, `dateStart`, `dateEnd` required |38| `cw_update_schedule_entry` | write | Move, re-assign, firm up or mark done |3940## Workflows4142### Book a technician on a ticket43441. `cw_get_ticket` to confirm the ticket and its company.452. Resolve the member with `cw_search_members`. The member is **never** defaulted; confirm who is being booked.463. `cw_list_schedule_types` (Service type for a service ticket) and, if the user named one, `cw_list_schedule_statuses`.474. Check the member's existing bookings for the window with `cw_search_schedule_entries`.485. Convert the requested local time to UTC, then `cw_create_schedule_entry` with `objectId` (the ticket ID), `typeId`, `memberId`, `dateStart`, `dateEnd`, and optional `statusId`, `whereId` (On-Site, Remote, ...), `name`.496. If the booking is refused as a conflict, show the overlapping entry and let the user pick another time, or explicitly approve a double booking; only then retry with `allowScheduleConflictsFlag: true`.5051### Who is booked tomorrow5253Work out tomorrow's start and end in the user's time zone and convert both to UTC. Then `cw_search_schedule_entries` with `conditions: "dateStart < [<end UTC>] and dateEnd > [<start UTC>]"`, so bookings that start today and run into tomorrow are included, ordered by `dateStart asc`, then group by member.5455### Reschedule5657Find the entry with `cw_search_schedule_entries`, confirm the new time, and `cw_update_schedule_entry` with the new `dateStart`/`dateEnd`.5859## Gotchas6061- **Dates are UTC.** `'2026-09-22T02:00:00Z'` is 10:00 in Perth. Always convert and echo the local time back to the user.62- **Conflicts are refused by default.** Set `allowScheduleConflictsFlag` only when the user explicitly wants a double booking.63- **Reminder IDs** have no list endpoint; read a `reminderId` off an existing entry with `cw_search_schedule_entries`.64- **A booking is not billable time.** Closing the ticket without a time entry bills nothing, however many schedule entries it has.