DE · EN

Call us

build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | built 2026-10-21 12:35 UTC format run

$ soultec get service/service-desk -o yaml$ soultec get service/service-desk -o json$ soultec get service/service-desk -o toml$ soultec get service/service-desk -o xml$ python3 service-desk.pyPS> ./service-desk.ps1$ go run service-desk.go$ node service-desk.js

apiVersion: soultec.ch/v1kind: Servicemetadata: name: service-desk locale: en labels: group: support capability/managed-services: 2.65 annotations: source: src/content/services/en/service-desk.md route: /en/services/service-desk/ schema: /nerd/schema/services.json markdown: /en/services/service-desk.mdspec: title: Service Desk group: support audience: [enterprise, provider] order: 1 tags: [managed-services] summary: >- One point of contact, run to ITIL, around the clock if you want it, in German, French and English. photoNeed: >- The support desk in an ordinary hour: headset, ticket queue on screen, the person actually working stub: false draft: false sections: - heading:

What is included

body: | - **A single point of contact**, rather than a list of extensions - **Qualified people** at the other end, not just a hand-off - **Ticketing to ITIL standard** - **Reachable by email, phone and ticket** - **Service hours to suit**, up to 24/7/365 - **Remote support** - **The interface to the vendors** involved in the problem - **German, French and English** - heading:

Premier Operations Service

body: | The reactive part of our operations services: tickets opened with us around the clock for incidents, service requests, change requests and problems, with a phone call back within 45 minutes for critical cases. Plus a shared Teams channel for the operational questions, straight to your soulTec team. - heading:

Routing incidents

body: | In an estate that grew, the person with the problem cannot tell whether it sits in the network, the server or the application, and every misrouting costs more time than the fix does. - heading:

What to watch

body: | Service hours are a cost decision rather than a technical one. Round the clock pays where an out-of-hours outage genuinely costs money, and elsewhere it is expensive reassurance. What has to be covered in which window belongs in the conversation before the contract, not in it.status: corpus: 315 solutions: - {ref: solutions/omnissa/workspace-one/workspace-one-assist, score: 0.58} - {ref: solutions/vmware/vmware-cloud-service-provider, score: 0.56} - {ref: solutions/omnissa/horizon/horizon-accelerator, score: 0.47} - {ref: solutions/omnissa/workspace-one/workspace-one-itsm-connector, score: 0.45} alsoLike: - {ref: services/managed-service, score: 0.52} - {ref: services/monitoring, score: 0.52} - {ref: solutions/igel/igel-onboarding-service, score: 0.45} experts: - {ref: experts/daniel-stadelmann, score: 0.33} - {ref: experts/valentina-cicmak, score: 0.29} - {ref: experts/matthias-frech, score: 0.24} search: /en/search.json

{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "service-desk", "locale": "en", "labels": { "group": "support", "capability/managed-services": 2.65 }, "annotations": { "source": "src/content/services/en/service-desk.md", "route": "/en/services/service-desk/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/service-desk.md" } }, "spec": { "title": "Service Desk", "group": "support", "audience": [ "enterprise", "provider" ], "order": 1, "tags": [ "managed-services" ], "summary": "One point of contact, run to ITIL, around the clock if you want it, in German, French and English.", "photoNeed": "The support desk in an ordinary hour: headset, ticket queue on screen, the person actually working", "stub": false, "draft": false, "sections": [ { "heading": "

What is included

", "body": "- **A single point of contact**, rather than a list of extensions\n- **Qualified people** at the other end, not just a hand-off\n- **Ticketing to ITIL standard**\n- **Reachable by email, phone and ticket**\n- **Service hours to suit**, up to 24/7/365\n- **Remote support**\n- **The interface to the vendors** involved in the problem\n- **German, French and English**" }, { "heading": "

Premier Operations Service

", "body": "The reactive part of our operations services: tickets opened with us around the clock for\nincidents, service requests, change requests and problems, with a phone call back within 45\nminutes for critical cases. Plus a shared Teams channel for the operational questions,\nstraight to your soulTec team." }, { "heading": "

Routing incidents

", "body": "In an estate that grew, the person with the problem cannot tell whether it sits in the\nnetwork, the server or the application, and every misrouting costs more time than the fix\ndoes." }, { "heading": "

What to watch

", "body": "Service hours are a cost decision rather than a technical one. Round the clock pays where an\nout-of-hours outage genuinely costs money, and elsewhere it is expensive reassurance. What\nhas to be covered in which window belongs in the conversation before the contract, not in\nit." } ] }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/omnissa/workspace-one/workspace-one-assist", "score": "0.58" }, { "ref": "solutions/vmware/vmware-cloud-service-provider", "score": "0.56" }, { "ref": "solutions/omnissa/horizon/horizon-accelerator", "score": "0.47" }, { "ref": "solutions/omnissa/workspace-one/workspace-one-itsm-connector", "score": "0.45" } ], "alsoLike": [ { "ref": "services/managed-service", "score": "0.52" }, { "ref": "services/monitoring", "score": "0.52" }, { "ref": "solutions/igel/igel-onboarding-service", "score": "0.45" } ], "experts": [ { "ref": "experts/daniel-stadelmann", "score": "0.33" }, { "ref": "experts/valentina-cicmak", "score": "0.29" }, { "ref": "experts/matthias-frech", "score": "0.24" } ], "search": "/en/search.json" }}

apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "service-desk"locale = "en"[metadata.labels]group = "support""capability/managed-services" = 2.65[metadata.annotations]source = "src/content/services/en/service-desk.md"route = "/en/services/service-desk/"schema = "/nerd/schema/services.json"markdown = "/en/services/service-desk.md"[spec]title = "Service Desk"group = "support"audience = ["enterprise", "provider"]order = 1tags = ["managed-services"]summary = "One point of contact, run to ITIL, around the clock if you want it, in German, French and English."photoNeed = "The support desk in an ordinary hour: headset, ticket queue on screen, the person actually working"stub = falsedraft = false[[spec.sections]]heading = "

What is included

"body = '''- **A single point of contact**, rather than a list of extensions- **Qualified people** at the other end, not just a hand-off- **Ticketing to ITIL standard**- **Reachable by email, phone and ticket**- **Service hours to suit**, up to 24/7/365- **Remote support**- **The interface to the vendors** involved in the problem- **German, French and English**'''[[spec.sections]]heading = "

Premier Operations Service

"body = '''The reactive part of our operations services: tickets opened with us around the clock forincidents, service requests, change requests and problems, with a phone call back within 45minutes for critical cases. Plus a shared Teams channel for the operational questions,straight to your soulTec team.'''[[spec.sections]]heading = "

Routing incidents

"body = '''In an estate that grew, the person with the problem cannot tell whether it sits in thenetwork, the server or the application, and every misrouting costs more time than the fixdoes.'''[[spec.sections]]heading = "

What to watch

"body = '''Service hours are a cost decision rather than a technical one. Round the clock pays where anout-of-hours outage genuinely costs money, and elsewhere it is expensive reassurance. Whathas to be covered in which window belongs in the conversation before the contract, not init.'''[status]corpus = 315search = "/en/search.json"[[status.solutions]]ref = "solutions/omnissa/workspace-one/workspace-one-assist"score = "0.58"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-service-provider"score = "0.56"[[status.solutions]]ref = "solutions/omnissa/horizon/horizon-accelerator"score = "0.47"[[status.solutions]]ref = "solutions/omnissa/workspace-one/workspace-one-itsm-connector"score = "0.45"[[status.alsoLike]]ref = "services/managed-service"score = "0.52"[[status.alsoLike]]ref = "services/monitoring"score = "0.52"[[status.alsoLike]]ref = "solutions/igel/igel-onboarding-service"score = "0.45"[[status.experts]]ref = "experts/daniel-stadelmann"score = "0.33"[[status.experts]]ref = "experts/valentina-cicmak"score = "0.29"[[status.experts]]ref = "experts/matthias-frech"score = "0.24"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Service"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>service-desk</name> <locale>en</locale> <labels> <group>support</group> <entry key="capability/managed-services">2.65</entry> </labels> <annotations> <source>src/content/services/en/service-desk.md</source> <route>/en/services/service-desk/</route> <schema>/nerd/schema/services.json</schema> <markdown>/en/services/service-desk.md</markdown> </annotations> </metadata> <spec> <title>Service Desk</title> <group>support</group> <audience> <item>enterprise</item> <item>provider</item> </audience> <order>1</order> <tags> <item>managed-services</item> </tags> <summary>One point of contact, run to ITIL, around the clock if you want it, in German, French and English.</summary> <photoNeed>The support desk in an ordinary hour: headset, ticket queue on screen, the person actually working</photoNeed> <stub>false</stub> <draft>false</draft> <sections> <section> <heading>

