SAP Service Cloud V2 Partner in Switzerland and the DACH Region

Finding an SAP Service Cloud V2 partner in the DACH region who has actually delivered the product in production is not straightforward. SAP lists hundreds of CX partners. Most of them built their reputation on C4C or Sales Cloud. Service Cloud V2 is a different product with a different architecture, different integration patterns, and different configuration model. The overlap in expertise is smaller than you’d expect.

This post explains who we are, what we’ve delivered in Service Cloud V2 specifically, and why DACH companies with serious service operations choose us.

TL;DR: Spadoom AG is an SAP Gold Partner headquartered in Zurich. We specialize in SAP Service Cloud V2 implementations across Switzerland, Germany, and Austria. We’ve delivered V2 for biotech companies, food distributors, and B2B manufacturers — including omnichannel configuration, Joule AI setup, and deep S/4HANA integration. Mid-market implementations go live in 6-12 weeks. We also build custom service extensions on SAP BTP. Get a free Service Cloud V2 assessment.

Why Your Service Cloud V2 Partner Needs to Be Local

SAP Service Cloud V2 is not a SaaS tool you configure over a Zoom call. It touches your service agents’ daily workflows, your SLA definitions, your escalation paths, your integration with ERP for warranty checks and installed base lookups. Getting this right requires understanding how your service organisation actually works — and in the DACH region, that means understanding things that don’t translate well across continents.

Multilingual Service Is the Default, Not a Feature

A Swiss company with customers in Zurich, Geneva, and Lugano runs service operations in at least three languages. Your ticket routing rules, email templates, knowledge base articles, and agent interfaces need to reflect that. Not as an afterthought. From day one.

We configure Service Cloud V2 for multilingual service operations on every Swiss project. Language-dependent routing, localised email templates, multilingual knowledge articles with automatic language detection — this is standard in our implementations, not an add-on.

Beyond language, DACH service culture expects fast, precise responses. A customer in Munich who logs a ticket at 08:00 expects acknowledgement before lunch, not a “we’ll get back to you within 48 hours” auto-reply. Your SLA configuration needs to match those expectations.

Data Protection Is a Service Configuration Problem

Service cases contain personal data. Customer names, contact details, purchase history, complaint descriptions, sometimes health or safety information. In Switzerland, the revised Federal Act on Data Protection (nDSG) governs how you handle this. In Germany and Austria, the GDPR applies.

Your Service Cloud V2 configuration needs consent management workflows, data retention policies tied to case closure, right-to-deletion processes that actually work, and audit trails your compliance team can use. These are not theoretical requirements. The Swiss FDPIC and German data protection authorities enforce them.

A partner based in Zurich who configures nDSG-compliant service workflows every month handles this differently from one who encounters Swiss data protection law for the first time on your project.

On-Site Workshops With Your Service Team

Service implementations require deep discovery. You need to map your service processes: how tickets arrive (email, phone, chat, portal), how they get classified and routed, what information agents need to resolve them, when and how escalations happen, which SLA targets apply to which customer segments.

This discovery happens best in person. We run service process workshops in Zurich, Bern, Basel, Vienna, Munich, and Milan. When your senior agents explain how they actually handle a complex warranty claim — not how the process document says they should — we’re in the room. That matters.

DACH Expectations: Precision and Accountability

DACH companies expect fixed-price proposals, defined scope, and contractual clarity. Your service management team wants to know exactly what they’re getting, when they’re getting it, and what it costs. No open-ended sprints. No “we’ll figure out the scope as we go.”

We quote fixed-price Service Cloud V2 implementations. We define the scope before we start. We deliver what we agreed to deliver.

About Spadoom AG

Spadoom AG was founded in 2018 and is headquartered in Zurich, Switzerland. We are an SAP Gold Partner specializing in the SAP Customer Experience (CX) portfolio.

