Autotask Service Calls

Autotask Service Call Management

Overview

Service Calls in Autotask are used to schedule and plan work against tickets. They represent a planned visit or block of work — linking one or more tickets to a time slot and assigning technicians. This skill covers the full lifecycle: creating service calls, linking tickets, assigning resources, and completing/closing them.

Anti-triggers

• The underlying request being worked — a service call schedules tickets, it does not replace them; use autotask-tickets.
• Hours actually worked — a service call is a plan; billable time is logged separately with autotask-time-entries.
• Multi-phase planned work with dependencies — use autotask-projects.

Service Call Status Codes

Instance note: Status picklist values are instance-specific. Use autotask_get_field_info with entityType: "ServiceCalls" to confirm valid values for your Autotask instance.

Data Model

Service Calls have a three-layer structure:

ServiceCall
  └── ServiceCallTicket(s)        ← links a Ticket to the ServiceCall
        └── ServiceCallTicketResource(s)  ← assigns a Technician to that ticket

• A single ServiceCall can cover multiple tickets
• Each ServiceCallTicket can have multiple resources (technicians)
• Resources can have a roleID to specify their role for billing purposes

Complete Field Reference

ServiceCall Fields

ServiceCallTicket Fields

ServiceCallTicketResource Fields

Available MCP Tools

Common Workflows

Create a Service Call and Link a Ticket

1. autotask_create_service_call
   → description, startDateTime, endDateTime, companyID

2. autotask_create_service_call_ticket
   → serviceCallID (from step 1), ticketID

3. autotask_create_service_call_ticket_resource
   → serviceCallTicketID (from step 2), resourceID, roleID

Complete a Service Call

Two equivalent approaches:

# Option A: Set complete flag
autotask_update_service_call → serviceCallId, complete: true

# Option B: Update status
autotask_update_service_call → serviceCallId, status: 5

Find All Tickets for a Service Call

autotask_search_service_call_tickets → serviceCallId: <id>

Find All Service Calls for a Ticket

autotask_search_service_call_tickets → ticketId: <id>

Find Upcoming Service Calls for a Company

autotask_search_service_calls → companyId: <id>, startAfter: "2026-03-22T00:00:00Z"

API Patterns

Create Service Call

POST /v1.0/ServiceCalls
Content-Type: application/json

{
  "description": "On-site visit - network troubleshooting",
  "status": 1,
  "startDateTime": "2026-03-25T09:00:00Z",
  "endDateTime": "2026-03-25T12:00:00Z",
  "companyID": 12345
}

Link Ticket to Service Call

POST /v1.0/ServiceCallTickets
Content-Type: application/json

{
  "serviceCallID": 99001,
  "ticketID": 54321
}

Assign Technician

POST /v1.0/ServiceCallTicketResources
Content-Type: application/json

{
  "serviceCallTicketID": 88001,
  "resourceID": 29744150,
  "roleID": 5
}

Update / Complete Service Call

PATCH /v1.0/ServiceCalls
Content-Type: application/json

{
  "id": 99001,
  "complete": true
}

Query Service Calls

POST /v1.0/ServiceCalls/query
Content-Type: application/json

Upcoming service calls for a company:

{
  "filter": [
    { "op": "eq", "field": "companyID", "value": 12345 },
    { "op": "gte", "field": "startDateTime", "value": "2026-03-22T00:00:00Z" }
  ],
  "pageSize": 25
}

Open service calls (not complete):

{
  "filter": [
    { "op": "noteq", "field": "status", "value": 5 }
  ]
}

Error Handling

Best Practices

1. Always link at least one ticket — A service call with no linked tickets has no billable context
2. Assign resources after linking tickets — ServiceCallTicketResource requires a ServiceCallTicketID, not a ServiceCallID
3. Set companyID on the service call — Helps with scheduling views and reporting
4. Use autotask_get_field_info to discover instance-specific status picklist values before creating service calls
5. Complete promptly — Mark service calls complete when work is done so scheduling boards stay accurate

Related Skills

• Autotask Tickets - Ticket management
• Autotask Time Entries - Time tracking and billing
• Autotask API Patterns - Query builder and authentication