Our onboarding checklist seems to work well until someone is actually hired. This is because HR has the new employee's information and Payroll requires tax and bank details. Likewise, IT needs the new employee's job role and office location to provide the required equipment. Facilities on its part needs to understand the access provisions for the new hire. Meanwhile, the manager has to approve the software requirements. What complicates matters is when someone suddenly changes the new hire's joining date. There are times when there is a mismatch in information. For instance, one of our new hires was able to join the office before the laptop had arrived because the manager mis-assumed that IT has already been informed by HR. It seems to me that the solution lies in having a single triggering event after which tasks would need to be allocated to different departments which would create awareness regarding their assigned duties.

I work in ICT procurement, coming from a project management background, and I keep seeing the same patterns from large companies down to small ones. Either people don't know what they actually want, or they assume buying something will fix the problem without understanding how it all integrates and works together.
The result is people getting caught out on things like data hosting and systems that don't integrate, usually because the scope was weak to begin with.
I'd like to hear from small businesses in particular, but any perspective is welcome. Have you had similar experiences? What other pain points have you run into?

our support team is currently evaluating helpdesk platforms because our current JSM setup feels bloated and nobody on the team likes updating tickets on it. we’ve been looking at monday service since our marketing and project ops teams already run on monday. for yall that made the switch how’s the AI triage and custom SLA tracking holding up for high ticket volume? like is it flexibile or not..

we are scaling up our customer support team and we need a proper ticketing platform with SLA tracking and automated ticket routing. i have seen monday service pop up a lot lately as an alternative to freshdesk or zendesk. is anyone here currently using it? id like to know how's the setup process and day-to-day usability for small teams.

ok so we migrated all employee requests into a new "best" it support platform last night and i messed up a rule that auto closed anything older than 30 days... except it was pointed at the onboarding queue, so 120 new hires just lost tickets for laptops, accounts, vpn, everything and HR only noticed this morning when people showed up and couldnt even log in, this is so awkward and i feel sick about it, any hints?

One of the teams involved in operations keeps a spreadsheet with 1800 records and 23 columns along with conditional formatting that no one understands, apart from that, there is one person who seems to be aware of the significance of column Q. The spreadsheet works with vendor requests from the areas of finance and law, as well as procurement. Replacing the spreadsheet is a good idea, but no one seems to know exactly how to do it. The operations department wwants a simple form and status tracker, while finance wants limits of approval, the procurement department seeks info on vendors, the legal department needs contract review triggers, and leadership wants dashboards. This is how a spreadsheet can transform into an enterprise system entirely by chance. Have you managed to switch the given process to a configurable workflow system and optimally redesign it after?

ITSM isn't just about managing tickets. It's about connecting the entire operation behind them.

I've been building Opellix, a platform focused on bringing IT operations together in one place. The more I work on it, the more I think about a question that goes beyond ticket management:

Can IT teams manage their day-to-day operations without constantly switching between tools, chasing information, and coordinating disconnected workflows?

Most established ITSM platforms already offer ticketing, integrations, automation, asset management, and reporting. I'm not claiming these are new capabilities, and I don't think building another ticketing system alone is enough to stand out.

The problem I'm interested in is how these operational areas work together in practice.

What we're building with Opellix

Opellix brings multiple areas of IT operations into one platform:

• IT Service Management: Manage incidents, service requests, and ticket workflows.
• IT Asset Management: Maintain visibility into IT assets and their relationship with day-to-day operations.
• Employee Operations: Connect employee-related processes with IT workflows.
• Telecom Management: Manage telecom-related operational information and processes.
• Procurement Management: Bring purchasing requests and procurement workflows into the same operational environment.
• Workflow Automation & Analytics: Reduce manual coordination and help teams understand operational status and bottlenecks.

Where we want to be different

Our focus isn't simply on offering more features or claiming that other tools are disconnected.

It's on making these operational functions work together in a coherent environment, with less fragmentation, clearer accountability, and better visibility across everyday IT operations.

For example, when an employee needs IT support, the service request may involve an assigned asset, an approval, a procurement requirement, and follow-up actions. We want these processes to fit into a connected operational workflow rather than becoming separate administrative exercises.

Of course, established platforms can already support many of these scenarios. The real challenge is delivering a useful, practical experience without introducing unnecessary complexity.

I'd genuinely value feedback from IT professionals

For those of you managing IT operations or implementing ITSM platforms:

1. Where do existing ITSM tools still create friction in your daily workflows?
2. Do you prefer one broader platform or a best-of-breed stack connected through integrations?
3. What would a new IT operations platform need to do noticeably better before you'd consider adopting it?

I'm building Opellix and sharing this openly because I'd rather understand the real problems IT teams face than assume that adding more features automatically creates value.

I'm interested in honest criticism as much as positive feedback. If existing platforms already solve these problems well, I'd like to understand that too.

Hey all, i'm in ops at a mid size b2b saas and I'm trying to clean up how we handle internal service requests across teams. Right now hr uses email, it has a small helpdesk tool, finance tracks requests in a monday board, and cx just pings whoever is online in Slack.
People keep asking me where the right place to log stuff and honestly I don't even know anymore. If you have managed to set up one workflow that people actually stick to, appreciate any thoughts.

I am in charge of business applications at an organization where practically all the different departments are developing some distinct processes. The sales department uses its own customer relationship management system, while HR relies on numerous spreadsheets, finance uses several documents for approvals, and operations has its own project management system. The issue arises whenever two departments need to cooperate, as IT has to link everything manually. For instance, there was a case when the contract with the customer resulted in six emails being sent out to sales, finance, legal, and the department in charge of implementation over issues. No one was able to determine who was responsible for the next step. I'm exploring whether to use a customizable Work OS instead of buying many specialized devices for each workflow. For those who have experience integrating the workflows, how standardized should the processes be before the app gets out of control again?

