[{"data":1,"prerenderedAt":265},["ShallowReactive",2],{"blog-post-en-cityos-40000-reports-case":3,"blog-siblings-en-cityos-40000-reports-case":98},{"id":4,"title":5,"author":6,"body":7,"category":80,"cover":81,"date":82,"description":83,"draft":84,"extension":85,"meta":86,"navigation":87,"path":88,"readingTime":89,"seo":90,"stem":91,"tags":92,"__hash__":97},"blog_en\u002Fen\u002Fblog\u002Fcityos-40000-reports-case.md","CityOS in a district of 180,000: 6 months, 40,000 tickets","Codifya",{"type":8,"value":9,"toc":71},"minimark",[10,14,19,22,25,29,32,35,39,42,49,55,61,65,68],[11,12,13],"p",{},"In January 2026, a district in Antalya deployed CityOS. By June, over 40,000 reports had been received and resolved. Beyond the numbers, the most valuable lessons from this period:",[15,16,18],"h2",{"id":17},"process-first-software-second","Process first, software second",[11,20,21],{},"The mayor's first question in the initial meeting wasn't about software features: \"How do we not reduce the permanent staff count?\" This was the right question. If they'd adopted CityOS just to \"collect reports faster,\" it would have been the same as the old system.",[11,23,24],{},"The solution: instead of an agent chasing reports, build a team that meets reports in the field. 12 street representatives in the city center, each responsible for 4 neighborhoods. Every morning their mobile app shows daily routes.",[15,26,28],{"id":27},"finding-category-matters-more-than-volume","Finding: category matters more than volume",[11,30,31],{},"In the first two months, the top report type was \"pothole.\" An analysis revealed that 600 of 1,000 potholes were in the same heatmap — an area with heavy winter rainfall and old infrastructure.",[11,33,34],{},"When CityOS's reporting view started showing the mayor \"the source of the problem,\" it transformed from a routine request handler into a decision-support tool.",[15,36,38],{"id":37},"three-slowdown-points","Three slowdown points",[11,40,41],{},"As with any system, three points caused delays:",[11,43,44,48],{},[45,46,47],"strong",{},"1. Vehicle assignment:"," Directing a report to the field is the most critical step. Average wait time was 4 hours. A rotation algorithm was developed to bring this down to 90 minutes.",[11,50,51,54],{},[45,52,53],{},"2. Citizen feedback:"," There was no \"what happened\" response to the citizen who filed the report. A closed-loop notification was added: \"Your request was received → team dispatched → resolved.\"",[11,56,57,60],{},[45,58,59],{},"3. Neighborhood headmen (muhtars):"," The headmen were outside the system. After giving them read access, they started checking before complaints even arrived.",[15,62,64],{"id":63},"outcome","Outcome",[11,66,67],{},"Of 40,000 reports in 6 months, 94% were resolved within 14 days. The municipality's own data shows this was 61% in the old system. The difference wasn't in the technology; it was in how the team receiving reports was designed.",[11,69,70],{},"CityOS became a tool that helped the municipality rethink its own internal processes. The software didn't solve the problem — it made the problem visible.",{"title":72,"searchDepth":73,"depth":73,"links":74},"",3,[75,77,78,79],{"id":17,"depth":76,"text":18},2,{"id":27,"depth":76,"text":28},{"id":37,"depth":76,"text":38},{"id":63,"depth":76,"text":64},"CityOS",null,"2026-04-20","How a district municipality managed 40,000 citizen reports in 6 months with CityOS. The design decisions that determined success — not the technology.",false,"md",{},true,"\u002Fen\u002Fblog\u002Fcityos-40000-reports-case",7,{"title":5,"description":83},"en\u002Fblog\u002Fcityos-40000-reports-case",[93,94,95,96],"case study","municipality","citizen engagement","operations","Nd-D3hXbvFQLP_puK3e6rgBun6y2UllB94Ph5wgmAaI",{"prev":99,"next":182},{"id":100,"title":101,"author":6,"body":102,"category":80,"cover":81,"date":171,"description":172,"draft":84,"extension":85,"meta":173,"navigation":87,"path":174,"readingTime":89,"seo":175,"stem":176,"tags":177,"__hash__":181},"blog_en\u002Fen\u002Fblog\u002Fcityos-vatandas-bildirim-sistemi.md","Designing a citizen reporting system from scratch",{"type":8,"value":103,"toc":164},[104,107,110,114,117,121,124,132,136,139,146,150,153,157],[11,105,106],{},"Citizen reporting is one of the most visible service metrics for a municipality — and usually one of the weakest operationally. Call center, social media, mobile app: each channel tends to live in its own silo.",[11,108,109],{},"When designing CityOS's reporting module, we set out to solve three core problems.",[15,111,113],{"id":112},"_1-a-unified-queue","1. A unified queue",[11,115,116],{},"Which channel a citizen used — phone, mobile app, web — should be a detail the assignee doesn't have to think about. CityOS pipes every channel into one queue; the assigned report looks the same regardless of source.",[15,118,120],{"id":119},"_2-auto-classification-but-overridable","2. Auto-classification, but overridable",[11,122,123],{},"Whether a report is \"park maintenance\" or \"road maintenance\" is obvious in roughly 80% of cases. The remaining 20% needs a human.",[11,125,126,127,131],{},"CityOS auto-classifies the incoming report, but the assignee can always change the category. That small detail — ",[128,129,130],"em",{},"\"AI suggested it, but you have the final say\""," — dramatically increases acceptance.",[15,133,135],{"id":134},"_3-live-updates-for-the-citizen","3. Live updates for the citizen",[11,137,138],{},"When the internal process completes, push notifications are the fastest way to tell the citizen. But which step should we notify? Assigned, in-progress, completed?",[11,140,141,142,145],{},"Three pilot municipalities tested it and the result was clear: a single notification — ",[128,143,144],{},"\"Your report is complete\""," — produced higher satisfaction than multiple updates. Notifying every step felt like nagging.",[15,147,149],{"id":148},"the-invisible-part-gdprkvkk","The invisible part: GDPR\u002FKVKK",[11,151,152],{},"Separating identity from report content, enabling audit log from day one, and minimizing personal data — all standard. This is the most expensive layer to add later.",[15,154,156],{"id":155},"takeaway","Takeaway",[11,158,159,160,163],{},"A reporting system requires far more decisions than it appears to. CityOS's module is a concrete application of the ",[128,161,162],{},"less clicking, more clarity"," principle.",{"title":72,"searchDepth":73,"depth":73,"links":165},[166,167,168,169,170],{"id":112,"depth":76,"text":113},{"id":119,"depth":76,"text":120},{"id":134,"depth":76,"text":135},{"id":148,"depth":76,"text":149},{"id":155,"depth":76,"text":156},"2026-04-22","What questions did we ask while designing CityOS's reporting module? Three points where municipal workflows tend to break, and the answers we built.",{},"\u002Fen\u002Fblog\u002Fcityos-vatandas-bildirim-sistemi",{"title":101,"description":172},"en\u002Fblog\u002Fcityos-vatandas-bildirim-sistemi",[178,179,180],"public sector","product design","workflow","NPgZezqxZi8KgQ0XrRLvamU8IRsYrBEWgcwiJc-PNbg",{"id":183,"title":184,"author":6,"body":185,"category":254,"cover":81,"date":255,"description":256,"draft":84,"extension":85,"meta":257,"navigation":87,"path":258,"readingTime":259,"seo":260,"stem":261,"tags":262,"__hash__":264},"blog_en\u002Fen\u002Fblog\u002Fqr-menu-kafe-vakasi.md","A café's switch to QR menu: 90 days later",{"type":8,"value":186,"toc":248},[187,190,212,215,219,222,226,229,233,240,243,245],[11,188,189],{},"In March, a single-location café in Konya switched to QR Menu. Ninety days in, here's what they shared:",[191,192,193,200,206],"ul",{},[194,195,196,199],"li",{},[45,197,198],{},"90% drop"," in printed-menu cost (only the table cards get reprinted)",[194,201,202,205],{},[45,203,204],{},"60% fewer"," order errors from international customers (thanks to auto-translation)",[194,207,208,211],{},[45,209,210],{},"8 minutes saved per day"," on menu updates",[11,213,214],{},"More interesting than the numbers were the behavior shifts.",[15,216,218],{"id":217},"how-long-do-customers-stay-on-the-menu","How long do customers stay on the menu?",[11,220,221],{},"Average viewing time went from one minute to 2.5. We initially read this as a bad signal — longer might mean more indecision. According to surveys, the opposite was true: customers were now reviewing photos, checking allergen labels, and reading content details.",[15,223,225],{"id":224},"the-waiters-role-changed","The waiter's role changed",[11,227,228],{},"The pressure on the waiter to answer \"what do you recommend?\" eased, because the customer had already seen detailed info on the menu. That freed the waiter to focus on table atmosphere and service.",[15,230,232],{"id":231},"the-unexpectedly-popular-feature","The unexpectedly popular feature",[11,234,235,236,239],{},"The owner did not predict that ",[45,237,238],{},"stock-based auto-hiding"," would matter most. Sold-out items quietly disappear from the menu — the customer orders, the waiter never has to apologize.",[11,241,242],{},"That single detail meaningfully improved customer satisfaction.",[15,244,156],{"id":155},[11,246,247],{},"Switching to QR menu isn't just a paper-to-digital migration. Done right, it's an infrastructure that reduces operational load and errors while quietly improving the customer experience.",{"title":72,"searchDepth":73,"depth":73,"links":249},[250,251,252,253],{"id":217,"depth":76,"text":218},{"id":224,"depth":76,"text":225},{"id":231,"depth":76,"text":232},{"id":155,"depth":76,"text":156},"QR Menü","2026-03-30","What changed for a single-location café after switching to QR Menu? A short case study on operations, customer behavior, and error rate.",{},"\u002Fen\u002Fblog\u002Fqr-menu-kafe-vakasi",5,{"title":184,"description":256},"en\u002Fblog\u002Fqr-menu-kafe-vakasi",[93,263,96],"restaurant","6ZxiVmPuaiJF0I3FvOYwjKItZUX8Lo9I6id0kwBEQlY",1781523775294]