What is included

</heading> <body>- **A single point of contact**, rather than a list of extensions- **Qualified people** at the other end, not just a hand-off- **Ticketing to ITIL standard**- **Reachable by email, phone and ticket**- **Service hours to suit**, up to 24/7/365- **Remote support**- **The interface to the vendors** involved in the problem- **German, French and English** </body> </section> <section> <heading>

Premier Operations Service

</heading> <body>The reactive part of our operations services: tickets opened with us around the clock forincidents, service requests, change requests and problems, with a phone call back within 45minutes for critical cases. Plus a shared Teams channel for the operational questions,straight to your soulTec team. </body> </section> <section> <heading>

Routing incidents

</heading> <body>In an estate that grew, the person with the problem cannot tell whether it sits in thenetwork, the server or the application, and every misrouting costs more time than the fixdoes. </body> </section> <section> <heading>

What to watch

</heading> <body>Service hours are a cost decision rather than a technical one. Round the clock pays where anout-of-hours outage genuinely costs money, and elsewhere it is expensive reassurance. Whathas to be covered in which window belongs in the conversation before the contract, not init. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <solutions> <item> <ref>solutions/omnissa/workspace-one/workspace-one-assist</ref> <score>0.58</score> </item> <item> <ref>solutions/vmware/vmware-cloud-service-provider</ref> <score>0.56</score> </item> <item> <ref>solutions/omnissa/horizon/horizon-accelerator</ref> <score>0.47</score> </item> <item> <ref>solutions/omnissa/workspace-one/workspace-one-itsm-connector</ref> <score>0.45</score> </item> </solutions> <alsoLike> <item> <ref>services/managed-service</ref> <score>0.52</score> </item> <item> <ref>services/monitoring</ref> <score>0.52</score> </item> <item> <ref>solutions/igel/igel-onboarding-service</ref> <score>0.45</score> </item> </alsoLike> <experts> <item> <ref>experts/daniel-stadelmann</ref> <score>0.33</score> </item> <item> <ref>experts/valentina-cicmak</ref> <score>0.29</score> </item> <item> <ref>experts/matthias-frech</ref> <score>0.24</score> </item> </experts> <search>/en/search.json</search> </status></manifest>

# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "service-desk", "locale": "en", "labels": { "group": "support", "capability/managed-services": 2.65, }, "annotations": { "source": "src/content/services/en/service-desk.md", "route": "/en/services/service-desk/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/service-desk.md", }, }, "spec": { "title": "Service Desk", "group": "support", "audience": ["enterprise", "provider"], "order": 1, "tags": ["managed-services"], "summary": "One point of contact, run to ITIL, around the clock if you want it, in German, French and English.", "photoNeed": "The support desk in an ordinary hour: headset, ticket queue on screen, the person actually working", "stub": False, "draft": False, "sections": [ { "heading": "

What is included

", "body": ( "- **A single point of contact**, rather than a list of extensions\n" "- **Qualified people** at the other end, not just a hand-off\n" "- **Ticketing to ITIL standard**\n" "- **Reachable by email, phone and ticket**\n" "- **Service hours to suit**, up to 24/7/365\n" "- **Remote support**\n" "- **The interface to the vendors** involved in the problem\n" "- **German, French and English**" ), }, { "heading": "

Premier Operations Service

", "body": ( "The reactive part of our operations services: tickets opened with us around the clock for\n" "incidents, service requests, change requests and problems, with a phone call back within 45\n" "minutes for critical cases. Plus a shared Teams channel for the operational questions,\n" "straight to your soulTec team." ), }, { "heading": "

Routing incidents

", "body": ( "In an estate that grew, the person with the problem cannot tell whether it sits in the\n" "network, the server or the application, and every misrouting costs more time than the fix\n" "does." ), }, { "heading": "

