Customer & field service

Validate account access and entitlement, manage communications, and coordinate case closure.

Model interruption and planned maintenance, publish status, and interpret availability evidence.

Plan a work order, assign a qualified resource, and collect completion evidence.

Configure playbook activities, complete an active run, and manage coordinated updates without losing case-specific access.

17 declared fields for Customer account. Required fields include Name.

10 declared fields for Installed customer asset. Required fields include Name, Customer account, Installed asset or service.

17 declared fields for Customer service contract. Required fields include Name, Customer account, Contract number, Coverage start.

11 declared fields for Service entitlement. Required fields include Name, Customer account, Customer service contract.

15 declared fields for Field work schedule. Required fields include Name, Published work plan, Service location, First occurrence (UTC).

9 declared fields for Technician absence. Required fields include Name, Technician, Unavailable from, Unavailable until.

10 declared fields for Customer feedback setting. Required fields include Survey question, Response window (days).

10 declared fields for Customer satisfaction response. Required fields include Customer case, Respondent.

8 declared fields for Case playbook. Required fields include Name.

9 declared fields for Captured case playbook. Required fields include Customer case, Playbook definition.

10 declared fields for Major customer issue. Required fields include Title, Business impact, Originating customer case.

14 declared fields for Service outage. Required fields include Outage title, Operational description, Primary affected CI, Service impact began (UTC).

14 declared fields for Customer service case. Required fields include Case title, Describe the issue, Customer account.

10 declared fields for Customer case task. Required fields include Customer case, Task title.