Utarbeidet med KI.
Routing rules determine who gets what. This guide presents a simple model that works, rather than a set of rules no one understands.
The first version should only send chat messages to the chat queue and emails to the email queue. Get it working, and build from there.
Route by topic or customer type when you have queues that are actually distinct. Routing to five queues with the same agents achieves nothing.
Rules are evaluated from top to bottom, and the first match wins. Put the most specific ones at the top; otherwise, a general rule will match everything.
Anything that doesn't match a rule has to go somewhere. Without a final rule, requests are left without a queue and are almost invisible.
Take ten inquiries from last week and check where they would have ended up. This reveals gaps faster than reading the rules.
See how many end up in the catch-all queue. If the proportion is high, you are missing a rule—or the rules are too narrow.
Still et spørsmål eller del hva som hjalp deg.

Publisert 7.10.2024
En portalløsning er en smart investering for mange virksomheter. Den gir ikke bare bedre kundeopplevelser og økt brukervennlighet, men også muligheten til å kutte betydelige kostnader gjennom effektiv selvbetjening.
Les merPublisert 1.10.2025
Det siste året har det skjedd mye i Dynamics 365 Customer Service - først og fremst innenfor AI og automatisering: Smartere verktøy, oversettelse i sanntid og trygg håndtering av data. Det gir bedre kundeopplevelser og mer effektive serviceteam.
Les merHar du et spørsmål eller en erfaring å dele?
Bli den første som bidrar.