Maven AGI Agent Platform

What do you like best about the product?

We started using Maven AGI as response times were fabulous for us. What we didn't realize was that ticket volume wasn't our biggest issue.Our knowledge lived everywhere. Some information was in the help center, some in internal documents, and some only existed in the heads of experienced employees. Human agents had learned to work around these inconsistencies, so we barely noticed them.When we implemented Maven, those gaps became impossible to ignore. It increased our efficiency and our support team was fast and on point.

What do you dislike about the product?

If your internal processes are messy, Maven will expose that quickly. For us, fixing those issues ended up creating long-term value far beyond AI automation.

What problems is the product solving and how is that benefiting you?

As we improved our documentation, both AI and human agents began delivering more consistent support. An unexpected benefit was that Maven improved more than just automation—it strengthened our entire support operation. Implementation did require coordination across support, operations, and knowledge owners, but that alignment helped us get the most out of it.

What do you like best about the product?

Before Maven AGI, our support team spent most of the day dealing with repeat contacts. Customers would start with a chatbot, get a partial answer, then end up in an email queue, and finally reach an agent. We weren't really reducing work—we were just moving it around.
What changed with Maven is that the AI can actually complete the entire request. After connecting it to our knowledge base and support systems, it starts the magic. This began handling multi-step issues without any human intervention.

What do you dislike about the product?

I think the one and only challenge lies in a successful automation system. Without proper knowledge and thoughtful testing it won’t run. So investing time here to know Maven properly is a must to do work.

What problems is the product solving and how is that benefiting you?

Customer context follows the conversation across channels. So the experience remains consistent whether someone starts in chat or follows up later. One situation that stood out involved subscription changes and billing questions. Previously those conversations would bounce between multiple agents. Now the agent can retrieve the right information, take action when appropriate, and resolve many cases without escalation.

What do you like best about the product?

My perception has completely changed after meeting Maven AGI. I was skeptical about AI voice solutions because most of my previous experiences felt like talking to an advanced phone menu. Customers would repeat themselves multiple times before eventually asking for a human.A customer changed the topic halfway through the conversation. Instead of restarting the flow or getting confused, the agent adapted naturally, pulled the relevant information, and continued helping the customer. That moment convinced me that voice AI was finally becoming practical.

What do you dislike about the product?

Voice automation still requires careful planning. We were conservative with permissions at first and gradually expanded what the agent could do. Taking that approach helped us build confidence while maintaining control over customer interactions.

What problems is the product solving and how is that benefiting you?

The system handles everything in an organised and hassle-free way. This can do order updates, and support requests while maintaining context throughout the conversation. When escalation is needed, human agents receive the transcript and relevant context immediately. Furthermore, it eliminates the need for customers to repeat themselves.The biggest impact has been on customer experience and agent productivity.

What do you like best about the product?

I was skeptical about AI voice support before using Maven. Most voice automation I've experienced feels like an upgraded phone menu. You say something, it misunderstands you, and eventually you just keep asking for a human.
Our experience with Maven Voice was very different. One of the first things we tested was a customer changing their request halfway through a conversation. The agent adjusted naturally, pulled the relevant information, and continued without restarting the whole process. That small moment was what convinced me the technology was actually becoming useful for real customer service.
We later started looking at more practical workflows such as account questions, order issues, status updates, and cases that needed escalation.

What do you dislike about the product?

Voice workflows need careful testing and help to enhance work efficiency rather than just provide information. We were more conservative with permissions at the beginning and gradually expanded what the agent was allowed to do.

What problems is the product solving and how is that benefiting you?

The biggest benefit has been giving time back to the team. Instead of spending most of the day answering variations of the same questions, our agents can focus on escalations, customer relationships, retention issues, and situations that require real problem-solving. For us, that has been more valuable than simply reducing ticket volume.

What do you like best about the product?

After trying several sources I love this Maven AGI for its efficiency. It helps not to feel disconnected from the actual customer conversation. This can easily understand the context and works thereby. Recently, a customer contacted us about a subscription issue and that had already been discussed through chat and email. Normally, an agent would need to spend several minutes reviewing previous conversations before responding. Automatic compiling and presenting relevant customer context in a single place is Maven's main concern. It helps agents spend less time gathering context and more time actually helping customers.

What do you dislike about the product?

Small edits or unusual situations can make pressure. Therefore I like to see more customization options for specialized workflows. Overall the experience has been very positive.

What problems is the product solving and how is that benefiting you?

Before Maven, agents spent a surprising amount of time switching between systems, searching ticket histories, and looking through knowledge articles just to understand a customer's situation. Maven brings that information together and generates responses that are much more relevant to the conversation. As a result, our response times have improved, agents are more productive, and customers don't have to repeat the same information across multiple interactions. The support experience feels more connected and consistent.