Offices: Switzerland (Zurich — headquarters), Italy (Milan), Austria (Vienna), Estonia (Tallinn).

Team: Certified SAP CX consultants, developers, and architects. Our consultants hold SAP certifications across Service Cloud, Sales Cloud, Commerce Cloud, Emarsys, CDP, and the SAP Business Technology Platform (BTP).

Specialization: SAP Service Cloud V2, SAP Sales Cloud V2, and the broader SAP CX portfolio — including Commerce Cloud, Emarsys, Customer Data Platform, CIAM, Loyalty Management, CPQ, and Field Service Management. See the full list at SAP CX Solutions.

Approach: We are a boutique consultancy. When you sign a project with us, the people in the proposal meeting are the people who deliver your project. No bait-and-switch with junior resources. We’ve written about what to look for in How to Choose an SAP CX Partner.

You can learn more about our team and certifications.

Our SAP Service Cloud V2 Track Record

We are among the few SAP partners in the DACH region with production Service Cloud V2 implementations. Not demos. Not proof-of-concepts. Live systems with real service teams handling real cases every day.

Miltenyi Biotec — Biotechnology / Life Sciences

Miltenyi Biotec is a global biotech company that needed its SAP landscape to work as one connected system rather than a collection of silos. We’ve been their SAP partner for over five years.

We integrated SAP Service Cloud V2 into a platform that already included Commerce Cloud, Emarsys, Customer Data Platform, and S/4HANA. The service desk now has full visibility into order history, marketing interactions, and product data — all within the agent’s workspace. No tab-switching. No “let me check another system.”

The result: a unified service experience where agents resolve cases faster because they have the full customer picture.

Read the full story: Miltenyi Biotec Success Story.

intelligentfood Schweiz AG — Food & Beverage Distribution

intelligentfood manages indirect sales channels for brands like El Tony Mate. A large field sales force with heavy customer-service requirements across Swiss retail locations.

We delivered SAP Sales Cloud V2 and SAP Service Cloud V2 together in three months — from kickoff to go-live. The service configuration handles inbound queries from retail partners, order-related issues, and product complaints, all routed to the right team based on case type and region. Custom BTP applications extend the standard platform with mobile-optimised workflows, all integrated with S/4HANA Public Cloud via SAP Integration Suite.

Read the full story: intelligentfood Success Story.

What We Configure

Every Service Cloud V2 implementation we deliver includes core platform configuration tailored to your service model:

• Omnichannel inbox — email, phone (with our CTI integration), chat, and customer portal channels consolidated in one agent workspace
• Case classification and routing — rule-based and ML-powered routing to the right agent team based on case type, product, customer segment, language, and skills
• SLA management — configurable response and resolution targets by customer tier, product line, or case severity, with automatic escalation
• Joule AI capabilities — sentiment analysis, case summarisation, suggested responses, and knowledge article recommendations. See our deep dive on Digital Service Agents
• Knowledge management — structured knowledge base with automatic article suggestions based on case context
• S/4HANA integration — installed base, warranty lookup, order history, and product master data available in the agent workspace without leaving Service Cloud
• Reporting and analytics — service dashboards with case volume, SLA compliance, agent utilisation, and customer satisfaction metrics

For a step-by-step breakdown, see our Service Cloud V2 Implementation Guide.

Typical Implementation Timeline

For mid-market companies (20-150 service agents), our SAP Service Cloud V2 implementations typically run 6 to 12 weeks from kickoff to go-live. The exact timeline depends on:

• Number of inbound channels (email only vs. email + phone + chat + portal)
• Complexity of routing rules and SLA definitions
• Depth of S/4HANA integration (basic order lookup vs. full installed base and warranty)
• Custom extension needs on SAP BTP
• Data migration volume from legacy service tools

Larger enterprises with complex multi-country rollouts or deep integration requirements take 3-5 months. But even those start with a focused first phase that delivers value quickly.

What Sets Us Apart From Other DACH Partners