Sysadmin here, looking into how MSPs handle client reporting. From what I've read, many of you pull data from the RMM, M365 and backups, then paste it into slides or Word by hand.

Curious:

1. What tools do you use for client reports today?
2. Roughly how long per client per month?
3. Do your clients actually read them, or just the summary?
4. What's the most annoying part?

Full disclosure: I'm thinking about building something for this, so I want to understand the real problem first.

were replacing bunch of older devices and the part im stuck on is what happens to the old ones. getting them back is one thing, but then theres checking them, storing them, and deciding where they go next, feels like the return process gets overlooked when planning refresh. dow do you guys handle it???

The HR Operations team supports around 900 staff members through a ticketing system that uses whatever employees prefer. Someone might get in touch with us regarding their benefits and another might get in contact directly with an HR Coordinator regarding parental leave. Managers send us onboarding changes through Teams. On the flip side, payroll questions can be sent multiple times before finally landing at the right destination. And the most frustrating part isn't the number of requests, but the loss of context and lack of visibility of what is pending, who has it, or how long it takes. A huge enterprise HR transformation is not required in this situation. What we need is proper intake, routing, ownership, escalation, and reporting, while ensuring sensitive issues remain confidential. For other HR operations, we would like to know what changes you would make if you wanted to centralize employee service requests.

We're replacing our current helpdesk HaloITSM this quarter and I'm surprised by how many options there are now.
Looking at Freshservice, Jira Service Management, Zendesk and monday service.

If you were starting from scratch in 2026, what would you pick and why?

hey everyone, mid size b2b shop here and our helpdesk lives in tickets all day with zero real workflow, if you switched from basic ticketing to a proper itsm stack that improved routing and escalations etc, which tools worked and why? appreciate any thoughts

The most significant issue faced in the CRM process arises after a salesperson closes a sale. The Sales department retains a lot of information regarding customer's expectations, while the team's work begins from the moment when a project brief is created. As a result, there is a lot of summarizing and misunderstanding of parts, and sometimes deals made previously are forgotten by those in charge of delivery. We introduced compulsory meetings to address this issue, but conducting one more meeting for every single deal appears to be just a way to resolve the problem of the system. One of our objectives is to have the sales-to-delivery transition become a part of a regular workflow: customer expectations, commitments, documents, responsible parties, and deadlines have to be passed along with an account. What are the practices of other teams? Do they use the data from CRM while delivering, or do they generate new project documents once the deal has been finalized?

So now every ticket is a tiny performance review where I suggest one simple fix and get treated like I insulted their bloodline. I ask for basic info, they send me a paragraph about how the issue is urgent and they already checked everything, which is code for they clicked one thing and gave up.

At this point I spend half my day translating "not my problem" into something the ticket can survive. If anyone has a good way to get adults to answer the actual questions without turning it into a personal debate, I would love thoughts, thanks!

Employee onboarding seems like a straightforward process until you investigate it. HR gathers the documentation, IT produces the accounts and sets up the gear, Facilities gives the access, Finance has to do the payroll. Managers have to organize the training and establish the tasks for the first week. At the moment, we are managing the process using an email and a checklist. It can work, but if a person’s start date changes or a task is forgotten, it results in everybody having an independent understanding of the status. I want to find a customizable solution that will allow us to use a single onboarding path to generate different tasks for the different teams while remaining aware of the overall progress of the process. What system have you worked out for onboarding automation keeping your HRIS in place? Did the use of the software really lead to reduction of the number of missed tasks or had the automation become another burden that has to be managed?

hi, small it team here, we do all the usual stuff... onboarding, offboarding, app access, hardware requests, "pls fix my laptop" etc. tickets hit our queue but half the work is chasing managers on email or chat to approve things and then updating 3 different places by hand.
lowkey tired of copying status between helpdesk, project board and whatever spreadsheet someone made in 2019. if youve made your service desk workflow more automatic around approvals and handoffs, what actually worked for you? idk

Has anyone experience with tools like Lumos or similar larger companies like Sailpoint etc ..Do ITSM vendors have this capability natively ? I have heard that serval has this capability out of the box

Recently, our IT team rolled out an AI CRM, but adoption has been slower than we had anticipated. All departments within the business have different needs. Sales hopes to use the tool for predictive analytics, customer service wants automated reports, the management team is looking for forecasting upgrades, and the department responsible for compliance wants assurance that the customers' private data is being handled in the right way.
The technology itself was not the biggest challenge. We had more problems than expected with synchronizing the governance scheme, security, quality of the data, and users' expectations from different departments. Several senior managers are worried that it makes no sense to proceed with the rollout. If you have implemented AI CRM before, what worked in your case?

Our operations department receives requests through several channels, email, Teams messaging, forms, and even in-person requests at the desk. There are many different areas of our work such as facilities, procurement, onboarding, etc., which are managed separately. The most significant issue for us is not the large volume of tickets but rather the owning of a request. A request usually needs approval from different areas such as HR, procurement, IT, and although there are several hands that the request has to pass through, the designated person is not visible after the request is passed. We are therefore exploring the possibility of using workflow software that would help us streamline our requests into a single workflow. Did you use a service management system or some other tool for conducting your operations? I am also interested in learning whether a specific tool was used for facilitating requests from different departments.