What do you like best about the product?

Sometimes a customer has a long history with multiple interactions, and figuring out the full story can take several minutes. Maven usually gives me a useful summary almost instantly. I also like that it suggests responses without sounding overly robotic. I rarely copy and paste the suggestion exactly, but having a solid draft saves a surprising amount of time throughout the day. There have been plenty of situations where it surfaced information that I probably would have missed if I were manually searching through articles and notes.

What do you dislike about the product?

It's not perfect. Every now and then I'll tweak the suggested response or add extra details before sending it. But that's expected with any AI tool, and the suggestions are generally good enough to work from.

What problems is the product solving and how is that benefiting you?

It comes with the most efficient feature that can handle a high volume of support requests. The copilot helps us move through tickets more confidently and consistently. Resolution times have improved, onboarding new agents has become easier. The overall workload feels much more manageable than before.

What do you like best about the product?

We originally started looking at Maven because we wanted something that could work across chat and email without having to maintain separate bots. After digging into the platform, that ended up being the part I liked most.What surprised me was how much context carries across channels. If a customer starts in chat and later reaches out through another channel, the experience feels much more connected than what we were used to before.All of our existing processes can go easily without redesign.

What do you dislike about the product?

Automation is definitely saving the most time here . We can see the impact also but having that broken down in more detail would be useful.

What problems is the product solving and how is that benefiting you?

It wasn't unusual for customers to repeat information or for agents to jump between systems to find answers.Maven helped bring more consistency to that process. The biggest benefit for us hasn't actually been reducing tickets. It's that customers get more consistent answers regardless of where they reach out, and our team spends less time searching for information.

What do you like best about the product?

Security and operational control were major factors for us. Maven combines AI automation with access controls, configurable guardrails, audit logs, sensitive-data handling, and support for major enterprise compliance requirements. We also appreciate that the same governance model can apply across internal and customer-facing channels. It is convenient for us as it saves time rather than creating different rules for every deployment.

What do you dislike about the product?

Because the platform can connect deeply with business systems and perform real actions, implementation should involve support, IT, security, and operations rather than being treated as a simple chatbot installation. That coordination can require additional planning in larger organizations.

What problems is the product solving and how is that benefiting you?

Maven allows us to expand automation into workflows that previously required manual handling because of security, context, or system-access requirements. The result is faster resolution, more predictable support quality, and better oversight of what the AI is doing across different customer channels.

What do you like best about the product?

The biggest difference is that it goes beyond FAQ automation. It can use customer context, company knowledge, and existing workflows together. From an operations perspective, having one intelligence layer across different channels also makes things much easier to manage.

What do you dislike about the product?

You quickly discover that AI automation exposes weaknesses in your own documentation. We found outdated information and inconsistencies that humans had simply learned to work around. We had to clean some of that up before we were comfortable increasing automation. In hindsight, that was actually useful, but it did create some additional work during setup.

What problems is the product solving and how is that benefiting you?

It works fantastic in the absence of a human team and provides the possible best support. Routine calls can be resolved automatically. Of course, this gives more time to our agents to pay attention to customers and all.

What do you like best about the product?

We originally brought Maven AGI into the conversation because our response times were getting harder to manage. But during implementation, we discovered that ticket volume wasn't actually our only problem.
Our support knowledge was scattered across different places. Some answers lived in the help center, others were buried in internal documents, and experienced agents sometimes knew things that weren't documented anywhere. Humans had learned how to navigate that mess over time, so we didn't realize how much friction it was creating.
Connecting Maven forced us to look at our support operation differently. As we organized the knowledge and connected the systems Maven needed, we started creating a much more reliable source of truth for both customers and employees.That ended up being one of the unexpected benefits.
I like that Maven isn't limited to customer-facing automation. The same intelligence can support customers through chat or email while also helping internal teams through tools such as Slack and other existing workflows.

What do you dislike about the product?

Maven will expose messy processes pretty quickly. If documentation is outdated, ownership is unclear, or two departments have different rules for the same situation, those issues need to be resolved.
So there was more internal coordination involved than we initially expected. In our case, though, fixing those gaps ultimately improved the whole support operation.

What problems is the product solving and how is that benefiting you?

The obvious benefit is reducing repetitive customer support work, but the bigger impact for us has been consistency. Customers get faster answers, agents spend less time searching for information, and internal teams have a clearer understanding of the policies being used. Maven gave us automation, but it also pushed us toward a much cleaner and more scalable way of running customer support.