We Build, Not Just Configure

Most SAP partners configure the standard product and stop there. We build on top of it.

We develop custom extensions on SAP BTP using the SAP Cloud Application Programming Model (CAP). Our own product — Spadoom Engage — is a full CTI integration for SAP Sales and Service Cloud V2 that runs in production across multiple customer tenants. It provides click-to-call, caller identification, screen pop with customer context, and call logging directly inside the Service Cloud agent workspace.

When your requirements go beyond what the standard platform offers — a customer self-service portal, a custom approval workflow for high-value warranty claims, a mobile field service extension — we don’t need to bring in a separate development team. The people who understand your service processes write the code. That matters.

Combined Sales and Service Deployment

SAP Sales Cloud V2 and Service Cloud V2 share the same underlying platform. Implementing them together is more efficient than running two separate projects. Most of our DACH implementations include both.

A combined deployment means your sales team and service team share the same customer record. When a service agent handles a complaint, they see the full sales history. When a sales rep prepares for a meeting, they see open service cases. No data silos. No duplicate records.

We’ve written about the Sales Cloud V2 side in detail: SAP Sales Cloud V2 Partner in Switzerland and the DACH Region.

Full SAP CX Portfolio

Service Cloud V2 rarely exists in isolation. Your sales team runs on SAP Sales Cloud V2. Your marketing team sends campaigns through Emarsys. Your field technicians use FSM. Your e-commerce platform runs on SAP Commerce Cloud.

We cover the full SAP CX portfolio. One partner, one relationship, one integrated solution. See all solutions.

Swiss Quality, Competitive Pricing

We deliver with Swiss precision — on time, on spec, on budget. But we are not a Big Four consultancy, and we don’t price like one.

Our fixed-price models, lean team structure, and focus on SAP CX mean you get senior consultants at rates that make sense for mid-market companies. No inflated day rates. No army of juniors billing hours.

For a detailed cost breakdown, see our SAP Sales Cloud V2 Pricing Guide — the licensing model is shared with Service Cloud V2.

How We Compare to Sybit, Adesso, and Other DACH Partners

The DACH market for SAP Service Cloud V2 implementation is dominated by two types of partners: large system integrators like Sybit and Adesso with hundreds of consultants, and smaller boutique firms. Here’s how we differ.

Sybit (NTT DATA Group)

Sybit is a well-known SAP CX partner in Germany. They have a large team and long history with SAP. The trade-off: as part of the NTT DATA group, projects often involve layers of management, and the senior architects who present during the sales process aren’t always the people who do the configuration. Sybit’s strength is scale — if you need 50 consultants across multiple countries, they can deliver that. For mid-market DACH companies that need 2-5 senior consultants who stay on the project from start to finish, our model fits better.

Adesso SE

Adesso is a large German IT services company with SAP CX as one of many practice areas. They cover everything from custom software development to SAP ERP to cloud infrastructure. The breadth is a strength for companies that want one vendor for everything. The trade-off: SAP Service Cloud V2 is a fraction of their business. At Spadoom, it’s the core of what we do. When V2 ships a new feature or changes an API, we know about it because we’re working with the product every day, not because someone forwarded an SAP release note.

Where Spadoom Fits

We are a focused SAP CX boutique. That means:

• Named team members — you know who will work on your project before you sign the contract
• Senior consultants only — no pyramid staffing with juniors doing the configuration while seniors attend other projects
• V2-specific depth — we don’t just know SAP CX. We know the V2 platform, its limitations, its workarounds, and its roadmap
• Extension development in-house — custom BTP apps, CAP services, and integration middleware built by the same team that configures the platform
• Swiss-headquartered — we understand nDSG, multilingual operations, and DACH business culture because it’s where we live and work

Industries We Serve in the DACH Region

Manufacturing and Industrial

