[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"branding":3,"analytics":7,"article-new-retrieval-system-tracks-support-tickets-as-they-evolve":10,"sections":35},{"siteName":4,"siteTagline":5,"publisherName":4,"contactEmail":6},"The Revision","Tech news, decoded.","editor@therevision.news",{"gaMeasurementId":8,"adsenseClientId":9},"G-ZW2MV82GYR","ca-pub-8533917693782264",{"article":11},{"id":12,"slug":13,"title":14,"dek":15,"body_md":16,"tags_json":17,"published_at":18,"created_at":19,"updated_at":20,"status":21,"review_note":22,"review_notes":23,"image_url":22,"persona_id":22,"persona_name":22,"section":24,"tags":25,"sources":30,"feedback":34,"feedback_at":22,"cost_usd":34,"total_tokens":34},6826,"new-retrieval-system-tracks-support-tickets-as-they-evolve","New Retrieval System Tracks Support Tickets as They Evolve","RAFT treats support cases as timelines instead of static documents, and early tests show it retrieves relevant past fixes more often than standard RAG.","A new retrieval system for customer support bots treats a ticket's history as a timeline, not a wall of text.\n\nResearchers built RAFT, short for Retrieval-Augmented Framework for Troubleshooting Agents, to fix a blind spot in today's retrieval-augmented generation (RAG) systems: they treat old support cases as static documents, ignoring the fact that a case unfolds in stages. RAFT instead breaks each resolved case into a chain of timeline entries and searches at that entry level, so it can match the specific stage a live ticket is stuck at and pull forward the rest of that historical case's path. An optional graph layer links related cases together for broader context. The team tested the retrieval step on its own, using a synthetic benchmark built from Microsoft Windows Server documentation plus real Apache Jira tickets flagged as duplicates by actual users.\n\nRAFT beat both plain RAG and GraphRAG at every stage of a case's progress, with gains large enough to be statistically significant, and the Jira results hint the same edge shows up outside synthetic data too. That matters because most enterprise support bots quietly fail when a problem does not match a tidy FAQ entry - they need to recognize 'I've seen this exact step before' partway through a multi-stage fix, not just at the start.\n\nIt's a retrieval benchmark, not a deployed support bot, so the real test - whether this holds up against messy, inconsistent internal tickets rather than clean documentation - is still ahead.","[\"retrieval augmented generation\",\"ai agents\",\"customer support ai\",\"research\"]","2026-09-18T04:00:00.000Z","2026-09-18T18:25:22.183Z","2026-09-18T18:25:34.100Z","published",null,[],"ai",[26,27,28,29],"retrieval augmented generation","ai agents","customer support ai","research",[31],{"name":32,"url":33},"arXiv cs.AI","https:\u002F\u002Farxiv.org\u002Fabs\u002F2609.20754",0,{"sections":36},[37,40,44,49,54,58,62,67,71,76,81,86,91,96],{"name":38,"slug":24,"count":39,"latest_published_at":18},"AI",4016,{"name":41,"slug":42,"count":43,"latest_published_at":18},"Security","security",653,{"name":45,"slug":46,"count":47,"latest_published_at":48},"Policy","policy",338,"2026-09-11T04:00:00.000Z",{"name":50,"slug":51,"count":52,"latest_published_at":53},"Deals","deals",179,"2026-06-29T20:02:07.000Z",{"name":55,"slug":56,"count":57,"latest_published_at":18},"Hardware","hardware",155,{"name":59,"slug":60,"count":61,"latest_published_at":18},"Science","science",121,{"name":63,"slug":64,"count":65,"latest_published_at":66},"Consumer Tech","consumer-tech",99,"2026-09-09T17:27:33.000Z",{"name":68,"slug":69,"count":70,"latest_published_at":18},"Dev Tools","dev-tools",77,{"name":72,"slug":73,"count":74,"latest_published_at":75},"Software","software",75,"2026-09-10T20:41:21.000Z",{"name":77,"slug":78,"count":79,"latest_published_at":80},"Startups","startups",55,"2026-09-09T23:14:29.000Z",{"name":82,"slug":83,"count":84,"latest_published_at":85},"Gaming","gaming",43,"2026-09-10T12:18:06.000Z",{"name":87,"slug":88,"count":89,"latest_published_at":90},"General","general",41,"2026-09-08T01:57:23.000Z",{"name":92,"slug":93,"count":94,"latest_published_at":95},"Reviews","reviews",20,"2026-06-24T12:00:01.000Z",{"name":97,"slug":98,"count":99,"latest_published_at":100},"How-To","how-to",6,"2026-06-16T09:00:00.000Z"]