You are here:
How an Incident Record Moves Through Omnichannel Routing
This is what the high-level workflow for omnichannel routing looks like for an incident.

使用較常見的搜尋字詞。
選取較少篩選條件以擴大您的搜尋。
You are here:
This is what the high-level workflow for omnichannel routing looks like for an incident.
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, and Unlimited Editions with Agentforce IT Service. |
An IT incident is reported through any channel and key details, such as subject, description, urgency, impact, and priority are captured.
After an incident is created, it is routed to a queue through one of these methods:
Since Omnichannel Routing is set up, after the incident is assigned to a queue, Salesforce routes it to the most suitable support rep through their Omni-Channel inbox. The IT rep receives a notification for the incoming incident and they can accept it from their Omni-Channel inbox to start working on it.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.