What to watch

", "body": ( "Service hours are a cost decision rather than a technical one. Round the clock pays where an\n" "out-of-hours outage genuinely costs money, and elsewhere it is expensive reassurance. What\n" "has to be covered in which window belongs in the conversation before the contract, not in\n" "it." ), }, ], }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/omnissa/workspace-one/workspace-one-assist", "score": "0.58", }, { "ref": "solutions/vmware/vmware-cloud-service-provider", "score": "0.56", }, { "ref": "solutions/omnissa/horizon/horizon-accelerator", "score": "0.47", }, { "ref": "solutions/omnissa/workspace-one/workspace-one-itsm-connector", "score": "0.45", }, ], "alsoLike": [ { "ref": "services/managed-service", "score": "0.52", }, { "ref": "services/monitoring", "score": "0.52", }, { "ref": "solutions/igel/igel-onboarding-service", "score": "0.45", }, ], "experts": [ { "ref": "experts/daniel-stadelmann", "score": "0.33", }, { "ref": "experts/valentina-cicmak", "score": "0.29", }, { "ref": "experts/matthias-frech", "score": "0.24", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))

# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Service' metadata = [ordered]@{ name = 'service-desk' locale = 'en' labels = [ordered]@{ group = 'support' 'capability/managed-services' = 2.65 } annotations = [ordered]@{ source = 'src/content/services/en/service-desk.md' route = '/en/services/service-desk/' schema = '/nerd/schema/services.json' markdown = '/en/services/service-desk.md' } } spec = [ordered]@{ title = 'Service Desk' group = 'support' audience = @('enterprise', 'provider') order = 1 tags = @('managed-services') summary = 'One point of contact, run to ITIL, around the clock if you want it, in German, French and English.' photoNeed = 'The support desk in an ordinary hour: headset, ticket queue on screen, the person actually working' stub = $false draft = $false sections = @( [ordered]@{ heading = '

What is included

' body = @'- **A single point of contact**, rather than a list of extensions- **Qualified people** at the other end, not just a hand-off- **Ticketing to ITIL standard**- **Reachable by email, phone and ticket**- **Service hours to suit**, up to 24/7/365- **Remote support**- **The interface to the vendors** involved in the problem- **German, French and English**'@ } [ordered]@{ heading = '

Premier Operations Service

' body = @'The reactive part of our operations services: tickets opened with us around the clock forincidents, service requests, change requests and problems, with a phone call back within 45minutes for critical cases. Plus a shared Teams channel for the operational questions,straight to your soulTec team.'@ } [ordered]@{ heading = '

Routing incidents

' body = @'In an estate that grew, the person with the problem cannot tell whether it sits in thenetwork, the server or the application, and every misrouting costs more time than the fixdoes.'@ } [ordered]@{ heading = '

What to watch

' body = @'Service hours are a cost decision rather than a technical one. Round the clock pays where anout-of-hours outage genuinely costs money, and elsewhere it is expensive reassurance. Whathas to be covered in which window belongs in the conversation before the contract, not init.'@ } ) } status = [ordered]@{ corpus = 315 solutions = @( [ordered]@{ ref = 'solutions/omnissa/workspace-one/workspace-one-assist' score = '0.58' } [ordered]@{ ref = 'solutions/vmware/vmware-cloud-service-provider' score = '0.56' } [ordered]@{ ref = 'solutions/omnissa/horizon/horizon-accelerator' score = '0.47' } [ordered]@{ ref = 'solutions/omnissa/workspace-one/workspace-one-itsm-connector' score = '0.45' } ) alsoLike = @( [ordered]@{ ref = 'services/managed-service' score = '0.52' } [ordered]@{ ref = 'services/monitoring' score = '0.52' } [ordered]@{ ref = 'solutions/igel/igel-onboarding-service' score = '0.45' } ) experts = @( [ordered]@{ ref = 'experts/daniel-stadelmann' score = '0.33' } [ordered]@{ ref = 'experts/valentina-cicmak' score = '0.29' } [ordered]@{ ref = 'experts/matthias-frech' score = '0.24' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32

// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": map[string]any{ "name": "service-desk", "locale": "en", "labels": map[string]any{ "group": "support", "capability/managed-services": 2.65, }, "annotations": map[string]any{ "source": "src/content/services/en/service-desk.md", "route": "/en/services/service-desk/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/service-desk.md", }, }, "spec": map[string]any{ "title": "Service Desk", "group": "support", "audience": []any{"enterprise", "provider"}, "order": 1, "tags": []any{"managed-services"}, "summary": "One point of contact, run to ITIL, around the clock if you want it, in German, French and English.", "photoNeed": "The support desk in an ordinary hour: headset, ticket queue on screen, the person actually working", "stub": false, "draft": false, "sections": []any{ map[string]any{ "heading": "

What is included

", "body": "- **A single point of contact**, rather than a list of extensions\n" + "- **Qualified people** at the other end, not just a hand-off\n" + "- **Ticketing to ITIL standard**\n" + "- **Reachable by email, phone and ticket**\n" + "- **Service hours to suit**, up to 24/7/365\n" + "- **Remote support**\n" + "- **The interface to the vendors** involved in the problem\n" + "- **German, French and English**", }, map[string]any{ "heading": "

Premier Operations Service

", "body": "The reactive part of our operations services: tickets opened with us around the clock for\n" + "incidents, service requests, change requests and problems, with a phone call back within 45\n" + "minutes for critical cases. Plus a shared Teams channel for the operational questions,\n" + "straight to your soulTec team.", }, map[string]any{ "heading": "

Routing incidents

", "body": "In an estate that grew, the person with the problem cannot tell whether it sits in the\n" + "network, the server or the application, and every misrouting costs more time than the fix\n" + "does.", }, map[string]any{ "heading": "

What to watch

", "body": "Service hours are a cost decision rather than a technical one. Round the clock pays where an\n" + "out-of-hours outage genuinely costs money, and elsewhere it is expensive reassurance. What\n" + "has to be covered in which window belongs in the conversation before the contract, not in\n" + "it.", }, }, }, "status": map[string]any{ "corpus": 315, "solutions": []any{ map[string]any{ "ref": "solutions/omnissa/workspace-one/workspace-one-assist", "score": "0.58", }, map[string]any{ "ref": "solutions/vmware/vmware-cloud-service-provider", "score": "0.56", }, map[string]any{ "ref": "solutions/omnissa/horizon/horizon-accelerator", "score": "0.47", }, map[string]any{ "ref": "solutions/omnissa/workspace-one/workspace-one-itsm-connector", "score": "0.45", }, }, "alsoLike": []any{ map[string]any{ "ref": "services/managed-service", "score": "0.52", }, map[string]any{ "ref": "services/monitoring", "score": "0.52", }, map[string]any{ "ref": "solutions/igel/igel-onboarding-service", "score": "0.45", }, }, "experts": []any{ map[string]any{ "ref": "experts/daniel-stadelmann", "score": "0.33", }, map[string]any{ "ref": "experts/valentina-cicmak", "score": "0.29", }, map[string]any{ "ref": "experts/matthias-frech", "score": "0.24", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}

// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Service", metadata: { name: "service-desk", locale: "en", labels: { group: "support", "capability/managed-services": 2.65, }, annotations: { source: "src/content/services/en/service-desk.md", route: "/en/services/service-desk/", schema: "/nerd/schema/services.json", markdown: "/en/services/service-desk.md", }, }, spec: { title: "Service Desk", group: "support", audience: ["enterprise", "provider"], order: 1, tags: ["managed-services"], summary: "One point of contact, run to ITIL, around the clock if you want it, in German, French and English.", photoNeed: "The support desk in an ordinary hour: headset, ticket queue on screen, the person actually working", stub: false, draft: false, sections: [ { heading: "

What is included

", body: "- **A single point of contact**, rather than a list of extensions\n" + "- **Qualified people** at the other end, not just a hand-off\n" + "- **Ticketing to ITIL standard**\n" + "- **Reachable by email, phone and ticket**\n" + "- **Service hours to suit**, up to 24/7/365\n" + "- **Remote support**\n" + "- **The interface to the vendors** involved in the problem\n" + "- **German, French and English**", }, { heading: "

Premier Operations Service

