Ticketing and Concierge Configuration Overview
This section provides a high level overview of configuring Moveworks Concierge, as well as important foundational terminology to understand before diving into the configuration. Terms such as Ticket Type, Ticket Destination, Domain, Prefix, Table Name, Service Desk ID, Ticket Mapping, Ticket Routing, and Ticket Workflow are technical concepts that are required to be familiar with before starting the ticketing configuration.
Familiarity with these terms will help you follow the rest of the guide and configure effectively.
Key Terminology
Term | Definition |
---|---|
Ticket Type | A ticket type is a classification or category—such as INCIDENT, REQUEST, or HR CASE—that defines the nature and workflow of a ticket and mapping to a specific system record.
|
Ticket Destination | The logical container or structure within your external ticketing system where tickets are created and managed e.g., the table |
Domain | A domain in Moveworks refers to a high-level category—like IT, HR, or FACILITIES—used to route employee requests to the appropriate support area or team. This classification ensures that a particular ticket is handled efficiently by the right department or function (e.g., Read more on Domains |
Prefix | A unique identifier added at the beginning of a ticket reference for clear categorization and easy tracking e.g., "IT" for |
Table Name | Name of the external ticketing system table storing the ticket e.g., the table This value is usually the same as the Ticket Destination as shown above |
Service Desk ID | ID for a project/service desk in systems like Jira. |
Ticket Mapping | Setup that connects Moveworks to your ticketing system and defines actions like create/update. |
Ticket Routing | Logic that determines which workflow to use based on context. |
Ticket Workflow | Ticket workflows are sequence of steps Moveworks executes for a ticketing action. The system provides predefined default workflows for standard ticket actions, detailed as follows:
|
I |
Ticket States and State Mapping
Internal States
Internal States are the names or labels used within Moveworks AI Assistant to categorize the status of a ticket. These states are part of your internal workflow or process management. In the AI Assistant, there are a total of 5 Internal States
- NEW: Represents a newly created or reopened ticket.
- WAITING_FOR_USER: Indicates that the ticket is waiting for input or action from the user.
- WIP (Work In Progress): Marks a ticket that is actively being worked on.
- RESOLVED: Signifies that the ticket has been resolved.
- CLOSED: Shows that the ticket is closed, either because it was completed or canceled.
NO LONGER SUPPORTEDWAITING_FOR_VENDOR, WAITING_FOR_APPROVAL and NOT_APPLICABLE are legacy states that are no longer supported in AI Assistant
External States
External States are the names or labels used in the connected Ticketing Service Management system . These states reflect the status of a ticket as recognized by the external system. They are mapped to internal states to ensure consistency and communication between systems.
Mapping Process
State Mapping: The process involves linking each external state to an internal state. This ensures that when a ticket's status changes in the Ticketing Service Management system, it is accurately reflected in the AI Assistant.
For example, if a ticket in the ServiceNow is marked as "In Progress" or "On Hold," it corresponds to the internal state of WIP the AI Assistant
State Transition: When an action occurs (e.g., a user comment or a resolution of a Ticket), the system updates the ticket's state based on these mappings. This ensures that both systems stay in sync and reflect the current status of the ticket accurately.
The Process of Configuring Moveworks Ticketing and Concierge
- Select the Source Ticketing System: Choose the appropriate connector for your ticketing system.
- Configure Ticket Types: Configure the relevant ticket types and relevant tables or projects from your existing Ticketing system, which you would like to integrate into Moveworks.
- Configure Ticket Action Mapping: This is where you configure Ticket Mapping and Ticket Action Payloads that get used by the Moveworks AI Assistant for ticketing actions such as querying, creating, updating, resolving, and reopening tickets.
- Specify how Moveworks performs ticket actions (create, update, resolve, reopen):
- Map data fields between Moveworks and your system.
- Define status/value mappings to trigger notifications.
- Specify how Moveworks performs ticket actions (create, update, resolve, reopen):
- Configure Ticket Workflows (Routing & Workflow Conditions) - Set conditional rules to route requests to the correct workflow based on attributes like domain, user attributes, or ticket type.
- Define the operational steps for each ticket action:
- Choose connector.
- Configure API calls and data payloads.
- Add conditional or default steps.
- Define the operational steps for each ticket action:
- Configure Ticket Filters - Control which tickets are included/excluded from bot actions:
- Standard Filters: Apply globally across the assistants
- Skill-Specific Filters: Apply only to certain actions (e.g., notifications).
- Ticket Notifications (Concierge Notifications) -- Customize user notifications for key events:
- Enable/disable alerts (e.g., resolved, commented).
- Configure nudge rules.
- Set quiet hours or working hours.
After you've reviewed this configuration process, you can follow the detailed step by step guides below to configure Moveworks Concierge for your Ticketing system:
- Configure Ticketing for ServiceNow
- Configure Ticketing for Jira Service Desk
- Configure Ticketing for Fresh Desk
Common Enhancements
Once you've completed the baseline configuration steps above, oftentimes you may configure common enhancements like Rich Ticket filing.
Rich Ticket Filing
Enhance the ticket creation flow with custom forms:
- Define fields to collect per domain/type.
- Auto-fill known information.
- Deliver form-based UX within chat.
You can view more details about the Rich Ticket Filing configuration in this guide.
Updated 13 days ago