Behind the scenes: How the Flexopus support team works
Who is actually behind the quick help with Flexopus? In this article, we'll introduce you to our support team. Learn how we overcome technical hurdles, why personal contact is more important to us than anonymous tickets, and how we incorporate feedback directly into software development. Real support from real people for your best desk sharing experience possible!
Table of contents
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posere.
Who uses Flexopus, notices quickly: Behind the software is not only a powerful product, but also a support team that really helps. But how does this team actually work? Who are the people behind it, how do they handle complex cases and what makes Flexopus support special?
We spoke with Nils, Alischa, Pascal and Vanessa and give an honest look behind the scenes.
The team behind support
The Flexopus support team consists of people with different areas of expertise but a common goal: to help customers sustainably. Here are some of the people behind Flexopus Support:
Nils
Nils handles all types of support cases, accompanies onboardings, trains new customers and checks bugs and feature requests.
Alischa
Alischa is a lead in first-level support, help desk manager and project manager for major customers. She coordinates feature requests, works closely with development and creates changelogs.
Pascal
Pascal takes care of customer support, onboardings, bug analyses and tests new features.
Vanessa
As a Customer Success Manager, Vanessa accompanies customers throughout the entire life cycle — from onboarding to feedback meetings.
What connects them all: Proximity to the product, direct customer contact and genuine responsibility.
Support without standard phrases
A clear difference from many other providers:
Flexopus does not provide standard automated answers.
Each case is examined individually. Support often goes beyond the actual question, including best practices that help customers in the long term.
“Our goal isn't to close tickets quickly, but to really solve problems.” - Vanessa
A typical support day? It doesn't exist.
The day usually starts with a team sync in the morning:
Exchange on open or complex cases
Coordination with development, sales or marketing
Prioritize incoming tickets
After that, the spectrum ranges from:
Classic support requests
Onboardings & customer appointments
Bug analysis & feature testing
Help center maintenance
No day is the same and that is exactly what many people in the team appreciate.
“We do much more advice than trouble shooting — this is primarily due to the stable and intuitive product” - Alischa
What are the most common inquiries?
Support is most commonly reached by:
Floor plan preparations
Site expansions
Identity provider connections
Individual use cases where existing functions can be cleverly combined
Large customer projects that require cross-team collaboration are particularly exciting (and challenging).
Close cooperation with Development & Co.
Support with Flexopus doesn't end at the ticket border:
Feature requests flow directly into product planning
Bugs are analyzed together with development
Marketing and sales are regularly informed about new developments
The result: short distances, quick decisions and visible improvements.
Behind the scenes: things that surprise
A few insights that many customers wouldn't expect:
Floor plans are prepared by hand by graphic artists, even sketches or hand drawings are no problem
Support has a real impact on feature prioritization
Many adjustments are implemented directly without detours from support
Bug fixes and minor improvements are often implemented within a few hours, larger features within a few weeks or months, depending on the scope
Support as a team effort
What motivates the team every day?
Really moving customers forward
Positive feedback
Exciting new use cases
The strong cohesion in the team
In stressful phases, no one is left alone. Tasks are distributed, priorities are set together and successes are celebrated.
“No one has to work alone for us. We're always there for each other.” — Alisha
Key values in the support team:
Cooperation
Openness
Trust
Dependability
Humour
“Customer support is serious — but positive customer feedback is the biggest motivation for me.” — Nils
Tips from Support: How to get to the solution faster
So that inquiries can be resolved as efficiently as possible, the team recommends:
How does Flexopus support differ from traditional call centers?
With Flexopus, you'll meet an in-house team of experts instead of anonymous call center employees. Support is deeply interlinked with development, which means that inquiries are not only answered superficially, but are also solved in a technically sound manner. The focus is on speed, humanity and genuine expertise directly from the software manufacturer.
How does customer feedback from support influence the development of the app?
Feedback is not a dust collector for us. The support team acts as a direct interface between users and product design. Common customer requests or specific challenges in everyday work are regularly evaluated and incorporated directly into the roadmap for new features and updates. In this way, Flexopus stays close to the practice and needs of administrators.
What resources does Flexopus offer in addition to personal support?
In addition to direct contact, Flexopus uses “self-service enablement.” An extensive knowledge base with step-by-step instructions, video tutorials and best practices enables administrators to find solutions independently and quickly. The goal is a perfect combination of quick self-help and competent personal advice on complex issues.