[{"data":1,"prerenderedAt":425},["ShallowReactive",2],{"blog-post-otai-desk-frontschicht-entscheidungshilfe-en":3},{"id":4,"title":5,"body":6,"date":415,"description":416,"draft":417,"extension":418,"meta":419,"navigation":420,"path":421,"seo":422,"stem":423,"__hash__":424},"blogEn\u002Fblog\u002Fotai-desk-frontschicht-entscheidungshilfe.md","OTAI Desk: Front Layer or Full System? A Decision Guide for IT Leaders",{"type":7,"value":8,"toc":405},"minimark",[9,13,38,41,46,55,71,78,82,85,106,136,140,147,167,185,193,197,217,283,290,294,301,335,342,346,369,372,392,395],[10,11,5],"h1",{"id":12},"otai-desk-front-layer-or-full-system-a-decision-guide-for-it-leaders",[14,15,16,23,24,28,29,33,34],"p",{},[17,18,22],"a",{"href":19,"rel":20},"https:\u002F\u002Fdesk.openticketai.com",[21],"nofollow","OTAI Desk"," is listed in ",[17,25,27],{"href":26},"\u002Fsystems\u002Fotai-desk","Open ITSM Hub"," as an active ticketing system—with structured comparison data and dedicated ",[17,30,32],{"href":31},"\u002Fcompare\u002Fotai-desk-vs-zammad","comparison articles",". But the practical question is rarely “Is OTAI Desk good?”—it is: ",[35,36,37],"strong",{},"Should it replace my helpdesk or relieve the existing system?",[14,39,40],{},"This article explains both deployment models and links the right hub resources for your next evaluation.",[42,43,45],"h2",{"id":44},"two-models-one-product-line","Two Models — One Product Line",[14,47,48,49,54],{},"According to the ",[17,50,53],{"href":51,"rel":52},"https:\u002F\u002Fdesk.openticketai.com\u002Fhow-it-works\u002F",[21],"product architecture",", OTAI Desk supports:",[56,57,58,65],"ol",{},[59,60,61,64],"li",{},[35,62,63],{},"Standalone helpdesk"," — requests via chat, email, or Microsoft Teams; local LLMs classify, RAG searches the knowledge base, routine cases are resolved directly.",[59,66,67,70],{},[35,68,69],{},"Intelligent front layer"," — L1 requests are intercepted; unresolved cases go to Zammad, Znuny, OTOBO, Jira Service Management, or Matrix42 as structured tickets.",[14,72,73,74,77],{},"The second mode is the differentiating approach: ",[35,75,76],{},"no rip-and-replace."," Backend processes, packages, and agent workflows remain intact.",[42,79,81],{"id":80},"when-the-front-layer-fits","When the Front Layer Fits",[14,83,84],{},"The front layer often makes sense when at least three points apply:",[86,87,88,94,100],"ul",{},[59,89,90,93],{},[35,91,92],{},"Existing system runs stably"," — migration would cost more than extension.",[59,95,96,99],{},[35,97,98],{},"L1 volume is high"," — password resets, FAQ, standard routing tie up agents.",[59,101,102,105],{},[35,103,104],{},"Data protection rules out cloud AI"," — local inference and audit trails are mandatory.",[14,107,108,109,113,114,113,118,122,123,113,126,130,131,135],{},"Typical backends in the hub: ",[17,110,112],{"href":111},"\u002Fsystems\u002Fzammad","Zammad",", ",[17,115,117],{"href":116},"\u002Fsystems\u002Fznuny","Znuny",[17,119,121],{"href":120},"\u002Fsystems\u002Fotobo","OTOBO",". Comparisons ",[17,124,125],{"href":31},"OTAI Desk vs. Zammad",[17,127,129],{"href":128},"\u002Fcompare\u002Fotai-desk-vs-znuny","vs. Znuny",", and ",[17,132,134],{"href":133},"\u002Fcompare\u002Fotai-desk-vs-otobo","vs. OTOBO"," show technical differences and selection criteria.",[42,137,139],{"id":138},"when-a-full-system-switch-makes-sense","When a Full System Switch Makes Sense",[14,141,142,143,146],{},"Evaluate OTAI Desk as a ",[35,144,145],{},"replacement"," when teams:",[86,148,149,156,159],{},[59,150,151,152,155],{},"want an ",[35,153,154],{},"AI-first"," helpdesk from scratch, without Perl\u002FRuby OTRS tradition;",[59,157,158],{},"plan Microsoft Teams and chat as primary channels;",[59,160,161,162,166],{},"prefer on-premise deployment with ",[17,163,165],{"href":164},"\u002Fpackages\u002Fopen-ticket-ai-runtime","Open Ticket AI Runtime"," (LGPL-2.1, Docker, CPU without GPU requirement).",[14,168,169,170,172,173,175,176,180,181,184],{},"Against an established ",[17,171,112],{"href":111}," or ",[17,174,117],{"href":116}," operation with .opm\u002F",[177,178,179],"code",{},".szpm"," ecosystem, a ",[35,182,183],{},"feature parity test"," must follow: multi-channel depth, ITIL processes, CMDB, Generic Interface, Elasticsearch operations.",[14,186,187,188,192],{},"Use the ",[17,189,191],{"href":190},"\u002Fcompare","interactive comparison","—OTAI Desk is now selectable there.",[42,194,196],{"id":195},"otai-desk-vs-open-ticket-ai-runtime","OTAI Desk vs. Open Ticket AI Runtime",[14,198,199,200,202,203,207,208,211,212,216],{},"Easy to confuse: ",[35,201,22],{}," is the helpdesk product with UI and channels. The ",[35,204,205],{},[17,206,165],{"href":164}," is middleware for classification and automation ",[35,209,210],{},"inside"," Znuny, OTOBO, or Zammad—via PyPI packages like ",[17,213,215],{"href":214},"\u002Fpackages\u002Fotai-otobo-znuny","otai-otobo-znuny",".",[218,219,220,235],"table",{},[221,222,223],"thead",{},[224,225,226,230,232],"tr",{},[227,228,229],"th",{},"Requirement",[227,231,22],{},[227,233,234],{},"OTAI Runtime alone",[236,237,238,250,261,272],"tbody",{},[224,239,240,244,247],{},[241,242,243],"td",{},"L1 deflection with chat\u002FTeams",[241,245,246],{},"yes",[241,248,249],{},"no (no end-user UI)",[224,251,252,255,258],{},[241,253,254],{},"Keep backend unchanged",[241,256,257],{},"yes (front layer)",[241,259,260],{},"yes (plugin)",[224,262,263,266,269],{},[241,264,265],{},"AI audit dashboard",[241,267,268],{},"per product site",[241,270,271],{},"limited",[224,273,274,277,280],{},[241,275,276],{},"Ticket classification only",[241,278,279],{},"overkill",[241,281,282],{},"sufficient",[14,284,285,286,216],{},"More context: ",[17,287,289],{"href":288},"\u002Fblog\u002Fopensource-helpdesk-ki-apis-automation-datenschutz","AI in open-source helpdesks",[42,291,293],{"id":292},"proof-of-concept-checklist","Proof of Concept Checklist",[14,295,296,297,300],{},"Before deciding, we recommend the same matrix for front layer ",[35,298,299],{},"and"," full system:",[56,302,303,310,316,322,328],{},[59,304,305,306,309],{},"Run ",[35,307,308],{},"10–20 real L1 requests"," (password, FAQ, routing).",[59,311,312,315],{},[35,313,314],{},"Escalation case"," to backend—verify ticket fields, context, status sync.",[59,317,318,321],{},[35,319,320],{},"Audit log"," completeness for compliance.",[59,323,324,327],{},[35,325,326],{},"Measure initial response latency"," (product site cites under 30 seconds as a target—project-dependent).",[59,329,330,331,334],{},"Document ",[35,332,333],{},"operational effort"," Docker stack vs. existing infrastructure.",[14,336,337,338,341],{},"Results belong in your internal shortlist—the hub provides structured ",[17,339,340],{"href":190},"comparison data",", not the final decision.",[42,343,345],{"id":344},"classification-in-open-itsm-hub","Classification in Open ITSM Hub",[14,347,348,349,113,351,113,353,130,355,359,360,364,365,216],{},"OTAI Desk complements the directory alongside ",[17,350,112],{"href":111},[17,352,117],{"href":116},[17,354,121],{"href":120},[17,356,358],{"href":357},"\u002Fsystems\u002Fkix","KIX",". Vendor ",[17,361,363],{"href":362},"\u002Forganizations\u002Fsoftoft","Softoft"," also maintains OTAI plugins in the ",[17,366,368],{"href":367},"\u002Fpackages","package directory",[14,370,371],{},"Further reading:",[86,373,374,380,386],{},[59,375,376],{},[17,377,379],{"href":378},"\u002Fblog\u002Fotai-desk-ki-first-helpdesk","OTAI Desk: AI-First Helpdesk — Introduction",[59,381,382],{},[17,383,385],{"href":384},"\u002Fopen-source-ticketsysteme","Open-source ticketing systems guide",[59,387,388],{},[17,389,391],{"href":19,"rel":390},[21],"OTAI Desk at desk.openticketai.com",[393,394],"hr",{},[14,396,397],{},[398,399,400,401,216],"em",{},"Neutral classification within Open ITSM Hub. Binding product and pricing information: ",[17,402,404],{"href":19,"rel":403},[21],"desk.openticketai.com",{"title":406,"searchDepth":407,"depth":407,"links":408},"",2,[409,410,411,412,413,414],{"id":44,"depth":407,"text":45},{"id":80,"depth":407,"text":81},{"id":138,"depth":407,"text":139},{"id":195,"depth":407,"text":196},{"id":292,"depth":407,"text":293},{"id":344,"depth":407,"text":345},"2026-09-17","When OTAI Desk makes sense in front of Zammad, Znuny, or OTOBO — and when a classic helpdesk switch remains the better option. With comparison links and checklist.",false,"md",{},true,"\u002Fblog\u002Fotai-desk-frontschicht-entscheidungshilfe",{"title":5,"description":416},"blog\u002Fotai-desk-frontschicht-entscheidungshilfe","k0M080TUPRPAaVKJERU35qDWL1d2cCn3otIH97WUjNs",1789746274429]