<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Logistics Support Ticket Overview in Data Stories Gallery</title>
    <link>https://community.fabric.microsoft.com/t5/Data-Stories-Gallery/Logistics-Support-Ticket-Overview/m-p/4784600#M14786</link>
    <description>&lt;P&gt;Hi Bro , great dashboard with clear &amp;amp; good insights pls share me the PBIX file&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 04 Aug 2025 21:25:51 GMT</pubDate>
    <dc:creator>amks</dc:creator>
    <dc:date>2025-08-04T21:25:51Z</dc:date>
    <item>
      <title>Logistics Support Ticket Overview</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Stories-Gallery/Logistics-Support-Ticket-Overview/m-p/4760266#M14672</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Logistics Support Ticket Overview&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;This dashboard was built for the customer-support team of a worldwide third-party logistics provider, using ticket data from 2021 to 2024.&lt;/P&gt;&lt;HR /&gt;&lt;P&gt;1. Project purpose&lt;/P&gt;&lt;P&gt;Logistics providers live and die by how fast—and how well—they solve customer issues. The goal of this report is to give &lt;STRONG&gt;ops leaders and CS managers a one-page pulse&lt;/STRONG&gt; on the four service channels (Calls, Chats, Emails, Escalations):&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Work-load&lt;/STRONG&gt; – ticket volumes &amp;amp; YoY change&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Speed&lt;/STRONG&gt; – average resolution time and SLA compliance&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Quality&lt;/STRONG&gt; – customer-rated satisfaction&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Root cause&lt;/STRONG&gt; – top categories driving contacts&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;&lt;P&gt;2. Data &amp;amp; modelling&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;Item Detail &lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;STRONG&gt;Source&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;73 402 anonymised tickets (CSV, 2021-01-01 → 2024-12-31)&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;STRONG&gt;Fields&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;Dates opened/resolved, Channel, Category, Priority, Region, Shipment type, SLA days, Resolution days, CSAT&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;STRONG&gt;Model&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;&lt;EM&gt;FactTickets&lt;/EM&gt; (one row per ticket) + &lt;EM&gt;DimDate&lt;/EM&gt; + slim lookup tables (Channel, Category, Region…) → star schema&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;STRONG&gt;Measures&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;Explicit DAX with VAR pattern (e.g. &lt;STRONG&gt;Tickets YoY %&lt;/STRONG&gt;, &lt;STRONG&gt;Avg Resolution&lt;/STRONG&gt;, &lt;STRONG&gt;SLA Met&lt;/STRONG&gt;). DIVIDE used for safe ratios.&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;HR /&gt;&lt;P&gt;3. Page design choices &lt;EM&gt;(see screenshot)&lt;/EM&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;Design element Rationale &lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;STRONG&gt;Column-per-channel layout (4 cards)&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;Instant side-by-side comparison; uniform reading path&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;STRONG&gt;KPI card + YoY badge&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;At-a-glance headline plus directional cue (green ▲ / red ▼)&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;STRONG&gt;Quarterly mini-bars&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;Quick seasonality check without leaving the page&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;STRONG&gt;Resolution-time histogram&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;Reveals skew &amp;amp; long-tail outliers better than a single average&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;STRONG&gt;SLA annotation&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;Inline reminder of contractual target per channel&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;STRONG&gt;Top-5 category bars&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;Zero-ink alternative to tables; drives conversation on root causes&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;STRONG&gt;Custom theme &amp;amp; icons&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;Consistent brand colours (teal, amber, olive, cyan) and intuitive glyphs&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;STRONG&gt;Year slicer (top-right)&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;Lets users time-travel while keeping the canvas uncluttered&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;HR /&gt;&lt;P&gt;4. Key insights (demo data)&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Calls&lt;/STRONG&gt; remain the busiest (5 417 in 2023) but volume slipped -2 % YoY, hinting at channel-shift to chat.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Chats&lt;/STRONG&gt; grew +1 % and show the &lt;STRONG&gt;fastest average resolution (3 days)&lt;/STRONG&gt; thanks to simpler issues like &lt;EM&gt;Live Tracking&lt;/EM&gt;.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Emails&lt;/STRONG&gt; hover around 5 400 tickets; resolution time skews wider (long tail up to 18 days).&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Escalations&lt;/STRONG&gt; are &amp;lt;15 % of load, yet &lt;STRONG&gt;SLA compliance lags (only 79 %)&lt;/STRONG&gt;—risk area for the COO.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;&lt;P&gt;6. How to use the report&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Pick a &lt;STRONG&gt;year&lt;/STRONG&gt; in the slicer (defaults to current).&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Scan the &lt;STRONG&gt;YoY badges&lt;/STRONG&gt; to spot channels needing attention.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Hover over a &lt;STRONG&gt;bar chart&lt;/STRONG&gt;&amp;nbsp;for exact ticket count &amp;amp; % within SLA.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Click any &lt;STRONG&gt;category bar&lt;/STRONG&gt; to cross-filter the entire page (e.g., isolate &lt;EM&gt;Damaged Goods&lt;/EM&gt; issues).&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Export to &lt;STRONG&gt;PowerPoint&lt;/STRONG&gt; for exec meetings or subscribe to a &lt;STRONG&gt;Power BI alert&lt;/STRONG&gt; on SLA &amp;lt; 85 %.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;STRONG&gt;Why this matters&lt;/STRONG&gt;: In logistics, every delayed resolution compounds downstream costs. This dashboard distils four years of ticket data into a 30-second situational briefing—so leaders can move from gut feel to data-driven decisions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;A big thank you to&lt;/SPAN&gt; &lt;SPAN&gt;&lt;A class="" href="https://www.linkedin.com/in/ACoAABFOYTkBTYnzmBVfTkIrmSceOsxi0s7s5zI" target="_self"&gt;Injae Park&lt;/A&gt;&amp;nbsp;for his guidance on this project.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="reportid hidden"&gt;eyJrIjoiZDExZTM1N2YtNGZhYS00ZTM4LWE1ZWItZmY4ODkwZDZiNGUzIiwidCI6IjQ5MzkwMzQ4LTk2ZGMtNDZhZC05YTYyLWMxMDQzMDIwZmQ2MyJ9&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jul 2025 15:38:49 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Stories-Gallery/Logistics-Support-Ticket-Overview/m-p/4760266#M14672</guid>
      <dc:creator>Ali_India</dc:creator>
      <dc:date>2025-07-11T15:38:49Z</dc:date>
    </item>
    <item>
      <title>Re: Logistics Support Ticket Overview</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Stories-Gallery/Logistics-Support-Ticket-Overview/m-p/4784600#M14786</link>
      <description>&lt;P&gt;Hi Bro , great dashboard with clear &amp;amp; good insights pls share me the PBIX file&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Aug 2025 21:25:51 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Stories-Gallery/Logistics-Support-Ticket-Overview/m-p/4784600#M14786</guid>
      <dc:creator>amks</dc:creator>
      <dc:date>2025-08-04T21:25:51Z</dc:date>
    </item>
    <item>
      <title>Re: Logistics Support Ticket Overview</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Stories-Gallery/Logistics-Support-Ticket-Overview/m-p/4803982#M14900</link>
      <description>&lt;P&gt;I like the clean look. If you can share the PBIX, I would like to check it out more. Thanks for sharing your project.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Aug 2025 16:15:53 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Stories-Gallery/Logistics-Support-Ticket-Overview/m-p/4803982#M14900</guid>
      <dc:creator>CyberCub</dc:creator>
      <dc:date>2025-08-21T16:15:53Z</dc:date>
    </item>
    <item>
      <title>Re: Logistics Support Ticket Overview</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Stories-Gallery/Logistics-Support-Ticket-Overview/m-p/4811222#M14937</link>
      <description>&lt;P&gt;Hello, good morning. I'm from Brazil, and I'm one more person who joins the chorus in saying that your work was very good. I don't know if you shared the pbix with the guys, but if you could, I'd be extremely grateful. Thank you.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Aug 2025 07:33:29 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Stories-Gallery/Logistics-Support-Ticket-Overview/m-p/4811222#M14937</guid>
      <dc:creator>Thais_Cabral</dc:creator>
      <dc:date>2025-08-29T07:33:29Z</dc:date>
    </item>
  </channel>
</rss>

