Company · Customer Care Team
Support that stays with the system.
The Customer Care Team is the coordinating interface after the order and throughout operation. It connects delivery, commissioning, training, technical support and lifecycle topics with the specialists behind the comemso system.
One interface across the lifecycle
Keep responsibility connected after delivery.
The Customer Care Team stays involved throughout the system lifecycle, clarifies requests, retains the project context and coordinates the right technical or organisational route. The objective is not to pass a case on. It is to make the next step explicit.
Project handover and delivery
Monitor delivery schedules, keep the handover structured and connect the ordered configuration with the people responsible for commissioning and operation.
Commissioning coordination
Coordinate the practical start-up route for the supplied system and make interfaces, responsibilities and prerequisites visible before the session begins.
Training and enablement
Connect users with product training, application knowledge and the material required to operate the configured functions with confidence.
Technical support
Route questions about products, applications, observed behaviour, software or firmware to the correct specialist while retaining the system context.
Lifecycle service
Coordinate calibration, maintenance, repair and update topics with the relevant service and metrology teams.
Customer feedback
Bring experience, recurring questions and criticism back into service and product improvement instead of treating feedback as an isolated ticket.
How the team works
Listen. Clarify. Coordinate. Close the loop.
A useful answer starts with the actual system, configuration and engineering objective. Customer Care preserves that context while the responsible specialists work on the case.
Clarify the system, configuration, application, expected behaviour and business impact.
Separate product operation, application engineering, software, metrology and commercial topics.
Connect the case with the people who can resolve it without losing the original context.
State what is needed, who acts next and which evidence closes the question.
Prepare the support request
Send the context that makes the issue reproducible.
A concise technical brief reduces clarification loops and helps the team route the case correctly from the start.
- Product, system configuration and serial number
- Software, firmware and test-library versions
- Device under test, interface and charging or BMS standard
- Expected behaviour compared with the observed behaviour
- Steps required to reproduce the issue
- Logs, reports, screenshots, traces or project files
- Operational impact and required timing
Feedback makes the system stronger
Customer experience returns to engineering.
Questions, suggestions and criticism expose recurring friction, missing explanation and new application requirements. The Customer Care interface helps convert that experience into service and product improvement.
Direct lifecycle routes
Use the route that matches the responsibility.
Customer Care coordinates the lifecycle. The following pages contain the deeper evidence, documents and specialist access for the individual topic.
Existing systems, faults, operation and technical assistance.
Open support contactAccreditation, calibration scope and traceability context.
Review calibration evidenceUse the support route to clarify the update path for the configured system.
Open update routeBrochures, guides, checklists, webinars and technical material.
Open resourcesExisting system or new requirement?
Use Support for continuity. Use Sales for the next configuration.
Frequently asked questions
Customer Care and technical support.
When should I contact the Customer Care Team?
Use Customer Care for after-sales coordination, delivery and commissioning topics, training, questions about an existing system and help finding the correct lifecycle route.
What belongs with Sales instead of Support?
New systems, expansions, upgrades, demonstrations, quotations and commercial project scope belong with Sales. Technical issues and operation questions for an existing system belong with Support.
Which information should a technical request contain?
Include the product and serial number, system configuration, software and firmware versions, expected and observed behaviour, reproduction steps and any relevant logs, reports or screenshots.
Can Customer Care coordinate commissioning and training?
Yes. The published Customer Care responsibilities include commissioning coordination and the organisation of training and education.
Continue from technical context
Turn the information into the next engineering decision.
Continue to the relevant application, current product scope or responsible comemso team.