--- title: Smart Handoff excerpt: '' deprecated: false hidden: true metadata: title: '' description: '' robots: index next: description: '' --- > 🚧 This covers only Moveworks Classic > > For Moveworks Copilot experiences, refer to **"[Moveworks Copilot - Feature Overview](/docs/moveworks-copilot-feature-overview)"** page. # Overview Moveworks Smart Handoff directs the user to the correct set of destinations when no resolution is provided by the bot. The **Smart Handoff** feature: * Intelligently routes employees to the right team or destination for further help. * Has configurable backstop after Moveworks attempts to answer the question. * Powered by domain recognition and user metadata. As part of **Enterprise Answers**, **Smart Handoff** hands the user off to the right set of destinations when no resolution is provided, as shown in the image below. These destinations include the following: * Filing into Ticketing System * **Live Agent Handoff** - URL-based, API, or channel (Teams, Slack Channel) * **URL** - to self-service portal, e.g. [https://linktoportal.com/](https://linktoportal.com/) * **Chat Channel ID (if Slack)** - CXXXXXXXXX (Slack Channel ID) * **Slack handle** - @John Smith * **Email Address** - [facilities@company.com]() * **Another Bot** - URL-based * …and more These handoff destinations or **items** can be configured by **context** - domain classification, language detected, language set, and user’s status, e.g. VIP (to name a few examples).  # How is Smart Handoff Configured? ## Background The Moveworks bot will be integrating within your company’s chat platform and interacting with users to provide answers in different categories. We need to come up with the text for the “Smart Handoff” to another category if no answer is available. In this guide, Moveworks will provide a standardized handoff template as a placeholder for the initial Smart Handoff experience. The contents of the example messages include verbiage across all defined categories, items, and their specifics. At the end, we will assemble and test the Smart Handoff.  ## Definitions We can group the Smart Handoff configurations into two distinct setups: 1. `single-domain`: Only one domain (category) is enabled in your environment such as Moveworks for IT or Moveworks for HR. 2. `multi-domain`: More than two domains are enabled in your environment such as Enterprise Service (up to eight domains, as mentioned below). Your Customer Success team will work with you to pick which setup is appropriate, *depending on the SKU that was purchased.* *** The Smart Handoff card has two major components: 1. An `item` represents a *single handoff destination*, e.g. email address, URL, file ticket, live agent chat, handoff to channel (to name a few). Helpful to think of an item as the lowest leaf level, e.g. a leaf node. 2. A `category` represents a visual grouping of items (once triggering items are determined, they will be displayed under their category). 1. A common paradigm is to have categories **represent individual domains**, e.g. IT, HR, Legal, etc. A single category can also represent one language (e.g. URL for german-speakers would be an `item` living under the German `category`). ## Select Out-of-the-box (OOB) Domains While this is a provided template for the newly added category, the “Smart Handoff” can be customized to cater to your specific needs. Users will also have the ability to navigate within different categories. A common paradigm is to set categories to domains, starting with the list below which are out-of-the-box:
| Domain | Moveworks Description |
|---|---|
| IT | Issues and requests pertaining to information technology, i.e. the use of computer systems to create, process, store, retrieve, and exchange electronic data and information. |
| HR | Issues and requests that typically fall under the purview of a human resources department. We consider most requests about the following topics to be HR domain: benefits, employee recruitment, training & development, performance appraisal, pay & benefits systems\*\*, organizational changes, & industrial relations, i.e. balancing organizational practices with requirements from laws & collective bargaining. * \*may also fall under Payroll |
| Facility | Issues and requests pertaining to workspaces and other facilities leased or owned by the organization.\ We consider requests about the following topics to be Facility domain: facility access badges, office supplies. facility information lookups, including of conference rooms, furniture, catering, cleaning, facility maintenance, other requests pertaining to the planning, design, construction, lease, occupancy, maintenance of facilities Potential overlap with IT: information technology infrastructure for an office or other facility, such as badge access and wifi networks. |
| Finance | Issues and requests pertaining to corporate finance or financial accounting. We include personal finance questions under this domain as well. We consider requests, queries, and issues about the following subjects to be Finance domain: financial transactions related to the organization (summary, analysis, reporting, and execution), including purchase orders and invoices, budgets, money, financial agreements with entities outside the organization, tools and analysis used to allocate financial resources, the capital structure of the organization, & short-term borrowing and lending |
| Legal | Legal requests and ethics/compliance questions, including anything related to contracts/master agreements with vendors, suppliers, partners, and customers. |
| Payroll | Requests pertaining to the process of calculating employee earnings, factoring out taxes and voluntary deductions such as 401(k) contributions and Employee Stock Purchase Plan (ESPP) contributions, and paying employees for their labor. |
| Procurement | Requests pertaining to the corporate process of sourcing and purchasing goods and services from an external source, like a third-party vendor or supplier. Includes vendor negotiation and vendor management, handling organizational purchase requests (requisitions), issuing purchase orders and developing term contracts. |
| Travel & Expense | Requests pertaining to travel logistics and reimbursements to employees for expenses. |