Email Ticketing Software

One of the main challenges with ServiceNow ITSM is its complexity. While the interface is generally user-friendly, some features and configuration options can be difficult for new users to navigate without proper training. The platform offers extensive integration capabilities, but setting up and managing integrations can sometimes be time-consuming. Performance is usually reliable, although heavily customized implementations may require ongoing optimization. Cost is another consideration, as licensing and implementation expenses can be significant. The documentation and support resources are useful, but certain advanced use cases still require experienced administrators. The AI and automation capabilities help reduce manual effort, but there are occasions where recommendations need additional fine-tuning to deliver the best results. Overall, these are manageable challenges, but they are worth considering before implementation. Review collected by and hosted on G2.com.

One of the biggest problems ServiceNow ITSM solves for us is bringing all IT support activities into a single place. It gives better visibility into incidents, requests, and ongoing work, which makes it much easier to understand priorities and track progress. The dashboards and workflows help keep teams aligned, and users can quickly see the status of their requests without needing constant follow-ups. The platform integrates well with other systems we use, which reduces manual work and helps information flow more smoothly across teams. We've also seen benefits from the automation and AI capabilities, particularly in ticket routing and handling routine tasks. This has helped improve response times and overall service quality. While onboarding and configuration required some effort initially, the platform has paid off through improved efficiency, better collaboration, and more consistent service delivery. Overall, it has helped our team work more effectively and provide faster, more reliable support to end users. Review collected by and hosted on G2.com.

What I find challenging about Salesforce Service Cloud is its complexity during setup and customization, particularly for beginners. Certain advanced features require extra training to use effectively, while licensing and implementation can be expensive. The platform can also feel overwhelming to navigate at times, and managing integrations or resolving technical issues requires specialized expertise. Review collected by and hosted on G2.com.

It addresses challenges like handling customer inquiries from different channels, reducing manual case tracking, and improving response times. It brings customer information together in one place, automates routine tasks, and offers real-time insights into support operations. As a result, it helps increase team efficiency, resolve cases faster, streamline workflows, and provide a more consistent customer experience. Review collected by and hosted on G2.com.

Overall, there isn’t much to dislike. The only minor issue we’ve run into is the Turkish localization, where a few translations are missing or a bit imprecise. That said, it’s not critical and hasn’t affected our day-to-day use of the platform or our efficiency. Review collected by and hosted on G2.com.

Zoho Desk streamlines and automates support communication for our boutique MSP, covering interactions with both clients and infrastructure providers. The ability to message vendors directly within the app, then link those conversations as child tickets to the main customer issue, has significantly simplified our workflow and keeps all the technical context organized in one place. Review collected by and hosted on G2.com.

Keeping triggers and automations consistent across both brands took more care than I expected, built a rule for one brand once and completely forgot to mirror it over to the other, which caused a small inconsistency in how tickets got auto tagged for a few weeks before I caught it. Review collected by and hosted on G2.com.

Customers genuinely can't tell they're being supported by the same team behind two different storefronts, which was exactly the point. Agents working from one unified queue instead of switching tools has also kept training simple, new hires only learn one system regardless of which brand's tickets they end up handling. Automation consistency across brands needs real attention though, it's easy to build something for one and just forget the other exists. Review collected by and hosted on G2.com.

Some issues require site visits which have nothing to do with RMM. Review collected by and hosted on G2.com.

A lab PC is three months behind on Windows updates and failing a compliance check. Patching pushes the missing updates after hours, confirms they installed, and clears the flag without a campus visit. A front-desk machine is frozen mid-enrollment. Remote control puts you on the session in about a minute, you kill the stuck process, and the adviser stays on the phone with the applicant. Disk space on a shared workstation hits the alert threshold before the user notices. You clear the cache and the temp files from the console. The ticket never gets written. A laptop drops off the network overnight. The agent shows it last checked in, whether it is online now, and which switch port it was on. You know if it is asleep, unplugged, or actually down before anyone drives over. Review collected by and hosted on G2.com.

A few things frustrate me. Customer support replies often read like AI wrote them. They’re generic and sometimes miss the actual question, so getting a real answer can take several back and forths. I also see duplicate emails come through, which is confusing and makes it hard to tell whether a message is new or one I’ve already handled. Shared inboxes can feel unclear too. It isn’t always obvious who can see what, or whether a teammate is already working on a thread, so I worry about overlap or something private being visible to the wrong person. Finally, it’s expensive, especially once you add users and need the Productive plan to get the features that matter. The pricing adds up fast for a small team. Review collected by and hosted on G2.com.

