DE · EN

Call us

apiVersion: soultec.ch/v1kind: Servicemetadata: name: service-desk locale: en labels: group: support capability/managed-services: 3.23 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 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** - **German, French and English** - heading:

Why the single point of contact is the point

body: | Because the real problem is rarely response time, it is knowing who to call. 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: 267 solutions: - {ref: solutions/vmware/vmware-cloud-service-provider, score: 0.59} - {ref: solutions/hpe/hpe-greenlake, score: 0.44} - {ref: solutions/hpe, score: 0.36} alsoLike: - {ref: services/managed-service, score: 0.54} - {ref: services/monitoring, score: 0.54} - {ref: experts/valentina-cicmak, score: 0.35} experts: - {ref: experts/valentina-cicmak, score: 0.35} - {ref: experts/matthias-frech, score: 0.29} - {ref: experts/mike-schmid, score: 0.25}

{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "service-desk", "locale": "en", "labels": { "group": "support", "capability/managed-services": "3.23" }, "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", "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- **German, French and English**" }, { "heading": "

Why the single point of contact is the point

", "body": "Because the real problem is rarely response time, it is knowing who to call. In an estate\nthat grew, the person with the problem cannot tell whether it sits in the network, the\nserver 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\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": 267, "solutions": [ { "ref": "solutions/vmware/vmware-cloud-service-provider", "score": "0.59" }, { "ref": "solutions/hpe/hpe-greenlake", "score": "0.44" }, { "ref": "solutions/hpe", "score": "0.36" } ], "alsoLike": [ { "ref": "services/managed-service", "score": "0.54" }, { "ref": "services/monitoring", "score": "0.54" }, { "ref": "experts/valentina-cicmak", "score": "0.35" } ], "experts": [ { "ref": "experts/valentina-cicmak", "score": "0.35" }, { "ref": "experts/matthias-frech", "score": "0.29" }, { "ref": "experts/mike-schmid", "score": "0.25" } ] }}

apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "service-desk"locale = "en"[metadata.labels]group = "support""capability/managed-services" = "3.23"[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"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[[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**- **German, French and English**'''[[sections]]heading = "

Why the single point of contact is the point

"body = '''Because the real problem is rarely response time, it is knowing who to call. In an estatethat grew, the person with the problem cannot tell whether it sits in the network, theserver or the application, and every misrouting costs more time than the fix does.'''[[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 = 267[[status.solutions]]ref = "solutions/vmware/vmware-cloud-service-provider"score = "0.59"[[status.solutions]]ref = "solutions/hpe/hpe-greenlake"score = "0.44"[[status.solutions]]ref = "solutions/hpe"score = "0.36"[[status.alsoLike]]ref = "services/managed-service"score = "0.54"[[status.alsoLike]]ref = "services/monitoring"score = "0.54"[[status.alsoLike]]ref = "experts/valentina-cicmak"score = "0.35"[[status.experts]]ref = "experts/valentina-cicmak"score = "0.35"[[status.experts]]ref = "experts/matthias-frech"score = "0.29"[[status.experts]]ref = "experts/mike-schmid"score = "0.25"

<?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">3.23</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> <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> </spec> <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**- **German, French and English** </body> </section> <section> <heading>

Why the single point of contact is the point

</heading> <body>Because the real problem is rarely response time, it is knowing who to call. In an estatethat grew, the person with the problem cannot tell whether it sits in the network, theserver or the application, and every misrouting costs more time than the fix does. </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> <status> <corpus>267</corpus> <solutions> <item> <ref>solutions/vmware/vmware-cloud-service-provider</ref> <score>0.59</score> </item> <item> <ref>solutions/hpe/hpe-greenlake</ref> <score>0.44</score> </item> <item> <ref>solutions/hpe</ref> <score>0.36</score> </item> </solutions> <alsoLike> <item> <ref>services/managed-service</ref> <score>0.54</score> </item> <item> <ref>services/monitoring</ref> <score>0.54</score> </item> <item> <ref>experts/valentina-cicmak</ref> <score>0.35</score> </item> </alsoLike> <experts> <item> <ref>experts/valentina-cicmak</ref> <score>0.35</score> </item> <item> <ref>experts/matthias-frech</ref> <score>0.29</score> </item> <item> <ref>experts/mike-schmid</ref> <score>0.25</score> </item> </experts> </status></manifest>

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 3.23

03Solutions

01Capabilities

267Corpus

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
German, French and English

Why the single point of contact is the point

Because the real problem is rarely response time, it is knowing who to call. 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.