Manufacturing companies in DACH need service desks that handle warranty claims, spare parts inquiries, and machine downtime reports. Service Cloud V2’s installed base management, integration with SAP S/4HANA for product and warranty data, and ML-based case routing make it a natural fit. We’ve implemented V2 for manufacturers where the service case often starts with a machine serial number and needs to pull warranty status, service history, and spare parts availability from ERP before the agent can respond.

Pharmaceutical and Life Sciences

Pharma companies in Switzerland and Germany handle regulated inquiries — adverse event reports, product quality complaints, medical information requests. Each case type has different routing rules, documentation requirements, and retention policies. Service Cloud V2’s configurable case types, mandatory field rules, and audit trails support these requirements. The platform’s EU data residency options align with GxP requirements. Our Miltenyi Biotec project is a direct example of Service Cloud V2 in this sector.

Professional Services

Consulting firms, engineering companies, and law firms across DACH need service management that tracks client requests, project-related issues, and internal knowledge. Service Cloud V2’s account-centric service model, knowledge management, and activity timeline give professional services firms the structure they need without the overhead of a system designed for high-volume consumer support.

Wholesale and Distribution

Distribution companies with large customer bases — food and beverage, building materials, industrial supplies — handle high volumes of order-related service requests: delivery issues, returns, quality complaints, invoice discrepancies. Service Cloud V2’s integration with S/4HANA for real-time order and delivery data means agents can resolve these cases without switching systems. Our intelligentfood implementation is a direct example.

Technology and Software

Software companies selling into DACH enterprise accounts need service management that integrates with their development workflow. Service Cloud V2’s REST APIs, event-driven architecture, and extensibility via SAP BTP make it possible to connect the service desk with Jira, GitHub, or internal incident management systems. The platform’s SLA management handles tiered support contracts — essential for B2B software with premium support tiers.

How to Evaluate an SAP Service Cloud V2 Partner

Choosing the wrong implementation partner is the single biggest risk in any service platform project. Here’s what to check:

V2-specific experience. How many SAP Service Cloud V2 projects have they completed? Not V1 (C4C). Not Sales Cloud V2 only. Service Cloud V2 specifically. The case management model, routing engine, and knowledge management are different from Sales Cloud — a partner with deep Sales Cloud experience doesn’t automatically deliver a strong Service Cloud implementation.

Omnichannel track record. Have they configured email, phone, chat, and portal channels in production? Multi-channel configuration is where complexity lives. A partner who has only done email-based service desks will struggle with CTI integration and real-time chat routing.

Integration depth. Service Cloud V2’s value multiplies with S/4HANA integration. Ask how they handle installed base sync, warranty lookups, and real-time order data. If the answer is “we’ll figure it out during the project,” that’s a red flag.

Named team members. Who will actually work on your project? Get names and CVs. If the partner describes “roles” instead of people, keep looking.

Reference customers. Can they connect you with a past Service Cloud V2 client? Can you speak directly with the service manager on the client side?

Post-go-live support. What happens after launch? Service platforms need ongoing optimisation — routing rules get refined, new channels get added, AI models improve with more data. What support model do they offer?

We’ve written a detailed guide: How to Choose an SAP CX Partner.

Data Privacy and Compliance

Service operations handle sensitive customer data. In the DACH region, this is not optional — it’s regulated.

Swiss nDSG

Switzerland’s revised Federal Act on Data Protection (nDSG, in force since 1 September 2023) requires companies to inform individuals about data collection, implement appropriate technical and organisational measures, and report breaches to the FDPIC. For service operations, this means consent capture on customer portals, data retention policies tied to case resolution, and deletion workflows that actually purge personal data from closed cases.

EU GDPR

For operations in Germany and Austria, the GDPR applies. Service Cloud V2 provides built-in tools for consent management, data subject access requests (DSARs), and audit trails. But these tools need correct configuration for your specific case types and data categories.

Where Your Data Lives

