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.
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.
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.
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.
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.
On-site Service Desk in Tamboré with NPS 9.0 and 99.5% FCR.
Case 02 · Credit Bureau
Audience
Credit bureau with over 60 years in Brazil. Critical microcomputing for internal IT and business users.
Challenge
ITSM (ServiceNow) under the client's responsibility. 1,200 tickets/month, 800 eligible for L1. 98% contractual SLA. Need for local presence.
Solution
PUC + SPOC with 4 on-site takers (1 senior, 2 mid-level, 1 technical lead). Monday to Friday, 8am to 6pm, in Barueri. Taking operational management. Infra and equipment 100% the client's. Technical SLA and XLA measured month by month.
Result
September/2025: 606 tickets resolved. 65% requests, 35% incidents. FCR 99.5%. SLA 99.1% over a 98% target. NPS 9.0 (August/2025).
446 stores in Brazil sustained with roaming Field by region.
Case 03 · Jewelry Retail
Audience
National leader in jewelry retail. 266 Vivara + 180 Life across the country. Accelerated opening and remodeling cycle.
Challenge
New store operating standardized from day one. Stable connectivity and CCTV across hundreds of malls simultaneously. Speed without compromising quality.
Solution
Roaming Field by region. Connectivity and rack: structured cabling, switches, patch panels, NVR/DVR, primary and secondary links. CCTV and security: WI-FI cameras, alarms, sensors, panic buttons, sirens, electromagnets and buzzers in the vault. Store front: POS, payment terminals, desktops, notebooks, thermal printers, pinpad, scanner, ambient sound.
Result
Deadlines met in accelerated cycles. Total standardization across units. Continuous post-opening sustaining with national scalability.
Field + Asset Management · SCCM + Intune + MDM · Full Cycle · Fashion Retail
C&A Moda
Asset management integrated with the Service Desk: an old machine becomes an avoided ticket.
Case 04 · Fashion Retail
Audience
One of the largest fashion retailers in the country. Expanding fleet: POS, mobile devices, workstations.
Challenge
Assets without control and inconsistent history. Low automation in distribution, support and updates. High service time for stores. Senior L2 doing L1 routine.
Solution
Field + Lifecycle Management. SCCM, Intune and MDM automated. Full asset cycle (purchase, installation, operation, maintenance, update, certified ESG disposal) centralized in the ITSM. L2 reallocated, with three Taking L1s onboarded at the start.
Result
Unified view of the lifecycle. Proactive identification of obsolete machines generating recurring tickets. Reduced service time. Senior doing what needs a senior. The operation grew to other fronts in the following months.
09FAQ
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.
Received. Taking will be in touch within one business day to schedule the conversation.
Your privacy matters
We use cookies to analyze site performance and improve your experience. You can accept or decline the use of analytics cookies at any time. Learn more in our Privacy Policy.