M365.FM - Modern work, security, and productivity with Microsoft 365

Mirko Peters - Founder of m365.fm, m365.show and m365con.net
  • 5.0 (3)
  • Tech News
  • Updated Daily

Welcome to the M365.FM — your essential podcast for everything Microsoft 365, Azure, and beyond. Join us as we explore the latest developments across Power BI, Power Platform, Microsoft Teams, Viva, Fabric, Purview, Security, and the entire Microsoft ecosystem. Each episode delivers expert insights, real-world use cases, best practices, and interviews with industry leaders to help you stay ahead in the fast-moving world of cloud, collaboration, and data innovation. Whether you're an IT professional, business leader, developer, or data enthusiast, the M365.FM brings the knowledge, trends, and strategies you need to thrive in the modern digital workplace. Tune in, level up, and make the most of everything Microsoft has to offer. M365.FM is part of the M365-Show Network. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

  1. 12h ago

    Dynamics 365 Opportunity Management - Simply Explained

    Dynamics 365 Opportunity Management gives sales teams a structured way to manage serious sales conversations from the first qualified interest through to a clear outcome: won or lost. Instead of keeping deal information across spreadsheets, emails, personal notes, and individual inboxes, Dynamics 365 Sales creates a shared opportunity record containing the customer, expected revenue, products, activities, probability, expected close date, ownership, and sales history. In this episode of M365 FM, Mirko Peters explains how opportunities work and how they connect the entire sales process. ㅤ WHAT IS AN OPPORTUNITY IN DYNAMICS 365? ㅤ A lead represents early interest, while an opportunity represents a potential sale with enough information to manage as a real sales conversation. An opportunity connects the possible deal to an account or contact and records what the customer might buy, how much the deal could be worth, who owns it, and when it could close. Think of an opportunity as a shared deal folder. Every serious buying conversation can have its own opportunity, even when multiple opportunities belong to the same customer. ㅤ HOW OPPORTUNITIES ENTER DYNAMICS 365 SALES ㅤ Many opportunities begin as leads. When a lead develops into a genuine buying conversation, the seller can qualify it and Dynamics 365 creates an opportunity while maintaining the connection to the original lead information. Opportunities can also be created directly. Existing customers may request additional products or services, partners may introduce potential buyers, or account managers may discover expansion and renewal opportunities during customer conversations. ㅤ THE FOUR SALES PIPELINE STAGES ㅤ Dynamics 365 Sales uses a Business Process Flow to guide opportunities through four standard stages: Qualify, Develop, Propose, and Close. During Qualify, sellers establish important facts such as the customer, timeframe, potential budget, purchasing process, and decision maker. Develop focuses on understanding customer needs, identifying stakeholders and competitors, and defining the proposed solution. During Propose, the sales team develops and reviews the proposal before presenting it to the customer. Close represents the final stage of the buying conversation, where the final proposal, expected decision date, and outcome become increasingly clear. ㅤ BUILDING AN OPPORTUNITY RECORD YOU CAN TRUST ㅤ The opportunity record becomes the central workspace for managing the deal. Estimated revenue shows how much the opportunity could generate, while the potential close date indicates when the customer is expected to make a decision. Probability provides additional context about the team's confidence in winning the opportunity. These values should change whenever the customer situation changes. Accurate opportunity information is essential because these records ultimately influence sales pipeline reporting and forecasting. ㅤ PRODUCTS, PRICING AND REVENUE ㅤ Opportunities can contain individual product line items representing what the customer may purchase. A software opportunity might include licenses, implementation services, training, and additional support. Products can include quantities, prices, and discounts, allowing expected revenue to reflect the actual proposed solution rather than simply an estimated number. Dynamics 365 also maintains consistent currency between the opportunity and its related product records. ㅤ ACTIVITIES, NOTES AND OWNERSHIP ㅤ Sales opportunities aren't only about numbers. Calls, emails, meetings, tasks, and notes provide the context behind the deal. Recording these activities helps everyone understand what happened with the customer and what needs to happen next. Each opportunity also has an owner responsible for keeping the sales conversation moving. Other specialists and managers can participate, but clear ownership prevents important actions from disappearing between team members. ㅤ WHY OPPORTUNITY DATA MATTERS FOR FORECASTING ㅤ Opportunity values and expected close dates contribute directly to the organization's view of potential future revenue. Outdated opportunity information therefore creates misleading forecasts. If a customer moves their decision from June to September, the opportunity should reflect that immediately. Keeping an old close date doesn't make the deal happen sooner; it simply gives sales management an inaccurate picture of the pipeline. ㅤ CLOSING OPPORTUNITIES AS WON OR LOST ㅤ Every opportunity should eventually reach a clear outcome. When the customer buys, the opportunity is closed as Won. When the customer decides not to proceed, it should be closed as Lost. Closing opportunities properly removes completed deals from the active pipeline while preserving their history inside Dynamics 365. Won opportunities show how successful deals developed, while lost opportunities can provide useful information about competitors, budget problems, delayed projects, or other reasons customers decided not to buy. ㅤ LEARNING FROM LOST OPPORTUNITIES ㅤ A lost opportunity still contains valuable sales intelligence. Recording meaningful loss reasons can help sales managers identify patterns across multiple deals. If several customers select the same competitor, postpone projects, or raise similar pricing concerns, leadership gains evidence that can inform future sales conversations, positioning, and strategy. Leaving unsuccessful opportunities permanently open hides these signals and artificially inflates the pipeline. ㅤ KEEPING THE SALES PIPELINE HONEST ㅤ Good opportunity management depends on continuously updating the record as the customer conversation changes. Sellers should update expected revenue, probability, decision dates, products, stakeholders, competitors, and activities when new information becomes available. When customers say yes, opportunities should be closed as Won. When customers say no, they should be closed as Lost. Deals shouldn't remain open simply because the sales team hopes circumstances might change. ㅤ THE KEY TAKEAWAY ㅤ Dynamics 365 Opportunity Management gives every serious sales conversation a structured home. From lead qualification and pipeline stages to products, revenue, activities, forecasting, and the final outcome, the opportunity record creates a shared picture of what is actually happening with the customer. Keep the deal record current and Dynamics 365 can provide sellers, managers, and leadership with a much more reliable view of the sales pipeline and potential future revenue. Subscribe to M365 FM for more Microsoft Knowledge Nuggets and Simply Explained episodes covering Dynamics 365, Microsoft 365, Power Platform, Azure, Copilot, AI, security, governance, and the Microsoft ecosystem. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

    Dynamics 365 Opportunity Management - Simply Explained

  2. 19h ago

    Dynamics 365 Omnichannel - Simply Explained

    A customer starts a website chat because an order has not arrived. They explain the problem, provide the order number, and answer several questions. Later, they call the company—and the person on the phone asks them to explain everything again. For the customer, this makes little sense. They did not start a new problem. They simply changed the way they contacted the company. In this episode of Microsoft Knowledge Nuggets on M365 FM, Mirko Peters explains Microsoft Dynamics 365 Omnichannel in plain English and shows how organizations can connect customer conversations across chat, voice, SMS, social messaging, and other service channels. We explore the unified agent workspace, customer identification, queues, Unified Routing, skills-based routing, agent presence, capacity, transfers, consultations, knowledge articles, quick replies, Copilot, Smart Assist, sentiment analysis, customer history, cases, transcripts, and supervisor analytics. The central idea is simple: customers can enter through many different doors, while agents work from one connected customer service desk. WHY SEPARATE CUSTOMER SERVICE CHANNELS CREATE PROBLEMS Traditional customer service often treats every communication channel as a separate system. Website chats appear in one application. Emails arrive in a shared mailbox. Calls are handled through another platform. Social messages may even be managed by a completely different department. Each system may work perfectly well individually, but the customer's story becomes fragmented. An agent answering the phone may not know that the customer already spent twenty minutes chatting with another employee earlier that day. The result is repetition, longer handling times, unnecessary searching, and frustrated customers. Dynamics 365 Omnichannel attempts to connect those pieces into a more consistent service experience. WHAT IS DYNAMICS 365 OMNICHANNEL? Think of Dynamics 365 Omnichannel as an office building with several front doors but one reception desk. Customers can enter through different communication channels. One person might use website chat. Another calls. Another sends a text message. Another contacts the organization through a supported social messaging channel. Behind those different entry points, Dynamics 365 provides a common customer service environment. The channel still matters because a live telephone call behaves differently from an asynchronous text conversation. But agents do not necessarily need completely separate working environments for every channel. THE UNIFIED AGENT WORKSPACE The agent workspace is where customer conversations come together. Instead of switching continually between a chat application, telephone system, CRM, knowledge base, and customer records, agents can work with conversations alongside relevant Dynamics 365 information. Each active piece of work can appear as a session or conversation. An agent might handle one customer chat and later move to another session without losing the original context. The workspace can also provide access to customer details, previous cases, activities, knowledge, notes, and other service information. This changes the agent's starting point from: "Can you explain everything again?" to: "I can see your previous interaction. Let's continue from there." IDENTIFYING THE CUSTOMER Connected customer history depends on knowing who the customer is. Sometimes Dynamics 365 already knows. For example, a customer may begin a conversation while authenticated through a connected customer experience. In other situations, somebody starts as an unknown website visitor. The agent can then request information such as an email address or order number and search for an existing contact. Once the conversation is associated with the correct customer or case, the transcript, notes, activities, and related service work can contribute to that customer's history. Customer identification is therefore an important part of making omnichannel actually feel connected. CASES KEEP CUSTOMER ISSUES TOGETHER Some questions can be solved during a single conversation. Others require follow-up. A case provides a structured Dynamics 365 record for an issue that needs to be tracked until resolution. Imagine a customer contacts support about a missing delivery. The initial chat does not solve the problem because another department needs to investigate. The agent creates or associates a case. When another employee later works on the issue, they can open that case and review the information already collected. The customer problem now has a persistent home instead of existing only inside one temporary conversation.  ROUTING: GETTING CUSTOMERS TO THE RIGHT TEAM A unified workspace is useful only when customer requests reach appropriate employees. This is where routing becomes important. Dynamics 365 can place incoming work into queues representing different areas of responsibility. An organization might have queues for: Billing, deliveries, technical support, sales, or another service function. Routing rules can use information collected from the customer to determine where the conversation belongs. A billing question can go toward billing. A delivery problem can go toward the delivery team. The customer does not need to understand the queue architecture. They simply describe what they need. SKILLS-BASED ROUTING Being available does not automatically make somebody the correct agent. A customer may need assistance in German. Another customer may require an employee who understands a particular product. Another request may require specialized account knowledge. Dynamics 365 can use skills to describe what agents can handle and match those capabilities with customer requirements. Instead of routing work only according to who happens to be free, the system can consider whether the employee is actually suitable for the conversation. This can reduce transfers and improve the chance that the first agent receiving the request can help. PRESENCE AND AGENT CAPACITY The correct agent also needs to be available. Presence indicates whether an employee is available, busy, away, offline, or in another configured state. Capacity helps represent how much work that employee can handle. A voice call may require almost complete attention. Messaging conversations can behave differently because customers frequently pause between messages. An organization can therefore define workload rules appropriate to its service model. This helps avoid situations where one qualified employee receives conversation after conversation while another suitable agent remains available. TRANSFERS VS CONSULTATIONS Sometimes a conversation reaches the wrong team. An agent discovers that a customer actually needs billing rather than technical support. In that situation, the conversation can be transferred to another appropriate queue or person. But not every specialist question requires transferring the customer. A consultation allows the original agent to involve another employee for assistance while remaining responsible for the customer conversation. Instead of saying: "I'll transfer you." the agent can effectively say: "I'm checking this with our specialist." That distinction can reduce unnecessary handoffs and provide customers with a more continuous service experience.  KNOWLEDGE ARTICLES AND QUICK REPLIES #Agents answer many similar questions every day. How do I reset my password? How do I return an item? Where can I download an invoice? What does this error message mean? Knowledge search allows employees to find approved information while the customer conversation remains open. Agents can use the article to guide their answer and, where appropriate, provide relevant information to the customer. Quick replies provide another productivity tool. Frequently used messages can be prepared in advance so employees do not need to type identical responses repeatedly. The agent still needs to review the response and make sure it actually fits the customer's situation. COPILOT AND SMART ASSIST AI capabilities can provide additional assistance where the organization has enabled them. Smart Assist can surface potentially useful knowledge articles, related information, or guidance. Copilot can help summarize longer conversations and, depending on the configured capabilities, assist with suggested responses. Imagine a customer spending ten minutes interacting before reaching a human agent. Instead of forcing the agent to read the complete conversation before understanding the problem, a summary can provide a faster overview of what the customer requested and what has already happened. These capabilities support the agent. They do not remove the need for review. The employee remains responsible for making sure information provided to the customer is appropriate and accurate.  VOICE, TRANSCRIPTION AND SENTIMENT Voice scenarios can also include additional assistance. When supported voice capabilities are configured, live transcription can convert spoken conversation into text. This can help agents review product numbers, customer concerns, or commitments made during a call. Sentiment signals can provide another indicator. If a conversation appears increasingly negative, the agent may decide to slow down, clarify the problem, or acknowledge the customer's frustration more explicitly. But sentiment should not be treated as a definitive interpretation of someone's emotions. Sarcasm, language differences, communication style, and context can all affect the signal. Sentiment is therefore best treated as another piece of information—not a verdict about the customer.  Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

    Dynamics 365 Omnichannel - Simply Explained

  3. 22h ago

    Dynamics 365 Relationship Intelligence - Simply Explained

    A Dynamics 365 Sales opportunity can look healthy on paper. The deal is still open, the estimated close date is in the future, and the timeline contains emails, meetings, calls, and tasks. But there is a much more important question: Is the customer still talking to you? A salesperson may have sent several emails without receiving a response. The last customer meeting may have happened weeks ago. Another employee inside the company may already know an important decision-maker, but the salesperson has no idea that relationship exists. In this episode of Microsoft Knowledge Nuggets on M365 FM, Mirko Peters explains Microsoft Dynamics 365 Relationship Intelligence in plain English and explores how Dynamics 365 Sales can turn everyday customer communication into useful relationship signals. We look at Relationship Analytics, Relationship Health, Who Knows Whom, Microsoft Exchange integration, communication activity, response times, engagement, customer sentiment, similar opportunities, warm introductions, opportunity management, and sales pipeline prioritization. The goal is not to let Dynamics 365 decide whether a deal will close. The goal is to give sellers better context for deciding which customer relationship needs attention and what conversation should happen next. THE HIDDEN PROBLEM INSIDE CRM DATA A CRM system can contain enormous amounts of customer information. Contacts. Accounts. Opportunities. Activities. Emails. Tasks. Meeting notes. Phone calls. But having information does not automatically mean understanding the relationship. A salesperson can open an opportunity containing ten recent activities and assume the deal is moving forward. But what if nine of those activities came from the salesperson? What if the customer stopped replying? What if no future meeting is scheduled? What if the last meaningful conversation happened a month ago? The CRM record may look active while the actual customer relationship has become quiet. Relationship Intelligence attempts to expose that difference. ACTIVITY DOES NOT AUTOMATICALLY MEAN ENGAGEMENT One of the most important ideas behind Relationship Intelligence is that activity needs context. Ten unanswered emails do not necessarily represent a strong relationship. Several internal tasks do not mean the customer is engaged. A large number of activities may simply mean the salesperson has been busy. By contrast, one meaningful conversation with the right decision-maker may move an opportunity significantly further than dozens of unanswered messages. Relationship Intelligence therefore looks beyond the existence of activities and helps sellers understand the communication patterns behind them. Is communication recent? Is the customer responding? Are both sides participating? Has the relationship suddenly become quiet? Those questions can reveal considerably more than a simple activity count. WHAT IS DYNAMICS 365 RELATIONSHIP INTELLIGENCE? Think of Relationship Intelligence as a relationship radar inside Dynamics 365 Sales. It brings together communication signals associated with leads, contacts, accounts, and opportunities and turns them into information sellers can use while working inside Dynamics 365. The supplied episode focuses on two major capabilities. The first is Relationship Analytics and Relationship Health. These capabilities help sellers understand communication patterns and identify relationships that may require attention. The second is Who Knows Whom. This capability helps identify colleagues inside the organization who may already know a lead or contact the seller wants to reach. Together, these capabilities answer two different but related questions: How healthy is the relationship we already have? and Who inside our organization can help us create a new relationship? RELATIONSHIP ANALYTICS Relationship Analytics takes activities associated with a sales record and transforms them into a communication picture that is easier to interpret. Instead of manually opening every email, appointment, and call, sellers can examine the overall pattern. Relationship Analytics can be relevant across contacts, accounts, leads, and opportunities. Each provides a slightly different perspective. A contact focuses on the relationship with an individual person. An account provides a broader view of communication with the customer organization. A lead can show whether an early sales conversation remains active. An opportunity connects communication signals with a potential deal. The purpose is not to reduce the relationship to a number. It is to help sellers notice communication patterns that deserve closer investigation. BASIC RELATIONSHIP INSIGHTS The episode distinguishes between Basic Relationship Insights and enhanced capabilities. Basic insights use emails, phone calls, and appointments that have been sent, received, or recorded in Dynamics 365. When a related activity is completed, those basic measures can update close to real time. That makes activity tracking extremely important. If a customer call occurs but nobody records it against the correct Dynamics 365 record, Relationship Intelligence cannot properly include that conversation. If an activity is connected with the wrong account or opportunity, the resulting picture becomes less useful. Relationship Intelligence can analyze captured communication. It cannot analyze conversations that the organization never captured. ENHANCED RELATIONSHIP INSIGHTS Organizations with the appropriate Dynamics 365 Sales licensing and configuration can use enhanced relationship insights. The episode explains that these capabilities can combine information from Dynamics 365 with email and meeting information from Microsoft Exchange when server-side synchronization is configured. This gives Dynamics 365 access to a broader communication picture. There is an important timing difference. Basic insights can update close to real time when relevant Dynamics 365 activities are completed. Enhanced insights operate on a 24-hour update cycle according to the supplied episode. That means sellers should not necessarily expect a message sent several minutes ago to immediately affect every enhanced relationship measure. EMAIL SENT VS EMAIL RECEIVED One useful relationship measure compares emails sent by the organization with emails received from the customer. Imagine a salesperson sends eight emails. The customer replies once. That does not automatically mean the opportunity is failing. Perhaps the customer prefers meetings or telephone calls. But the pattern raises a useful question: Are we having a conversation, or are we repeatedly sending messages without meaningful engagement? The opposite pattern can also expose problems. Perhaps the customer repeatedly sends questions while the sales team responds slowly. In that situation, the customer may be highly engaged while the organization itself is creating friction. The metric does not provide the answer. It tells the seller where to investigate. THE 60-DAY RELATIONSHIP ACTIVITY VIEW The episode describes a Relationship Activities view that looks across 60 days of communication activity. Instead of showing only a total number, the view separates activities by date and type. Sellers can examine patterns involving emails sent and received, meetings sent and received, and phone calls made and received. This makes the rhythm of the relationship visible. A customer relationship containing regular communication across the entire period looks very different from one containing intense activity during the first week followed by several weeks of silence. The quiet period could mean many things. Perhaps a proposal was delivered and nobody followed up. Maybe a meeting was cancelled. Perhaps the customer deliberately asked the seller to wait until another date. Relationship Analytics shows the pattern. The salesperson provides the business context. RESPONSE TIME AS A SALES SIGNAL Enhanced insights can also include response time. This compares how quickly sellers respond to customers with how quickly customers respond to sellers. Slow customer responses can indicate reduced attention. But slow seller responses can create exactly the same problem from the opposite direction. If an interested customer repeatedly waits several days for answers, they may eventually stop asking questions. Response time can therefore expose small problems before they become larger sales issues. It gives sellers and managers another signal for understanding whether communication is moving naturally or becoming increasingly difficult. HOURLY INVESTMENT Another enhanced measure discussed in the episode is hourly investment. This compares the amount of time the organization spends around a sales record with the amount of time customer contacts spend. Imagine two opportunities. In the first, the sales team spends many hours on meetings, calls, and communication while the customer contributes relatively little time. In the second, both sides regularly participate. Those represent different engagement patterns. Hourly investment does not determine which opportunity will close. A short conversation with a senior decision-maker may be considerably more important than several long meetings. But the metric can highlight situations where effort appears heavily one-sided.  Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

    Dynamics 365 Relationship Intelligence - Simply Explained

  4. 1d ago

    Dynamics 365 Customer Service Workspace - Simply Explained

    A customer sends an email, starts a chat, calls support, or contacts a company through another service channel. When an agent picks up that request, they need the complete customer story quickly. What did the customer already tell us? Which product do they own? Has somebody else worked on this problem? Is there an existing case? What was promised previously? Is there a service deadline approaching? Without a unified workspace, answering those questions can mean jumping between browser tabs, inboxes, CRM records, notes, knowledge bases, and communication applications. In this episode of Microsoft Knowledge Nuggets on M365 FM, Mirko Peters explains Dynamics 365 Customer Service Workspace, now known as Copilot Service Workspace, in plain English. We explore sessions and tabs, cases and timelines, omnichannel customer service, the agent inbox, Smart Assist, knowledge management, agent scripts, macros, quick replies, Copilot, Microsoft Teams collaboration, Unified Routing, queues, presence, capacity, SLA management, escalation, self-service, dashboards, and customer service analytics. The central idea is straightforward: give customer service agents one organized workspace where the customer, the problem, the history, the knowledge, and the tools required to solve it remain connected. WHAT IS DYNAMICS 365 CUSTOMER SERVICE WORKSPACE? Dynamics 365 Customer Service Workspace was designed as a focused working environment for customer service agents. Microsoft now refers to this newer agent experience as Copilot Service Workspace, so organizations may encounter both names in documentation, videos, training materials, or existing environments. Think of it as a browser designed specifically around customer service. Instead of opening a completely separate browser window for every customer, case, knowledge article, product record, and conversation, the workspace organizes related information around the piece of customer work currently being handled. The objective is not simply to display CRM records. It is to help agents move between multiple customer issues without repeatedly losing and rebuilding context. WHY CUSTOMER SERVICE AGENTS NEED A DIFFERENT WORKSPACE Imagine an agent halfway through a customer call. A high-priority email arrives. Another customer replies to yesterday's chat. A different case is approaching its promised response deadline. This is normal customer service work. Agents frequently manage several customers, several communication channels, and substantial histories for each customer simultaneously. They need to understand what the customer purchased, what already happened, who previously worked on the issue, and whether somebody promised a response. When that information lives across multiple systems, the agent becomes an information detective. Customer Service Workspace attempts to remove some of that detective work. THE PROBLEM WITH CONSTANT CONTEXT SWITCHING Consider the traditional workflow. An agent searches an email inbox for an old customer message. They open the customer record in another browser tab. They find a case. Another application contains internal notes. A knowledge base contains troubleshooting instructions. Then another customer contacts them. The agent changes context. Ten minutes later, they return to the first customer and need to remember why several browser tabs are open. The applications may all work correctly individually. The problem is that the customer story is fragmented across them. That fragmentation becomes visible to customers when they hear: "Can you tell me that again?" or: "Let me find the previous update." Customer Service Workspace attempts to keep more of that story together. FROM CUSTOMER SERVICE HUB TO COPILOT SERVICE WORKSPACE Many Dynamics 365 users will be familiar with the older Customer Service Hub experience. Customer Service Hub supported core service activities such as working with cases, customer records, activities, knowledge articles, and dashboards. Customer Service Workspace introduced a different style of agent experience focused more heavily on handling several active pieces of work while preserving the context associated with each one. The supplied episode describes Microsoft subsequently naming this experience Copilot Service Workspace. The underlying concept remains an agent-focused workspace where customer service information and tools are organized around active work.  THE AGENT DESK, NOT THE ADMINISTRATION CONTROL ROOM Copilot Service Workspace is primarily where agents perform their daily customer service work. It is not where every customer service rule is designed. Administrators configure areas such as channels, queues, routing rules, permissions, skills, capacity, and other service settings through the relevant administration experiences. The agent experiences the result of that configuration inside the workspace. Think of the distinction like this: The administration environment is the control room. Copilot Service Workspace is the service desk. Agents should be able to focus primarily on customers rather than the technical configuration behind how customer work reached them. SESSIONS: ONE CUSTOMER ISSUE, ONE WORKING CONTEXT One of the most important concepts inside the workspace is the session. Think of a session as a labeled desk drawer. One drawer contains everything associated with one customer's active issue. Another drawer contains another customer's conversation. Opening one drawer should not mix its contents with another. Inside Copilot Service Workspace, a session provides a boundary around a particular piece of customer work. That makes it easier for agents to manage several active issues without mixing their records, notes, and supporting information. TABS: EVERYTHING RELATED TO THE CUSTOMER ISSUE Inside each session are tabs. The first tab might contain the case. The agent clicks the customer and opens the customer record as another tab. They might then open the associated account. Another tab could contain the product. Another could contain a knowledge article. Another might contain an email. These are separate records, but they belong to the same customer story. Instead of scattering those records across unrelated browser windows, the workspace keeps them grouped inside the session. This gives agents the freedom to explore connected information without losing the original customer issue. ㅤ  A SIMPLE SESSION EXAMPLE Imagine a customer contacts support because their coffee machine stopped working. The agent opens the case. That becomes the working session. The case contains the reported problem and current status. The agent clicks the customer's name. The customer record opens as another tab inside the same session. The agent reviews previous support interactions. Next, they open the product record to determine which coffee machine model the customer owns. Then they find an approved troubleshooting article. That article opens in another tab. The agent can move between the case, customer, product, and knowledge article while everything remains associated with the same customer issue. MULTIPLE CUSTOMERS WITHOUT MIXING THEIR INFORMATION Now imagine another customer contacts support. Their problem has nothing to do with the coffee machine case. Instead of adding more unrelated tabs to the existing workspace, the second customer receives a separate session. That session has its own tabs, records, and context. The first customer remains in one drawer. The second remains in another. This separation can reduce simple but potentially serious mistakes. When agents handle several cases simultaneously, it can be easy to type a note on the wrong record, lose track of which customer owns which information, or accidentally continue working from the wrong context. Sessions provide clearer boundaries between those customer stories. SESSION AND TAB LIMITS The supplied episode states that Copilot Service Workspace supports up to nine sessions at one time, with up to ten tabs within each session. The important point is not that agents should spend their day counting tabs. It is that a customer case rarely exists alone. A service issue can connect to contacts, accounts, products, activities, emails, knowledge articles, notes, and other business information. The workspace gives those connected records somewhere to remain together while the agent works. SESSION RESTORE A browser refresh during a complicated customer case can be disruptive. The supplied material describes a session restore feature in preview that administrators can enable. With session restore enabled, supported records and tabs can be restored following a browser refresh rather than forcing the agent to begin again from an empty home page. The episode notes that supported cases, accounts, related tabs, and the agent's previous focus can return after presence loads, while active conversations such as chats and calls can also return. This can help preserve context when a refresh occurs at exactly the wrong moment. Agents still need to save their work appropriately. A workspace can restore supported context, but it cannot protect information that was never saved.  Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

    Dynamics 365 Customer Service Workspace - Simply Explained

  5. 1d ago

    Dynamics 365 Forecasting - Simply Explained

    Dynamics 365 Forecasting helps sales teams answer one of the most important questions in business: are we going to hit our sales target? Instead of collecting numbers from spreadsheets, emails, and individual sales reports, Dynamics 365 Sales brings opportunities, expected revenue, close dates, forecast categories, quotas, and sales performance into one shared forecasting view. In this episode of M365 FM, Mirko Peters explains how Dynamics 365 Forecasting works, how forecast categories represent confidence, and why accurate opportunity data is essential for reliable revenue forecasting. ㅤ WHAT IS DYNAMICS 365 FORECASTING? ㅤ Dynamics 365 Forecasting turns the opportunities your sales team already manages in Dynamics 365 Sales into a structured view of expected revenue. A sales forecast isn't a guarantee of future revenue. It's a continuously changing estimate based on what the sales organization currently knows about its open opportunities. The forecast combines important information including expected deal value, expected close dates, sales quotas, ownership, and confidence. This allows sellers and sales managers to understand not only how much potential revenue exists, but how realistic that revenue is for the current forecasting period. ㅤ FROM SPREADSHEETS TO A SHARED SALES FORECAST ㅤ Traditional forecasting often depends on individual spreadsheets that sellers update at different times. Managers then collect those files, consolidate the numbers, and try to determine which version contains the latest information. Dynamics 365 Sales changes this process by building forecasts from opportunity data already maintained by the sales organization. Instead of creating another reporting process, forecasting becomes part of everyday sales management. Everyone can work from the same underlying opportunity information. ㅤ UNDERSTANDING THE FORECAST GRID ㅤ The Dynamics 365 forecast grid acts like a shared sales scorecard. Depending on how forecasting is configured, rows can represent individual sellers, teams, territories, or products. Columns can show quota, forecast amounts, and different levels of forecast confidence. Managers can move beyond headline revenue numbers and drill into the opportunities behind those totals. This makes forecast conversations more practical because teams can discuss specific deals, changes in close dates, customer decisions, and pipeline risks instead of debating spreadsheet numbers. ㅤ FORECAST CATEGORIES EXPLAINED ㅤ Forecast categories provide a common language for describing the confidence behind each opportunity. Pipeline represents opportunities that are still relatively early or uncertain. Best Case represents opportunities showing meaningful progress but which are not yet reliable enough to treat as expected revenue. Committed represents opportunities where the customer has provided a strong verbal or contractual commitment, although the sale has not officially closed. Omitted removes an opportunity from forecast totals without deleting the opportunity from Dynamics 365 Sales. Won and Lost are handled differently. When opportunities are formally closed, Dynamics 365 updates their final status accordingly. Together, these categories allow teams to see the difference between potential revenue, realistic upside, and high-confidence opportunities. ㅤ FORECASTING FOR SELLERS AND SALES MANAGERS ㅤ Different roles can use the same forecasting data for different decisions. Individual sellers can compare their current forecast against quota and identify where they need to focus their attention. A seller who has a large gap between expected revenue and target can determine whether existing opportunities need attention or whether additional pipeline must be created. Sales managers can view the entire team and then drill into individual sellers and opportunities. This makes coaching more specific. Instead of simply asking why someone's forecast is low, managers can discuss actual opportunities, customer activity, delayed close dates, missing proposals, and the next actions required to move deals forward. ㅤ FORECAST HIERARCHIES AND ROLLUPS ㅤ Dynamics 365 Forecasting can aggregate opportunity information through different organizational structures. An organizational hierarchy can follow reporting relationships, while territory-based forecasts can organize revenue around geographic or assigned markets. Product forecasts can show expected revenue based on what the company sells. These rollups allow sellers, managers, directors, and leadership to work from connected sales data while viewing the information at the level appropriate to their responsibilities. ㅤ AI AND SALES FORECASTING ㅤ AI can provide additional signals around sales opportunities, but it doesn't know exactly which customers will buy. Opportunity scoring and related sales intelligence can analyze patterns such as customer interactions, meetings, emails, sales stages, opportunity values, and previous sales activity. These signals can help sellers and managers identify opportunities that may require attention. A low score should therefore be treated as another piece of information rather than a final decision about whether an opportunity will close. ㅤ WHY DATA QUALITY MATTERS ㅤ Even sophisticated forecasting technology cannot compensate for inaccurate sales data. If an opportunity has an outdated close date, incorrect expected revenue, or an unrealistic forecast category, those errors can flow directly into the forecast. Sellers should keep opportunity amounts, expected close dates, ownership, and forecast categories current whenever the customer situation changes. Accurate forecasting starts with accurate opportunity management. ㅤ HUMAN JUDGMENT STILL MATTERS ㅤ Sales data cannot capture every detail of a customer relationship. Budget changes, competitors, internal customer reorganizations, new decision makers, delayed projects, and changing priorities can dramatically affect an opportunity. The strongest forecasting process combines structured Dynamics 365 data with the knowledge of the people actually speaking with customers. Managers can use forecast reviews to understand what changed, challenge assumptions, and determine whether opportunities still belong in their current forecast categories. ㅤ BUILDING A RELIABLE FORECASTING RHYTHM ㅤ Reliable forecasting depends on regular updates rather than a last-minute cleanup before a leadership meeting. Sellers should review open opportunities throughout the week and update values, expected close dates, ownership, and forecast categories when circumstances change. Forecast reviews can then focus on meaningful questions: Which deals moved forward? Which opportunities slipped? Where is revenue at risk? Is there enough pipeline to reach quota? Which opportunities need immediate attention? This turns forecasting from a reporting exercise into an active sales management process. ㅤ THE KEY TAKEAWAY ㅤ Dynamics 365 Forecasting transforms everyday sales opportunity data into a shared view of expected revenue, confidence, quota performance, and pipeline risk. Sellers can understand where to focus their effort, managers can identify problems earlier, and leadership gains a clearer picture of expected business performance. But the quality of the forecast ultimately depends on the quality of the information behind it. Keep opportunity data accurate, use forecast categories consistently, and combine the numbers with human judgment. That's when Dynamics 365 Forecasting becomes a practical tool for sales planning rather than another report. Subscribe to M365 FM for more Microsoft Knowledge Nuggets and Simply Explained episodes covering Dynamics 365, Microsoft 365, Power Platform, Azure, Copilot, AI, security, governance, and the Microsoft ecosystem. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

    Dynamics 365 Forecasting - Simply Explained

  6. 1d ago

    AI Turns Integration into an Organism as a Service — How Azure Logic Apps Are Changing Enterprise Integration with Sonny Gillissen [MVP]

    Enterprise integration is everywhere, yet most people only notice it when something stops working. Applications need to communicate, APIs need to exchange information, ERP systems need to connect with business processes, and data needs to move reliably across organizational boundaries. For decades, integration has largely followed a deterministic model: when this happens, do that. Developers and architects define triggers, conditions, transformations, retries, exceptions, and destinations in advance. But what happens when AI becomes part of that integration layer? In this episode of M365 FM, Mirko Peters talks with Sonny Gillissen [MVP], an Azure Integration Services specialist with a particular focus on Azure Logic Apps, about a concept he calls “Organism as a Service.” The idea is that enterprise integration can evolve from static workflows into systems capable of interpreting context, responding to unexpected situations, choosing appropriate actions, and potentially recovering from failures more intelligently. The conversation covers Azure Logic Apps, Azure Integration Services, API Management, Azure Functions, Azure Service Bus, Event Grid, managed connectors, managed identities, Azure Key Vault, Infrastructure as Code, Bicep, Terraform, CI/CD, observability, Log Analytics, security, least privilege, network isolation, AI agent loops, self-healing integrations, and the future of intelligent enterprise integration. WHY ENTERPRISE INTEGRATION MATTERS Integration has effectively become infrastructure. Employees open an application and expect the information they need to appear. Customers place orders and expect them to reach the correct systems. Financial transactions move through ERP platforms. APIs exchange information. Events trigger downstream processes. From the user's perspective, this often feels automatic. Sonny compares it to turning on a water tap: people expect water to flow without thinking about everything happening behind the wall. Enterprise integration works similarly. The complexity becomes invisible until something fails. Behind seemingly simple processes can be dozens of applications, APIs, business rules, security controls, identities, transformations, queues, monitoring systems, and organizational responsibilities. Integration therefore isn't simply about connecting application A with application B. It is about keeping business processes operating across systems that were often never originally designed to work together. WHY ENTERPRISE INTEGRATION BECOMES SO COMPLEX The technology itself is not always the primary source of complexity. Enterprise business processes are complicated. ERP environments such as SAP and Microsoft Dynamics contain extensive transactional processes because financial and operational activities need control, consistency, and auditing. Multiple departments participate. Business knowledge remains distributed among employees. Organizations accumulate years of architectural decisions. Eventually, integration architecture begins reflecting all of that organizational complexity. Sonny argues that a good integration consultant therefore needs to look beyond the technical request. Instead of simply asking “How do we connect these systems?”, the more important question is: “What is the organization actually trying to accomplish?” Simplifying integration starts by understanding the business process behind it. WHAT MAKES A GOOD INTEGRATION ARCHITECTURE? An integration that works today is not necessarily a good integration. Sonny highlights reusability and security as particularly important characteristics. Modern integration architectures should become increasingly composable. Instead of rebuilding the same functionality repeatedly, organizations should be able to reuse components in different processes. Security is equally fundamental. Integration services frequently connect highly privileged business systems. Poorly designed access can turn an integration platform into an extremely attractive attack path. A successful request is therefore only one measure of integration quality. The architecture also needs to remain reusable, supportable, secure, observable, and adaptable as business requirements change. WHAT ARE AZURE INTEGRATION SERVICES? Azure Integration Services is not one product. It is a collection of Microsoft Azure capabilities that can be combined to build enterprise integration architectures. During the conversation, Sonny and Mirko discuss five major technologies: Azure Logic Apps provides workflow orchestration and low-code integration. Azure API Management provides an API gateway and management layer. Azure Functions provides serverless code for scenarios where pro-code functionality is appropriate. Azure Service Bus supports messaging and helps decouple systems. Azure Event Grid provides event-driven integration capabilities. Different services solve different pieces of the integration problem, and real enterprise architectures frequently combine several of them. AZURE LOGIC APPS VS AZURE FUNCTIONS One recurring architectural question is whether a particular integration should use Azure Logic Apps or Azure Functions. There is no universal answer. Organizations with strong low-code expertise may find Logic Apps particularly effective because developers and integration specialists can visually construct workflows. Organizations with experienced .NET development teams may prefer Azure Functions for scenarios where custom code provides greater flexibility. The important point is that this does not need to become an ideological choice between low code and pro code. An enterprise integration architecture can use both. Logic Apps can orchestrate processes while Functions provide specialized code where required. WHY AZURE SERVICE BUS MATTERS Azure Service Bus plays an important role in decoupling enterprise systems. Without a messaging layer, application A may directly depend on application B being available. That creates tight coupling. Introducing Service Bus can separate those systems. Application A can send information to Service Bus, while application B processes it according to the architecture. This can make backend integrations more resilient and provide opportunities for reprocessing. Sonny notes that Service Bus is not automatically appropriate for every synchronous scenario because adding asynchronous messaging can affect response time and user experience. But for backend processing and decoupled architectures, he considers it an important component.  WHY SONNY SPECIALIZES IN AZURE LOGIC APPS One reason Sonny focuses heavily on Azure Logic Apps is visibility. Traditional code requires developers to deliberately implement logging and monitoring. A Logic App provides a visual workflow and run history. After executing a workflow, developers can inspect what happened, which actions executed, what results were produced, and where failures occurred. This allows integration specialists to spend more time thinking about the business process and less time building basic troubleshooting infrastructure. For people who naturally think visually about processes rather than primarily through code, this can make Logic Apps particularly effective. THE DEVELOPER MISUNDERSTANDING ABOUT LOGIC APPS Developers sometimes assume that writing custom code will always be faster or more powerful than using a visual integration platform. For some scenarios, that may be true. But the calculation needs to include more than the time required to write the core functionality. Monitoring matters. Logging matters. Deployment matters. Error handling matters. Operations matter. Maintenance matters. Logic Apps provides significant platform functionality around the workflow itself. Sonny also discusses codeful workflows as an attempt to bridge the gap between visual Logic Apps development and traditional pro-code development approaches. LOGIC APPS SHOULD BE TREATED AS CODE Low code does not mean organizations should abandon software engineering practices. Sonny recommends treating Logic Apps as code and deploying them through CI/CD. An organization could manually create something in development, export it, and reproduce it in another environment. But manual deployment creates an obvious risk: Eventually, somebody forgets something. Development and production begin to differ. Those differences become operational problems. Automated deployment provides repeatability and helps organizations maintain consistent environments. INFRASTRUCTURE AS CODE WITH LOGIC APPS Azure Logic Apps can be deployed as part of an Infrastructure as Code strategy. The episode discusses ARM templates, Bicep, and Terraform. Infrastructure as Code describes the desired Azure environment deterministically. The configuration can define resources, SKUs, locations, resource groups, and other infrastructure properties. Bicep provides a more concise Azure-focused authoring experience while ultimately relating closely to ARM deployment. Terraform provides another approach for defining and deploying infrastructure. The important architectural principle is repeatability. Integration infrastructure should not depend entirely on somebody remembering which buttons they clicked in the Azure portal. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

    AI Turns Integration into an Organism as a Service — How Azure Logic Apps Are Changing Enterprise Integration with Sonny Gillissen [MVP]

  7. 1d ago

    Dynamics 365 Remote Assist - Simply Explained

    A machine stops in the middle of a shift. The technician standing beside it can see the problem, but the person with the deepest knowledge of that machine may be hundreds or thousands of kilometers away. Traditionally, solving that problem could involve telephone calls, photographs, emails, unclear descriptions, repeated questions, or eventually sending a specialist to the site. The challenge is not necessarily that expertise does not exist. The challenge is getting that expertise to the place where the work is happening. In this episode of Microsoft Knowledge Nuggets on M365 FM, Mirko Peters explains Microsoft Dynamics 365 Remote Assist in plain English and explores how frontline workers can connect with remote experts through live video, visual guidance, Microsoft Teams, mobile devices, mixed reality, and connected Dynamics 365 processes. We look at how Remote Assist supports field service, manufacturing, maintenance, inspections, troubleshooting, training, remote collaboration, Microsoft Teams, Dynamics 365 Field Service, Microsoft 365 identity and security, and mixed reality scenarios. The central idea is simple: instead of trying to describe a physical problem to someone who cannot see it, let the expert see what the frontline worker sees. THE PROBLEM WITH REMOTE TECHNICAL SUPPORT Many frontline jobs happen far away from a desk. Maintenance employees work beside production equipment. Field technicians visit customer locations. Inspectors examine physical components. Engineers install machinery. Service teams troubleshoot equipment in warehouses, factories, offices, hospitals, or other facilities. When something unexpected happens, the employee on site can see the problem directly. They might hear an unusual sound. They might notice a loose cable. A warning light might appear. A component may not fit correctly. The difficulty begins when the employee needs help from someone who is somewhere else. The remote expert cannot initially see any of those details. The technician has to translate a physical situation into words. That translation creates opportunities for misunderstanding.  WHY PHONE SUPPORT HAS LIMITATIONS Imagine calling an expert and saying: "There's something wrong with the connector at the back." The sentence makes perfect sense to the technician standing beside the machine. But the remote expert immediately has several questions. Which connector? Which side of the machine? What is connected to it? What does the surrounding equipment look like? Is there visible damage? Is another component positioned incorrectly? The technician describes the situation. The expert tries to reconstruct the machine mentally. Both people may eventually understand each other, but valuable time can disappear simply establishing which physical object they are discussing. Dynamics 365 Remote Assist was designed to reduce that gap by creating a shared visual context. PHOTOS ARE USEFUL BUT STATIC Photographs improve remote support because the expert can finally see something. But a photograph represents one moment from one angle. The expert might reply: "Can you send another picture from the side?" The technician takes another photograph. Then the expert needs a close-up. Another photograph. Then they need to understand where that component sits relative to another part. Another photograph. Meanwhile, the technician may have moved, removed another panel, or discovered a different problem. Live video changes this interaction because the expert can ask the technician to move the camera immediately. Instead of exchanging snapshots of the problem, both people can explore the physical environment together. WHAT IS DYNAMICS 365 REMOTE ASSIST? Dynamics 365 Remote Assist is a Microsoft application designed to connect a frontline worker with a remote expert while keeping the conversation focused on the physical work being performed. The worker can share live video of the equipment, environment, or problem. The remote expert sees the same physical scene and can provide guidance while the technician remains beside the equipment. The worker might use a supported smartphone or tablet. For appropriate hands-free scenarios, supported mixed reality headsets can provide another experience. The objective is not to make the remote expert physically present. It is to give that expert enough visual context to provide more useful assistance without immediately traveling to the location. ㅤ LIVE VIDEO CHANGES THE SUPPORT CONVERSATION Imagine an expert sitting in a central support office. Without Remote Assist, they might receive a service ticket containing several sentences and a photograph. They need to interpret the problem from that limited information. With Remote Assist, the worker's camera becomes a window into the work environment. The technician can show the complete machine. Then the control panel. Then the component producing the problem. The expert can ask the technician to move closer, change the viewing angle, show a label, follow a cable, or inspect another component. The conversation becomes interactive. The expert no longer needs to imagine the physical environment entirely from a written description. USING REMOTE ASSIST ON MOBILE DEVICES Not every remote support scenario requires mixed reality hardware. Supported smartphones and tablets can provide a practical option for many everyday service situations. A field technician can take out a device, contact an expert, show the equipment, receive guidance, and continue working. This makes Remote Assist relevant to organizations that want visual remote support without deploying specialized headsets to every employee. For quick inspections, customer-site troubleshooting, equipment identification, or occasional expert assistance, familiar mobile devices can be sufficient. The important element is not the device. It is the shared visual context. MIXED REALITY AND HANDS-FREE SUPPORT Mixed reality becomes particularly interesting when employees need both hands available. Imagine a technician working inside a machine while holding tools. Repeatedly putting down the tools to pick up a smartphone interrupts the process. With an appropriate mixed reality headset, the worker can continue looking at the equipment while the remote expert sees the worker's perspective. The technician's hands remain available for the task. Guidance can remain connected to the physical work environment. This makes hands-free remote assistance potentially useful for complicated maintenance, manufacturing, inspection, and service processes. MICROSOFT TEAMS AND REMOTE ASSIST Microsoft Teams plays an important role in the Remote Assist experience. Teams provides familiar communication capabilities including calls, meetings, chat, and contacts. Remote Assist uses that communication foundation while focusing the interaction on frontline work. A technician can connect with an expert already working within the organization's Microsoft environment. Another specialist can potentially join when additional expertise becomes necessary. The organization does not necessarily need to build a completely separate communication network specifically for remote support. The people employees already collaborate with through Teams can become part of the support process. REMOTE ASSIST VS A NORMAL TEAMS CALL At first glance, Remote Assist may sound like a Microsoft Teams video call. There is an important difference. A traditional Teams meeting primarily connects people. Remote Assist focuses that connection on the physical work environment. The remote expert is not simply watching another person's face through a webcam. They are looking at the machine, equipment, installation, component, or physical environment the frontline worker is trying to understand. Visual guidance can then help both people focus on the same physical object. That makes the conversation considerably more useful for hands-on technical work. VISUAL ANNOTATIONS One of the most useful concepts behind Remote Assist is visual annotation. Imagine an electrical cabinet containing several rows of nearly identical connectors. The remote expert says: "Check the connector beside the blue cable." There may still be several possible components. Instead, the expert can visually indicate the relevant area. They might circle a connector, place an arrow near a switch, or mark another part of the scene. The technician can then see exactly which area the expert is discussing. A small visual mark can eliminate several minutes of verbal explanation. This becomes particularly valuable when machinery contains many visually similar components Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

    Dynamics 365 Remote Assist - Simply Explained

  8. 1d ago

    Dynamics 365 Unified Routing - Simply Explained

    When a customer sends a chat message, email, phone request, or support case, they usually expect one thing: the right person should help them as quickly as possible. But customer service becomes complicated as organizations grow. A shared inbox that worked perfectly for five agents can quickly turn into a bottleneck when hundreds of requests arrive through multiple channels, in different languages, with different priorities, and requiring different technical skills. In this episode of Microsoft Knowledge Nuggets on M365 FM, Mirko Peters explains Microsoft Dynamics 365 Unified Routing in plain English. We explore how Unified Routing classifies incoming customer requests, determines priority, identifies required skills, considers agent availability and workload, and then routes the work to the most appropriate person. We also explain workstreams, queues, skills, capacity profiles, presence, push assignment, pick assignment, machine learning, fallback queues, and Copilot Service workspace. WHAT IS DYNAMICS 365 UNIFIED ROUTING? Dynamics 365 Unified Routing is an intelligent routing capability designed to automatically distribute incoming customer service work to appropriate agents. Think of it as a smart front desk. Imagine a large office building where visitors arrive with completely different needs. One person needs accounting. Another needs technical support. Another speaks Spanish and needs someone who can communicate with them. Another has an urgent appointment. A good receptionist does not simply point everybody toward the same waiting room. They understand what each visitor needs and direct them toward the right person. Unified Routing performs a similar function for customer service requests. Instead of simply asking "Which agent is next?", the system can consider what the customer needs, who has the necessary skills, who is available, how much work each agent already has, and how urgently the request should be handled.  WHY BASIC CUSTOMER SERVICE QUEUES STOP WORKING Imagine a small customer service department with five employees. Customers send emails to one shared support address. Every email enters the same queue. When an agent finishes their current task, they take the next request. For a small organization with one product, one language, and relatively few requests, this can work perfectly well. Then the organization grows. Customers begin contacting support through email, live chat, voice, messaging, web forms, and case records. Some customers have billing questions. Others need technical assistance. Some require support in another language. Some have routine questions. Others have critical problems affecting their business. Suddenly, the shared queue looks less like an organized support process and more like a pile of papers sitting on somebody's desk. THE PROBLEM WITH FIRST-COME, FIRST-SERVED ROUTING Traditional queues frequently focus on when a request arrived. But arrival time is only one factor. Imagine an experienced technical specialist spending an hour answering basic password questions. Meanwhile, a customer with a serious technical problem waits because nobody noticed that their case requires specialist knowledge. Eventually, another agent opens the case, realizes they cannot solve it, and transfers it. The customer waits again. The organization creates additional work. The specialist eventually receives the request anyway. Unified Routing attempts to reduce these unnecessary handoffs by considering the requirements of the request before assigning it. The goal is to get closer to: Right customer request → right team → right agent → right time. BASIC ROUTING VS UNIFIED ROUTING Basic routing can already provide useful structure. An organization might create a simple rule: Billing cases go to the billing queue. Technical cases go to the support queue. For straightforward customer service environments, that may be sufficient. But a queue answers only part of the routing question. It tells the system where the request should wait. It does not necessarily determine which person inside that queue has the appropriate expertise, who is currently available, who already has several active conversations, or whether another request should receive higher priority. Unified Routing addresses this larger assignment problem. ONE ROUTING APPROACH ACROSS CUSTOMER SERVICE CHANNELS One of the important ideas behind Unified Routing is applying a common routing approach across different types of customer work. A live chat and an email are obviously different interactions. A telephone call has different timing requirements from a case created through a web form. But they share the same fundamental routing problem: Who should handle this request? Unified Routing can evaluate incoming work according to the organization's configured rules and requirements. The channel becomes one part of the decision rather than requiring an entirely disconnected routing philosophy for every customer interaction. SKILLS-BASED ROUTING Skills are one of the most important concepts in Unified Routing. A skill represents something an agent knows how to handle. That might be: A language. A particular product. A technical area. A customer service specialization. A business function. A support level. Incoming work can also receive required skills. Dynamics 365 can then match the requirements of the customer request with the skills associated with available agents.  A SIMPLE SKILLS-BASED ROUTING EXAMPLE Imagine two agents. Maria understands the company's advanced product line and speaks Spanish. David specializes in account questions and currently has capacity for another email. A Spanish-language request about an advanced technical problem should not automatically go to David simply because he happens to be the next available person. The work requires Spanish and advanced product knowledge. Maria is therefore a much stronger match when she is available and has sufficient capacity. This illustrates the fundamental difference between basic distribution and intelligent routing. Availability alone does not necessarily make somebody the right agent. THE TWO DECISIONS BEHIND UNIFIED ROUTING Unified Routing essentially performs two connected operations. First, it determines what the incoming request needs. Then it determines who should receive it. Microsoft's routing process can therefore be understood as: Classification → Assignment Classification adds useful information to the work item. Assignment compares those requirements with available agents. Keeping these two stages separate makes the overall routing process easier to understand. WHAT IS CLASSIFICATION? Imagine an email entering Dynamics 365. Initially, it may contain a customer name, subject line, message, and other basic information. That alone may not tell the routing system enough. Is this a billing problem? A product failure? An account question? Which language does the customer require? Does the customer have premium support? Does the case require specialist knowledge? How urgent is the problem? Classification adds the information required to answer those questions. It turns a relatively vague customer request into structured work that the routing system can understand.  CLASSIFICATION RULES Organizations can configure rules that examine information associated with incoming work. For example, a rule might determine that a customer has a premium support agreement and therefore assign a higher priority. Another rule could inspect the case category and require a billing skill. Another could identify the customer's language and add that language as a routing requirement. The important point is that these decisions become repeatable. Instead of every agent manually deciding how a request should be categorized, the routing configuration applies the organization's service rules consistently. MACHINE LEARNING AND ROUTING Rules work particularly well when customer information is structured and predictable. But customers do not always describe the same problem using the same words. One customer might say: "My device won't start." Another writes: "The screen stays black." Another says: "I can't turn it on." These sentences may describe the same underlying problem. Creating manual rules for every possible variation quickly becomes difficult. The supplied episode explains that machine-learning-based capabilities can help predict the skills required for a request by examining patterns in customer text. Instead of creating a separate rule for every phrase, a model can help determine whether a request appears to require product expertise, billing knowledge, or another support skill.  YOU DO NOT ALWAYS NEED MACHINE LEARNING More intelligence does not automatically mean better routing. A small customer service team with clear case categories may be perfectly successful using straightforward rules. Machine learning becomes more relevant when volumes increase, customer descriptions vary significantly, and maintaining manual routing rules becomes increasingly difficult. The routing architecture should match the complexity of the actual service operation. Organizations should not create an AI problem where a simple business rule already solves the requirement.  PRIORITY IS DIFFERENT FROM SKILLS Skills and priority answer two different questions. Skills ask: Who can solve this? Priority asks: How quickly should we deal with it? A routine request may safely wait behind a serious service disruption. A customer with a premium support agreement may require a faster response. An urgent operational problem may need to move ahead of several normal requests even when those requests arrived earlier. Unified Routing can use classification information to establish priority before an agent receives the work. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

    Dynamics 365 Unified Routing - Simply Explained
See All (943)

Ratings & Reviews

5
out of 5
3 Ratings

About

Welcome to the M365.FM — your essential podcast for everything Microsoft 365, Azure, and beyond. Join us as we explore the latest developments across Power BI, Power Platform, Microsoft Teams, Viva, Fabric, Purview, Security, and the entire Microsoft ecosystem. Each episode delivers expert insights, real-world use cases, best practices, and interviews with industry leaders to help you stay ahead in the fast-moving world of cloud, collaboration, and data innovation. Whether you're an IT professional, business leader, developer, or data enthusiast, the M365.FM brings the knowledge, trends, and strategies you need to thrive in the modern digital workplace. Tune in, level up, and make the most of everything Microsoft has to offer. M365.FM is part of the M365-Show Network. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

Information