I run operations across several businesses, including sponsorship partnerships for a creator brand, property management, real estate, and a travel advisory practice. Before Missive, those conversations lived in separate inboxes. Things slipped through the cracks, and finding the full history of a deal or a tenant issue took too long. Missive puts every account in one place, so I can see an entire conversation, comment internally with my team, and hand off threads without forwarding emails around. Pairing it with Claude has been the biggest win. I can pull up the context of a negotiation and get a draft reply ready in minutes instead of digging through old threads. The result is faster response times with partners and tenants, fewer dropped balls, and a lot less time spent managing email. Review collected by and hosted on G2.com.

The AI features are still something we're learning how to use effectively, so more guidance around different use cases would be helpful Review collected by and hosted on G2.com.

We're spending less time looking through tickets just to understand what needs attention. Agents also don't have to write every response from scratch, which is helpful when ticket volumes are high. Review collected by and hosted on G2.com.

Freshdesk should improve the Analytics section so it’s more accurate and easier to create reports for clients. In the current flow, it feels overly complex when trying to build and generate the data. Review collected by and hosted on G2.com.

We have multiple products, and the volume of user queries is very high. When a product is at its peak and query traffic increases significantly, automation and the stability of every support feature play a critical role. This helps us improve the overall user experience and provide faster, more instant solutions to users. In this context, Freshdesk provides a stable and reliable support platform that helps us manage high query volumes efficiently while improving the overall user experience. Review collected by and hosted on G2.com.

Notion sync isn’t real time. New pages take a while to be searchable by the agent. If we ship a fresh runbook in the morning the AI doesn’t know about it until later that day. Review collected by and hosted on G2.com.

it helped me to deploy AI for my entire company and reduce the volume of request my team used to receive Review collected by and hosted on G2.com.

I think, at times, visualizing files in Monday Service can be improved. Right now, files are kinda dumped into one bucket, and there's not a way to really organize them within the file structure. It'd be better if I could move files around and see them more clearly. Review collected by and hosted on G2.com.

monday service is critical for project management, allowing collaboration to reach goals and complete projects. It automates processes that would otherwise take hours, organizes and systematizes communication and project intake, and enhances collaboration and sharing of ideas. Review collected by and hosted on G2.com.

One thing I dislike about HubSpot Service Hub is that some of the more advanced features, like custom reporting or advanced automation, are locked behind higher-tier plans. This can limit small or growing teams from fully leveraging the platform’s potential without increasing costs. Additionally, while the system is user-friendly, there’s still a learning curve when setting up complex workflows or integrations. Review collected by and hosted on G2.com.

HubSpot Service Hub helps solve key customer service challenges like disorganized communication, slow response times, and lack of visibility into customer issues. By centralizing all support interactions through tools like the shared inbox, ticketing system, and knowledge base, it ensures that no customer query is missed and that teams can collaborate efficiently. The automation features reduce manual workload, allowing us to focus on delivering better service. Overall, it improves customer satisfaction while making our support processes more efficient and scalable. Review collected by and hosted on G2.com.

Some reports in the inventory area, especially those related to software, can still evolve. Expanding these analyses would provide a more complete set of information, facilitating the centralization of tools and improving IT asset control. Review collected by and hosted on G2.com.

Milvus has been fundamental for the continuous evolution of my support. Through dashboards, reports, and detailed monitoring of the services, I can identify patterns, map recurring failures, and act more strategically on the root cause of problems. This allows us to move from a merely reactive stance and work on neutralizing recurring incidents, increasing team efficiency, improving SLAs, and enhancing the quality of service provided to users. Review collected by and hosted on G2.com.

I don’t really have any major complaints. The main thing I’ve noticed is that the overall experience depends a lot on how the organization has configured the service portal. Some request forms ask for a lot of information, even for simple issues, so submitting a ticket can sometimes take longer than I’d expect.

Other than that, the platform itself has been reliable and straightforward to use. Review collected by and hosted on G2.com.

It gives me a structured way to raise IT requests instead of sending emails or messaging different people. Whether it’s a software installation, an access request, a hardware issue, or any other internal support need, everything is captured and tracked through a single ticket.

The biggest advantage is being able to see where my request stands at any time, without having to chase updates. Because all communication stays within the ticket, it’s also easy to look back at earlier messages and refer to previous conversations when needed.

