What would stop you from trying rallied (https://rallied.ai) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

Carlos Shieldsneutral

The biggest hurdle for me would be ensuring it integrates smoothly with our current ConnectWise PSA and the shared spreadsheets we use for L1 tracking. We've spent a lot of time refining those processes, and any new tool needs to slot in without causing major disruption or requiring a whole new system. I also need to see concrete proof that it can handle the specific nuances of law firm and dental practice tickets. Right now, we're managing ticket volume by meticulously documenting everything, which is time-consuming but effective. I'd be willing to pay around $150 per month, given the included credits.

Simulated interest: 60/100

Jackie Wiegandneutral

What would stop me from trying Rallied this month? Frankly, the biggest hurdle is the lack of granular control and auditability you mentioned in relation to the MSP. My current focus is on secure credential resets and multi-cloud integration nuances. While your AI sounds promising for automating L1/L2 tasks, I need to see concrete proof it can handle our specific security protocols without manual intervention. I’m currently managing these flows through a combination of custom scripts and careful Freshservice automation, which, while not ideal, gives me the precise control needed for compliance. We're also concerned about integrating with our specific stack; ensuring it truly works seamlessly with our systems, not just the common ones, is paramount. I'd need to see pilot data or a robust security overview that addresses our fintech's specific regulatory needs before considering a trial. As for payment, the pricing model of $150 a month with 2,000 credits, where a typical month covers about 700 tickets, translates to roughly $0.075 per ticket for the core work. Given my focus on ROI, and the potential for this to reduce my team's workload, I could consider up to $300 per month, provided it demonstrably reduces headcount hours or enhances stability without compromising security or auditability.

Simulated interest: 40/100

Joey Bornscheuernegative

My primary concern is that this "AI technician" sounds like another tool that will require significant overhead to manage and integrate. I currently handle password resets and onboarding with Python scripts that I've built and documented myself, giving me complete control. The idea of an "AI agent" resolving tickets autonomously makes me uneasy; I need absolute transparency and verifiable processes, especially concerning user access and data privacy, which aligns with my current focus on hardening Okta controls. While the promise of automation is appealing, the "your automation tool shouldn't need its own engineer" tagline makes me skeptical. I'd need to see proof that this tool doesn't introduce its own complex maintenance burden and that its decision-making is entirely auditable and configurable to my exact security standards. If it could demonstrably reduce the burden on my team without sacrificing that control, perhaps. But given my current setup, I'm not willing to pay for it.

Simulated interest: 10/100

Devangana Mehraneutral

What would stop me from trying Rallied? It's the integration with our current workflow, specifically how it would handle the L1 tickets that still come through WhatsApp, email, and manual notes. We currently manage this by having my team manually triage and assign those, which is inefficient but familiar. I need to be sure Rallied can genuinely absorb that chaos without creating more work for us in setup or ongoing management. Given our focus on frugality, I would be willing to pay up to $100 per month to test this, but only if it demonstrably streamlines our current L1 process without significant additional overhead.

Simulated interest: 50/100

Omar van Loonneutral

The biggest hurdle for me would be integrating a new AI tool into our existing workflow without causing disruption. We handle a lot of repetitive L1 tickets – password resets, basic access requests – which I currently manage by assigning them to my team and tracking trends in HaloPSA. I also maintain our SharePoint knowledge base, which helps frontline staff resolve common issues themselves. My concern is that this AI might not fully grasp the nuances of our specific environment or the unique ways our users report problems. The idea of it "resolving L1 tickets autonomously" sounds promising, but I'd need to see concrete evidence that it handles edge cases and complex queries accurately before I'd consider it. I'm also wary of a tool that requires significant setup or ongoing maintenance, as my time is already stretched thin. I am willing to pay a maximum of $150 per month, assuming the credit system covers a typical month's worth of tickets for us.

Simulated interest: 50/100

Andrée Leclercneutral

The primary concern stopping me from trying Rallied this month is the potential for AI 'hallucinations' that could cause client issues, which I then have to explain. Currently, I meticulously audit our ticket categories and refine our existing virtual agent's logic. I'd need to see a pilot in 'Plan Mode' and understand the exact approval workflows. Regarding pricing, I'd be willing to pay up to $200 per month, billed monthly, provided it demonstrably reduces our manual triage time by at least 10%.

Simulated interest: 60/100

Hubert Schroeder-Denesikneutral

Right now, I handle L1 tasks myself using a combination of self-written scripts and the native admin consoles. The sheer variety of environments means I need granular control, and I'm hesitant to introduce a third-party system that might add complexity or recurring costs I can't easily recoup across my six SMB clients. While the idea of an AI technician is appealing for efficiency, I'd need to be absolutely sure it could handle the unique configurations and security requirements of each client without introducing new problems. If it could demonstrably reduce the time I spend on routine escalations without compromising security or control, I might consider it. My maximum acceptable price would be $150 per month, billed monthly, as that aligns with the advertised pricing structure.

Simulated interest: 40/100

Ramón Sotelo Blanconeutral

My main concern about trying Rallied this month is how well it integrates with our current ManageEngine ServiceDesk Plus. We have a lot of basic password resets and printer issues that come in, and my team spends too much time on them. Today, my team handles these by rotating triage, and I try to keep our internal knowledge base updated, though adoption is slow. If Rallied can truly automate these L1 tasks without requiring extensive setup or an additional person to manage it, it would be valuable. I'd be willing to pay up to $300 per month, provided it significantly reduces our ticket volume and frees up my team for more complex issues.

Simulated interest: 70/100

Clark Cummerataneutral

The primary concern for me would be the integration with our on-premise ERP system. The description mentions integration with M365 and an RMM, but not legacy on-prem systems. We handle L1 tickets by following documented procedures and assigning them to my junior technician. I'd need to see clear evidence that Rallied can reliably interact with our specific ERP without introducing new risks or requiring extensive customisation. I also need to understand how it handles edge cases that aren't in the documentation. Given the unknowns, I wouldn't pay for it this month. If it proved capable of handling our ERP and demonstrating consistent resolution for our ticket types, I might consider paying up to $150 per month, provided the credit system is clear and sufficient for our volume.

Simulated interest: 30/100

Amaranaath Namboothirineutral

What stops me from trying Rallied this month is the lack of clear, verifiable data on its performance with complex, real-world integrations, especially legacy systems. Currently, my team handles L1 requests by meticulously refining our ServiceNow Virtual Agent scripts and through direct agent intervention, which is time-consuming but predictable. I would need to see pilot results or case studies demonstrating successful autonomous resolution of a significant percentage of our specific ticket types, particularly those generated by vague user inputs that often create duplicate tickets. The pricing model, $150 per month with 2,000 credits, is also a bit abstract. A typical month covers about 700 tickets, which sounds reasonable, but without knowing how many credits our average ticket would consume, it's hard to assess the true cost. I would be willing to pay up to $100 per month, provided it proves a demonstrable reduction in our ticket backlog and agent workload.

Simulated interest: 40/100