", body: "The reactive part of our operations services: tickets opened with us around the clock for\n" + "incidents, service requests, change requests and problems, with a phone call back within 45\n" + "minutes for critical cases. Plus a shared Teams channel for the operational questions,\n" + "straight to your soulTec team.", }, { heading: "

Routing incidents

", body: "In an estate that grew, the person with the problem cannot tell whether it sits in the\n" + "network, the server or the application, and every misrouting costs more time than the fix\n" + "does.", }, { heading: "

What to watch

", body: "Service hours are a cost decision rather than a technical one. Round the clock pays where an\n" + "out-of-hours outage genuinely costs money, and elsewhere it is expensive reassurance. What\n" + "has to be covered in which window belongs in the conversation before the contract, not in\n" + "it.", }, ], }, status: { corpus: 315, solutions: [ { ref: "solutions/omnissa/workspace-one/workspace-one-assist", score: "0.58", }, { ref: "solutions/vmware/vmware-cloud-service-provider", score: "0.56", }, { ref: "solutions/omnissa/horizon/horizon-accelerator", score: "0.47", }, { ref: "solutions/omnissa/workspace-one/workspace-one-itsm-connector", score: "0.45", }, ], alsoLike: [ { ref: "services/managed-service", score: "0.52", }, { ref: "services/monitoring", score: "0.52", }, { ref: "solutions/igel/igel-onboarding-service", score: "0.45", }, ], experts: [ { ref: "experts/daniel-stadelmann", score: "0.33", }, { ref: "experts/valentina-cicmak", score: "0.29", }, { ref: "experts/matthias-frech", score: "0.24", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 71 lines · YAML · validated at build# 102 lines · JSON · validated at build# 110 lines · TOML · validated at build# 125 lines · XML · validated at build# 126 lines · Python · read back at build, equals the JSON record# 123 lines · PowerShell · read back at build, equals the JSON record# 130 lines · Go · read back at build, equals the JSON record# 115 lines · JavaScript · read back at build, equals the JSON record · served at /en/services/service-desk.md

Service · support

Service Desk

One point of contact, run to ITIL, around the clock if you want it, in German, French and English.

Topics Managed Services 2.65

04Solutions

01Capabilities

315Corpus

photograph wantedThe support desk in an ordinary hour: headset, ticket queue on screen, the person actually working

What is included

A single point of contact, rather than a list of extensions
Qualified people at the other end, not just a hand-off
Ticketing to ITIL standard
Reachable by email, phone and ticket
Service hours to suit, up to 24/7/365
Remote support
The interface to the vendors involved in the problem
German, French and English

Premier Operations Service

The reactive part of our operations services: tickets opened with us around the clock for incidents, service requests, change requests and problems, with a phone call back within 45 minutes for critical cases. Plus a shared Teams channel for the operational questions, straight to your soulTec team.

Routing incidents

In an estate that grew, the person with the problem cannot tell whether it sits in the network, the server or the application, and every misrouting costs more time than the fix does.

What to watch

Service hours are a cost decision rather than a technical one. Round the clock pays where an out-of-hours outage genuinely costs money, and elsewhere it is expensive reassurance. What has to be covered in which window belongs in the conversation before the contract, not in it.

Experts for this

Daniel Stadelmann

Senior Solution Architect

Managed Services

0.33

Valentina Cicmak

System Engineer

Managed Services

0.29

Matthias Frech

Senior System Engineer

Managed Services

0.24

Maybe you? Take a look at our open roles.

Support 0.52

Managed Service

Support 0.52

Monitoring

IGEL 0.45

What is included

Premier Operations Service

Routing incidents

What to watch

What is included

Premier Operations Service

Routing incidents

What to watch

What is included

Premier Operations Service

Routing incidents

What to watch

What is included

Premier Operations Service

Routing incidents

What to watch

What is included

Premier Operations Service

Routing incidents

What to watch

What is included

Premier Operations Service

Routing incidents

What to watch

What is included

Premier Operations Service

Routing incidents

What to watch

What is included

Premier Operations Service

Routing incidents

What to watch

Service Desk

What is included

Premier Operations Service

Routing incidents

What to watch

Experts for this

Daniel Stadelmann

Valentina Cicmak

Matthias Frech

You might also like

Managed Service

Monitoring

Onboarding Service