Overall, it saves me time, keeps requests organized, and makes working with the IT team much smoother. Review collected by and hosted on G2.com.

The web interface doesn't always chime when a chat comes in if the tab is not in focus and when you finally do switch to that tab, you get blown up with all the chimes from the chats. I recommended a solution for them to fix. Review collected by and hosted on G2.com.

I really support my customers and am always there for them. This support system makes it super easy. Notifications are instant so I can get in touch with my customer within seconds. Review collected by and hosted on G2.com.

Since CommBox is such a comprehensive and powerful platform with so many features, the initial learning curve can be a bit steep. It takes some time to fully explore every capability and automation available, but once you get the hang of it, the results are definitely worth the effort Review collected by and hosted on G2.com.

Before CommBox, our main challenge was the limitation of our operating hours. We were losing potential leads and leaving customer inquiries unanswered during the night or weekends. As a growing business, we couldn't afford to have a 24/7 live team, but we also couldn't afford to miss those opportunities in a competitive market.

CommBox solved this by providing a robust automated system that handles interactions 24/7. We now capture every single lead, even when our team is offline, ensuring no opportunity slips through the cracks. It has allowed us to scale our operations and improve our Customer Experience. It has honestly made our business more efficient and our brand much stronger. Review collected by and hosted on G2.com.

The mobile app could be improved, and we'd like to see more advanced dashboard and reporting visualization options. Review collected by and hosted on G2.com.

We were looking for a solution that could be customized to fit our internal processes while offering more personalized support Review collected by and hosted on G2.com.

It's cloud-only, there's no downloadable or on-premise version, so if that's something your IT team needs you're out of luck. Also no dark mode yet, which some of our agents on the night shift keep asking about Review collected by and hosted on G2.com.

We're a 12-person support team and before this our shared inbox was a mess, no real structure to it. Now tickets get tagged and assigned automatically, and the AI suggestions have saved a good chunk off our first-response time. Basically it lets us grow the team without things falling apart. Review collected by and hosted on G2.com.

Some of the more advanced features do take time to get comfortable with. There’s a lot in the platform, and even after using it for about a year, we’re still turning on parts of it that we hadn’t used much before. Review collected by and hosted on G2.com.

With the previous tool we had, keeping track of equipment and software involved a lot of checking around. Alloy gives IT and the departments a common view of what we already have, which has cut down on duplicate purchase requests and made ownership easier to track. Review collected by and hosted on G2.com.

As Market Research & Consumer Insights Lead for our Austin CPG brand, Freshservice works well for logging IT and marketing support tickets, but it has notable gaps in custom profile field flexibility, native survey-platform integration, and targeted audit filtering that create extra manual work when managing consumer respondent data requests. These limitations slow our research workflows and add overhead when preparing CCPA evidence for our consumer feedback programs.

The biggest pain point is there is no native connector for Doopoll, our primary consumer polling and concept-testing platform. Every time I submit a ticket requesting Zapier workflow changes, new poll audience segmentation, or fixes to our CRM data exports, I have to manually copy poll IDs, respondent volume estimates, and PII retention rules into the ticket body. Last quarter, we ran a product concept test survey with over 1,800 consumer responses. I created three separate Freshservice tickets for pipeline setup, consent validation, and BI export configuration, and I had to manually paste in all survey metadata for each request. Without a direct integration, updates to poll status or respondent counts do not auto-refresh inside Freshservice tickets. On one occasion, our IT team worked off an older respondent volume estimate, which delayed our data pipeline launch by two business days. We also cannot auto-link ticket activity back to specific poll campaigns, so tracing the full lifecycle of a consumer data access request requires manual cross-referencing across Freshservice and Doopoll.

The second major limitation is restricted custom profile field functionality for our research team access controls. The profile edit screen shown in the screenshot only includes basic built-in fields like territory, time zone and contact details. We cannot add dedicated custom profile tags to mark which team members are authorized to view consumer PII. When onboarding new research analysts, I need to manually document their PII access permissions outside Freshservice in a separate spreadsheet. During our last CCPA review, auditors asked to see a list of users with permission to view survey respondent data. I had to combine Freshservice user exports with our offline permission log, which added 9 hours of manual reconciliation work. The platform also does not support fine-grained ticket-level permissions; read-only stakeholders cannot view ticket attachments containing PII handling documentation without being granted broader agent access.

