Centralised cases
Requests, tasks, responsibilities and history are kept traceable in one place.
Managed Zammad
infrahost operates Zammad for IT providers that want to organise support professionally — without having to manage installation, updates, backup and platform monitoring themselves.
Service management
Email inboxes and personal notes only scale so far. Zammad creates traceable cases, clear responsibilities, priorities and a shared knowledge base for your team.
infrahost provides the platform and takes care of technical operations. Your company defines support processes, groups, roles, templates and customer communication.
Scope of service
We focus on a stable technical foundation and a clean handover to your support team.
Requests, tasks, responsibilities and history are kept traceable in one place.
Support addresses are connected to Zammad and assigned to the appropriate groups.
The ticketing system can, for example, be reached at support.yourcompany.ch.
infrahost handles installation, platform maintenance and coordinated updates.
Database, attachments and configuration are protected according to the agreed backup strategy.
Availability and core platform services are monitored.
White-label delivery
Domain, logo, colours and contact information are adapted to your IT company’s identity. Email addresses and system notifications can be configured accordingly as well.
Your customers interact with your support organisation. infrahost remains the technical operator in the background and steps in only through the agreed escalation path.
Operations
You know your customers and support processes. We know the technical platform. This separation creates clear responsibilities and prevents updates or backups from being neglected in day-to-day operations.
Instance, domain, certificate, core mail integration and administrative access are configured.
Groups, roles and processes are coordinated with your team; business-specific content remains with you.
Technical updates are planned and carried out with the deployed integrations in mind.
Backups and the recovery path are defined according to the criticality of the ticketing system.
Transparency
Access rights, administrator roles, mail integration and backup locations are therefore planned deliberately. The specific data location and any customer requirements are considered before launch.
Frequently asked questions
For binding details on architecture, scope and service levels, we discuss your specific environment.
Ask a technical questionIn principle, yes. Version, database, attachments, integrations and mail channels need to be assessed first. We then create a migration and rollback plan.
We support the technical implementation. The business design of support processes, SLA and customer communication remains primarily with your IT company.
Updates are planned rather than installed blindly. Before major version changes, we assess dependencies and agree on a maintenance window.
Yes. Monitoring alerts, dedicated DNS and mail configurations, and coordinated backup and service-level concepts are particularly useful combinations.
Next step
We discuss users, mail channels, branding, migration and operational scope.