Skip to content

AI Actions

MAIA Plus adds a set of AI actions to ServiceDesk Plus ticket pages through page scripts. Which actions you see depends on the rules your SDP administrator has installed and on the page you are viewing.

The Copilot opens a conversation scoped to the ticket and can send messages, continue a run, show progress and the tools used, cancel a run, and present approval or rejection controls when an action is gated.

CapabilityEffect
Open or continue a conversationCreates or resumes a conversation for this ticket
Send a messageStarts a run; the answer may cite knowledge and read the ticket
Show run progress and tools usedRead-only view of what the run is doing
Cancel a runStops the run; nothing further is written
Approve or reject a gated actionDecides whether the proposed write is performed

Access requires a valid MAIA session with the technician role. Ticket and conversation scope are checked server-side, so the Copilot shows the portal the technician is working in.

The summary action appears in a configured request view and produces a summary of the ticket, with a rating control for eligible output. It reads the ticket; it does not modify it.

The rewrite action takes the current editor text and the request context, generates a replacement, and inserts it into the editor. It does not submit or save the request. Review and edit the inserted text; sending it remains a separate action you perform with ServiceDesk Plus controls.

AI Context Search provides a question field and searches the MAIA knowledge context available to you. MAIA Spotlight is a keyboard-driven search over ticket context. Both return candidates for you to assess: a result is a lead, not a verified answer, and the underlying ticket or policy remains the authority.

On request-detail pages, the hints script can search for similar tickets and surface root-cause or solution suggestions, either on a poll interval or on demand. Treat a hint as a prompt to look at the linked tickets, not as a diagnosis.

A write the Copilot proposes appears as an approval card when the agent’s policy or the tool’s policy requires one. Approving performs the write; rejecting ends the run without it; cancelling stops the run.

Approval is a decision, not a preview. Before you approve:

  • Read the action name and its full payload, not just the summary line.
  • Confirm the ticket and portal in the card are the ones you are working in.
  • Follow your organization’s approval policy for the change involved.

A control labelled as a dry run or a preview is not, by that label alone, without effect — check what the action will do before you decide.

Reviewing results · Access from ServiceDesk Plus · Troubleshooting · Copilot roles