Audit log filtering is also rigid. While Freshservice captures basic ticket activity, I cannot quickly filter logs to show only tickets related to consumer survey data access requests. The log exports are broad, so I must manually sift through hundreds of unrelated IT tickets to extract the subset of records required for CCPA audits. There is also no built-in automated archiving rule for research-related tickets, so I have to manually close and archive old survey-request tickets to meet our CCPA data retention timeline.

Suggestions for improvement: Build native Doopoll integration so poll metadata auto-populates into Freshservice tickets. Add custom profile dropdown fields to tag users with PII access classification. Enable filtered audit log exports, so I can isolate consumer data request tickets for auditors. Add webhooks to push ticket status updates to our BI platform, plus configurable ticket retention policies to auto-archive closed research tickets after our compliance window ends.

Freshservice is reliable for standard internal service requests and ticket tracking. Even so, it is not built for specialized market research teams managing consumer PII under CCPA. Without survey tool integrations and granular user tagging, it forces extra manual reconciliation and creates risk of incomplete audit documentation for our consumer insights work. Review collected by and hosted on G2.com.

As Market Research & Consumer Insights Lead for our Austin CPG brand, I oversee product concept testing and post-purchase feedback campaigns using Doopoll, and I regularly submit requests to IT, marketing and data teams to build survey pipelines and BI exports. Before rolling out Freshservice, our team faced major chaos for internal support requests. We struggled with scattered email threads for data access and integration requests, no centralized audit trail for consumer PII access approvals, and no single place to track when IT work for our survey projects was completed, but now we can log all research-related requests as tickets and tie them to team member profile records, which has resulted in roughly 3 hours saved weekly chasing request statuses and a 40% reduction in hours spent compiling CCPA audit evidence for consumer feedback programs.

Before Freshservice, every request for Zapier workflow tweaks, CRM data syncs or BI dashboard access was sent via email. I would send an email to IT to set up a new Doopoll poll export, and responses would get buried in long email chains. When team members rotated or left the company, critical approval context would disappear. Last year, we ran a large packaging concept test with over 2,000 participants, and we lost track of an email request to adjust PII retention rules. This created a gap in our compliance records, and we spent nearly 10 hours reconstructing the request history during our CCPA review. There was also no consistent way to route requests to the right team; tickets would land with the wrong department, causing unnecessary delays for our product research timelines. We had no unified place to store supporting documents like survey consent forms, poll mockups or data handling guidelines, so important attachments would get separated from the original request.

Freshservice solves these pain points with its ticket portal and user profile configuration panel shown in the screenshot. When I need IT to build a new data pipeline for a consumer poll, I create a ticket, attach all supporting research documentation, and assign it to the correct internal team. I can update team member profiles with territory, time zone and contact details, helping route tickets properly and keep our stakeholder directory organized. The “My Tickets” view lets me quickly check the status of every active request, so I don’t have to send repetitive follow-up emails to IT or data analysts. Every ticket keeps a permanent timestamped log of conversations, approvals and file attachments. When auditors request proof that we followed CCPA rules for consumer respondent data access, I can pull these ticket histories directly to demonstrate our approval workflow. We can also give stakeholders limited portal access to view ticket progress, so product and marketing leaders can check the status of research requests without reaching out to me directly.

Suggestions for improvement: Add native Doopoll integration so poll metadata auto-populates into newly created tickets. Add custom profile fields to tag users by their PII access permission level. Build filtered audit exports that isolate only market research and consumer data tickets. Add webhooks to send ticket status updates to our BI platform, plus configurable auto-archive rules for closed tickets after our CCPA retention window.

Freshservice will never replace Doopoll for running consumer polls and concept testing, or our BI tool for analyzing survey responses. Even so, it has become our single source of truth for all market research support requests. The ticket system eliminates messy email threads, preserves full request history, and creates auditable documentation for consumer data access approvals. This lets my insights team spend less time tracking down support request updates and more time turning consumer feedback into actionable product and marketing recommendations. Review collected by and hosted on G2.com.

Approval rules and escalation paths took us several attempts to get right. The capability is definitely there, but figuring out which setting produced which behaviour required a lot of testing on our side. Once we aligned the configuration with how we actually work, the team picked it up quickly and used it without much trouble. Review collected by and hosted on G2.com.

It’s taken the guesswork out of IT support. Every request follows the same clear path from being logged to being closed, so nothing depends on who happened to notice it. I’m no longer spending my day asking people for updates, and most of the manual chasing has disappeared. Review collected by and hosted on G2.com.