Digital Workplace

The user opened the ticket again. The machine is from 2021. No one had checked it yet!

AI-powered Service Desk, nationwide Field, Asset Management and Governance under a single desk. Taking answers for SLA, XLA, save and avoidance, and goes to the root cause so the ticket stops coming back.

01 Who it's for

For operations where the employee can't stop and the ticket can't escalate.

Hybrid environment, nationally distributed fleet, contractual SLA. ITSM or ESM already running — ServiceNow, Desk Manager or yours. Above 100 users, or fleets with stores, clinics, datacenters and offices across multiple sites.

24x7
support and sustaining for critical operations
+4,500
locations served in nationwide Field
100% Brazil
nationwide coverage with on-site support
02 Diagnosis

Those who reach out are in some or several of these scenarios.

Scenario 01

Day-to-day symptoms

  • The ticket opens, closes, and the same problem comes back the next week
  • The senior analyst is doing L1 work and costing twice as much
  • The vendor became a badge: it counts headcount, no one looks at the operation
  • The vendor's rep hasn't sat at your desk in over a year
Scenario 02

Impact on results

  • Buying machines without checking idle stock. Licenses paid with no real use.
  • IT became a cost line. It left the business agenda.
  • The monthly book arrives generic. You have nothing to defend the budget with.
  • Renewal comes and the IT manager has no savings argument.
Scenario 03

The price of staying as is

  • L1 tickets handled by expensive L2, month after month
  • Root cause never addressed. The same problem becomes a recurring ticket.
  • User experience drops even with the technical SLA on track
  • The competitor already made the transition. You're behind without noticing.
03 Why choose us

Four things that change when the badge becomes Taking.

Assessment with the plane in motion.

What we do. Friday the vendor leaves. Monday the Taking badge starts. In 6 months we map process, database, SLA and XLA KPIs, automations and channels. Assessment built into the contract.

The transition becomes an entry point. Taking works while it learns the house.

Gain sharing 50/50.

What we do. Save and avoidance in the monthly book with calculation memo. In month 6, if the operation reduced positions, the client chooses: discount or more scope within the same budget.

Instead of cutting people, the operation grows in scope without growing the bill.

Root cause, not firefighting.

What we do. When a ticket repeats, we stop. On-site survey. Documentation in the knowledge base. A known error becomes an automatic solution on the next ticket.

The more the operation matures, the fewer tickets appear.

Leadership in the operation.

What we do. Head of Digital Workplace and CEO in the client's direct chain. A critical decision doesn't wait to escalate through the commercial layer.

A structural problem is solved in hours, not in minutes-of-meeting over weeks.

04 What we deliver

A complete structure to operate, sustain and evolve your workplace.

Service Desk at the center. Fronts connected by single governance and shared ITSM.

Support

The layer in direct contact with the user, from the first ticket to the L3 specialist.

Front 01

AI Service Desk

L0 and L1. Multichannel chatbot + IVR (WhatsApp, Teams, Portal, Telegram). FCR on first contact. Agnostic to ITSM and ESM. Handover to a human with guaranteed history.

Front 02

Intelligent Field Services

On-site in +4,500 locations. Dedicated, shared, resident or roaming models. Microcomputing, infra, telecom and CCTV. Backup for absences and vacations.

Front 03

Professional Services

Specialized L3. OS (Windows, Linux, Unix, macOS), database, networks and security, storage and backup, virtualization and cloud (AWS, Azure, Oracle, VMware, Citrix).

Sustaining

The layer running underneath: asset, infra, security and the projects that evolve the environment.

Front 04

Asset Management

Full lifecycle with ESG. ITSM ↔ CMDB integration. The agent opens the ticket already knowing the age of the user's machine.

Front 05

NOC & BOC

NOC monitors infra (link, server, database, cloud). BOC monitors business (ERP, BI, app). End-to-end observability.

Front 06

Cyber Security

Pentest, continuous vulnerability analysis, awareness and SOC + SIEM 24x7 with intelligent event correlation.

Front 07

IT Projects

Legacy retrofit, large-scale rollout, certified cabling, technical survey, maturity assessment and CCTV.

05 Hardware as a Service

HaaS changes the financial equation of your technology fleet.

The AS IS rollout has a defined pace. Each quarter, a clear delivery. Month 6 is not the end of the rollout. It's when the evolution cycle begins.

CAPEX → OPEX the client stops tying up capital in depreciating assets and starts paying a fixed monthly fee per device in use.

01

Always up-to-date fleet

  • Monthly fee per device in use.
  • Upgrade every 24/36 months.
  • Scale on demand, no upfront investment.
02

Protection and continuity

  • Antivirus, backup and configuration included.
  • Spare equipment for emergencies.
  • Preventive and corrective maintenance.
