The practical questions, answered.

Mizan is an enterprise IT service management platform with a dedicated employee portal and an agent command center. It connects service requests, incidents, problems, changes, knowledge, assets, SLAs, automations, reporting, and administration in one system.

Mizan is designed for organizations and service teams that need more operational structure than a shared inbox or lightweight ticket tool, while still wanting a clear experience for employees and agents.

No. The accountless employee and command-center demos use synthetic people, tickets, articles, and metrics. Demo interactions stay in the current browser tab, are never saved, and do not send email or trigger automations.

Organization deployments receive their own configured application experience, database, branding, access rules, and service workflows. The public marketing pages shown here are specific to the Mizan demo deployment.

Yes. Mizan includes configurable organization SSO, allowed-domain controls, separate employee and staff sessions, staff roles, team structures, and permission-aware administrative surfaces.

Mizan supports AES-256-GCM encryption for stored attachments and selected secrets, signed sessions, secure transport expectations, role-based controls, and security-focused administrative settings. Final controls depend on the deployment configuration and agreement.

Mizan can provide AI assistance inside agent workflows. Organizations configure their own supported provider or local model connection, control runtime behavior, and keep people responsible for final decisions.

Each plan has a monthly platform price that includes a set number of agents, unlimited end users, and a dedicated Mizan environment. Additional agents are available at the published tier rate, with volume pricing for Enterprise deployments above 50 agents.

Yes. Categories, forms, sites, departments, roles, teams, queues, SLAs, automations, branding, security settings, and integrations can be shaped around the organization’s operating model.

Use the form on the contact page and include your role, organization, current service desk approach, and the workflows you want to explore so the session can be tailored to you.