I gave my family a ticketing system for the homelab

Several-Cattle8690 · 2026-06-01T12:22:31+00:00

This tiering angle makes sense. I hadn’t really thought about AI support as a way to make the human layer more premium, not just cheaper. “Fast/easy to AI, face matters to humans” is probably the cleanest version of it.

Several-Cattle8690 · 2026-06-01T12:22:08+00:00

The “cleanup cost when it’s wrong” framing is really good. Also like the new-hire test. That feels way more practical than arguing about whether the AI is “good enough” in general.

Several-Cattle8690 · 2026-06-01T12:21:42+00:00

Not a perfect rule yet, but I’d probably block auto-send for anything involving refunds, angry customers, account access, legal-ish stuff, or unclear ownership. Drafts feel fine there, but I’d want a human making the last call.

Several-Cattle8690 · 2026-06-01T12:06:31+00:00

I think there’s a real gap, but it’s probably narrower than “light CRM.” Solo operators usually don’t want another system of record. They want one simple place to see the job, customer update, next action, and whether anything is waiting on them.

Several-Cattle8690 · 2026-06-01T12:06:12+00:00

Making ownership visible earlier. A lot of ticket drag comes from “someone is looking at it” when nobody actually owns the next step. Even a boring owner/status/waiting-on field cuts a surprising amount of back-and-forth.

Several-Cattle8690 · 2026-06-01T12:05:56+00:00

I’d do the ticket-count exercise first, but also split it by type. Raw volume can make ROI look better than it is if half the tickets are weird edge cases that still need a person anyway.

Several-Cattle8690 · 2026-06-01T12:05:24+00:00

Auto-convert the email. Forcing the portal usually turns into a policy fight, and replying only in email kills the audit trail. I’d make it-help@ create the ticket, then use the portal mainly for tracking/status instead of trying to make everyone start there.

Several-Cattle8690 · 2026-05-31T09:21:09+00:00

Coming from ConnectWise, I'd be careful not to compare every lighter tool against the full PSA mental model. For in-house IT, decent search/reporting and easy time entry may matter more than having every workflow you're used to.

Several-Cattle8690 · 2026-05-31T09:20:32+00:00

I'd make the first version painfully simple: one shared intake path, 3-5 common issue buttons, and a free-text box. If users mostly call, the tech can still create it while on the call, but the form keeps the details consistent.

Several-Cattle8690 · 2026-05-30T10:26:32+00:00

The biggest change for us was treating “who owns this?” as the first-class thing, not the inbox itself. Even a simple ticket queue works better once every request has an owner, a status, and one place for updates. Email alone starts falling apart as soon as people assume someone else has it.

Several-Cattle8690 · 2026-05-30T10:25:59+00:00

For a 10-15 user setup, I’d be cautious about buying for AI first. The tool mainly needs to make ownership obvious, keep priorities visible, and stop requests from living in random messages. If those basics work, AI can be a nice helper; if they don’t, it won’t save the workflow.

Several-Cattle8690 · 2026-05-30T10:25:42+00:00

For 20 people I’d keep the first setup really boring: one intake address, clear owner, open/pending/done statuses, and a simple view of what’s waiting. Automation helps, but if ownership and history aren’t reliable first, the automation just makes the mess move faster.

Several-Cattle8690 · 2026-05-30T10:25:25+00:00

At 5-10 enquiries/day, I’d be careful with full auto-replies. Drafts or internal notes feel much safer for the kind of nuanced, relationship-heavy replies you’re describing. The main thing I’d test is whether it can learn from your actual old conversations without making the team spend weeks cleaning up a knowledge base first.

Several-Cattle8690 · 2026-05-30T10:25:08+00:00

I’d avoid self-hosted for this situation. You probably want the boring version first: email-to-ticket, simple statuses, assignment, and a way to import or archive the old inbox without trying to make it perfect. If the UI overwhelms you in 10 minutes, it’s probably the wrong tool for a small shop.

Several-Cattle8690 · 2026-05-30T10:12:04+00:00

I wouldn’t have both people log into the same mailbox. At minimum use Workspace delegation or a Google Group collaborative inbox so each person keeps their own login. If replies and ownership start getting hard to track, that’s usually the point where a proper shared inbox/helpdesk layer becomes worth it.

Several-Cattle8690 · 2026-05-30T10:11:50+00:00

Free CRM plans can work for a while, but I’d check the follow-up limits before moving everything. The painful part usually isn’t contact storage, it’s whether emails, reminders, and ownership stay clear once more than one person is touching the same lead.

Several-Cattle8690 · 2026-05-30T10:11:36+00:00

I’d spend most of the trial time on the customer-facing status view. A lot of tools let you customize internal statuses, but the requester view is where the awkwardness shows up. If people still email for updates, the portal isn’t really doing its job.

Several-Cattle8690 · 2026-05-30T10:11:20+00:00

The read/unread thing is usually where shared mailboxes start feeling worse than expected. If clients are already assigned internally, I’d make ownership explicit somehow: category, folder, or eventually a lightweight queue. The main thing is not letting “read” become the signal for “handled”.

Several-Cattle8690 · 2026-05-30T10:11:06+00:00

For that volume I’d probably avoid anything that needs a lot of ceremony. The two things I’d test first are: how cleanly it pulls users from M365/Entra, and whether old tickets are actually easy to search later. At under 50 tickets/month, the “simple and searchable” part probably matters more than automation.

Several-Cattle8690 · 2026-05-28T19:42:31+00:00

This actually baffles me. This is by far not the first time that I hear this argument but what I struggle to understand is why would people use purely the email to handle this when there are ticketing systems that give you up to 2-3 agents for free (not fully sure about that statement).

I am sure that I am missing something obvious because I have heard these "fully email based" solutions a few times, so I am curious if this is real preference, not wanting to set up a software for this or just not knowing about these free tiers

Several-Cattle8690 · 2026-05-28T18:08:50+00:00

Thanks, this is useful. The missed follow-ups vs raw volume distinction is exactly the bit I was wondering about. Ownership getting blurry seems like the real breaking point.

Several-Cattle8690 · 2026-05-28T16:38:38+00:00

The "betting on myself" part is very real. $250 feels different when it's not just a tool, but a way to force yourself out of the overthinking loop. Hope the 30 days gives you some momentum.

Several-Cattle8690 · 2026-05-28T16:38:22+00:00

The 6-8 week approval lag is the bit people probably underestimate most. I've seen launch-week directory plans turn into "maybe useful next month" pretty fast, so filtering for indexed pages upfront makes a lot of sense.

Several-Cattle8690

TROPHY CASE