SAP Service Cloud V2 runs on hyperscaler infrastructure with EU data centre options. For Swiss companies that require data residency within the EU or specifically within Switzerland, we configure deployments to align with your legal requirements.

Spadoom’s Approach

We treat data privacy as a core implementation workstream. During discovery, we map your service data flows, identify personal data categories in each case type, and configure the platform to meet nDSG and GDPR requirements from day one. Our consultants deal with Swiss and EU data protection law on every project. Read about how we work.

Getting Started

Free Service Cloud V2 Assessment

Not sure if SAP Service Cloud V2 is right for your service organisation? We offer a free assessment. In a 60-minute session, we review your current service model, identify gaps, and give you an honest recommendation — including whether V2 is the right fit or whether another tool would serve you better.

Request your Service Cloud V2 assessment.

What to Expect in a First Conversation

No sales pitch. No slides. We’ll ask about your service team structure, your current tools, your ticket volumes, your SLA targets, and your biggest pain points. You’ll leave with a clear picture of what a Service Cloud V2 implementation would look like for your organisation — scope, timeline, and budget range.

Contact Us

Ready to talk? Reach out directly. Or call us — we’re in Zurich, and we pick up the phone.

Frequently Asked Questions

Does Spadoom implement SAP Service Cloud V2?

Yes. Spadoom AG is a certified SAP Gold Partner with specific Service Cloud V2 implementation expertise. We’ve delivered V2 for B2B service teams across manufacturing, biotech, food distribution, and professional services. You can verify our partner status on the SAP Partner Finder. See our certifications page.

Can you implement Sales Cloud V2 and Service Cloud V2 together?

Absolutely. Most of our implementations include both. SAP Sales Cloud V2 and Service Cloud V2 share the same underlying platform, so implementing them together is more efficient than doing them separately. Our intelligentfood project is a direct example — Sales Cloud V2 and Service Cloud V2 delivered together in three months.

How long does Service Cloud V2 implementation take?

For mid-market companies (20-150 service agents), a typical implementation takes 6-12 weeks from kickoff to go-live. Complex multi-channel deployments with deep S/4HANA integration, custom portals, and CTI take 3-5 months. The timeline depends on the number of channels, routing complexity, integration depth, and data migration volume. See our step-by-step implementation guide.

Do you support multilingual service operations?

Yes. We configure Service Cloud V2 for multilingual support across German, French, Italian, and English — essential for Swiss companies serving multiple language regions. This includes language-based routing, localised email templates, multilingual knowledge articles, and agent interface localisation.

What does SAP Service Cloud V2 cost?

SAP doesn’t publish fixed pricing. Every deal is negotiated based on agent count, contract length, and bundled products. Service Cloud V2 shares the same licensing model as Sales Cloud V2 — we’ve written a detailed breakdown: SAP Sales Cloud V2 Pricing Guide. Implementation costs come on top, ranging from fixed-fee mid-market projects to larger multi-month enterprise deployments.

How is Service Cloud V2 different from V1 (C4C)?

Fundamentally different architecture. New data model, new APIs, new UI, new extension framework. It’s a reimplementation, not an upgrade. V2 adds ML-based routing, Joule AI capabilities, a modern omnichannel inbox, and native S/4HANA integration patterns. We’ve written a complete comparison: SAP Service Cloud V2 — What’s Different.

What industries do you specialise in?

Manufacturing, biotechnology, food and beverage distribution, pharmaceutical, professional services, and technology. Our strongest vertical experience in DACH is manufacturing and life sciences — companies with complex products, regulated service requirements, and deep SAP ERP integration needs.

Do you compare with Sybit or Adesso?

We work in the same market but with a different model. Sybit and Adesso are large system integrators — hundreds of consultants across many SAP practice areas. We are a focused SAP CX boutique with senior-only teams and in-house BTP development. For mid-market DACH companies that want a named team of experienced consultants, our model delivers better results at lower cost.