03

Full cycle

  • Logistics and reverse logistics.
  • Disposal with data sanitization and environmental certification.
  • Compliance with environmental and information-security standards.

Centralized management with a real-time inventory dashboard for the contract manager.

Models available in partnership with Acer: Mini PC · Aspire Go 15 · Travelmate · Travelmate P6. Other brands and configurations as needed by the client.

06 How it works

Six months to change your operation.

The AS IS rollout has a defined pace. Each quarter, a clear delivery. Month 6 is not the end of the rollout. It's when the evolution cycle begins.

Month 1 — 3 · Quarter 01

Mapping and plan

Process mapping, database, categorization, priority (Impact × Urgency). ITSM workflow. Improvement plan. SLA and XLA KPIs.

Month 4 — 5 · Bimester 02

Operation live

Team analysis. L1 upskilling. Start of support with FCR. New book. WhatsApp, Teams, Portal channels live. ITSM and chatbot integration. L1 automations.

Month 6 · Gain curve

Measurable result

FCR rises. Effective multichannel. Productivity goes up. Satisfaction goes up. AS IS vs. current operation. Field reduction. 50/50 gain sharing.

07 Governance in two layers

An operation that runs today. And evolves tomorrow.

Two connected desks. Distinct focus.

Block 01 · Present layer

Operational Management

Keeps the operation predictable, with SLA met and crisis contained.

Measures

SLA, capacity, backlog, vendor performance.

Drives

Crisis (T0 to T6), communication, demand, relationship.

Responds

Leadership · Coordination · Ticket Manager · Service Delivery Manager.

Block 02 · Evolution layer

Digital Desk

Increases FCR, reduces recurring tickets and matures the experience.

Monitors

Service quality, gamification, satisfaction.

Builds

Knowledge base, automation, indicators (SLA + XLA + OKR).

Delivers

Executive books and insights for decision-making.

08 Our cases

Where the badge turns into results.

01 / 04
09 FAQ

Questions that may come up before the meeting.

01How does the transition from the current vendor to Taking work?

The operation doesn't stop. On Friday, the current vendor ends; on Monday, the Taking team takes over. In parallel, during the first six months, we run the full assessment: process, database, KPIs, automations and improvement plan. The assessment is built into the contract.

02Does Taking operate with our ITSM tool or require its own?

Taking is tool-agnostic. We operate on ServiceNow, Desk Manager, BMC Remedy or any ITSM/ESM platform already deployed at the client. If you prefer, we run the operation on our stack.

03What's the difference between SLA and XLA, and why measure both?

SLA measures the technical service, response time and ticket resolution. XLA (Experience Level Agreement) measures the end user's experience of the service. The two indicators can diverge: a ticket may close within the contractual deadline and still leave the user dissatisfied. We measure both because solving both is what keeps the operation sustainable.

04What are save and avoidance in the monthly book?

Save is savings generated and delivered to the client (example: consolidating idle licenses). Avoidance is cost avoided (example: a service performed with internal resources within hours, instead of a separately contracted project). Both are reported month by month with a calculation memo.

05How does the 50/50 gain-sharing model work?

Every twelve months, we assess the operation. When Taking reduces positions through automation or efficiency gains, the gain is split equally. The client decides whether to convert it into an invoice discount or an expansion of scope within the same budget.

06What's the scope of Field Services and how do you model it per client?

Coverage is nationwide, with more than 4,500 locations served. The model is designed by context: for retail with distributed stores (Vivara and C&A cases), we work with roaming technicians by region. For mission-critical datacenters (Scala case), a 100% dedicated 24x7 operation.

07How does the HaaS model work and why is it worth it?

HaaS replaces hardware purchase with a fixed monthly fee per device in use. Maintenance, antivirus, backup and configuration are included. Technology renewal happens every 24 or 36 months, with no new investment. In case of failure, there's spare equipment to ensure continuity. At the end of the cycle, disposal is done with certified data sanitization and compliance with environmental standards. We operate in partnership with Acer, with flexibility for other brands as the client needs.

08What's the minimum contract term and why?

The minimum term is 24 to 36 months. Twelve months don't allow the operation to mature: in the first half, Taking is learning the house and deploying improvements; measurable gains come from the twelfth month onward. The assessment built into the contract offsets the extended duration.

Next step

45 minutes of conversation to understand your scenario and design a tailored operational diagnosis.

We reply within one business day to schedule the conversation. No proposal, no charge, no pitch. If it doesn't make sense for Taking, we'll say so in the meeting.

30–45 minutes. No charge, no proposal, no pitch.

Technical and business team from Taking — not a generic SDR.

You leave with a preliminary read of your scenario, and a clear decision to move forward, dig deeper, or stop.