Phone: 02-839-7500
Finance · ANYSUPPORT · Internal support
OK Financial Group
· ANYSUPPORT Customer Stories / OK Financial Group

CUSTOMER STORY

Group-wide support for affiliates' and branches' internal work environments

The central IT support team remotely supports the business applications, security modules, printers and authentication environments used across group affiliates and branches. Permissions and agent groups are separated per affiliate, while shared incidents are contained through group-wide notices and batch fixes.

ClientOK Financial Group
ProductANYSUPPORT · PC
Use TypeFinance · Internal support

BACKGROUND

Background

UsersAffiliate and branch staffGroup IT support teamSecurity operators

Challenge

Systems and responsible teams differ by affiliate and branch, making group-wide support standardization difficult.

Key Objective

Per-affiliate permissions must be preserved while shared incidents and knowledge are pooled at group level.

After

  • Standardized support across group companies
  • Prevention of shared incident spread
  • Consultation, resolution and completion records are kept as standard history and used to improve operations

SCENARIO

Remote Scenario

Affiliate and branch staff

Affiliate and branch inquiries

Inquiry ID and consent record

Group IT support team

Automatic routing to agent groups

Session ID and agent record

Group IT support team

Remote diagnosis

Issue classification and resolution log

Security operators

Shared or individual resolution

Approval, handoff and change records

Detailed Scenario

The central IT support team remotely supports the business applications, security modules, printers and authentication environments used across group affiliates and branches. Permissions and agent groups are separated per affiliate, while shared incidents are contained through group-wide notices and batch fixes. Per-affiliate permissions must be preserved while shared incidents and knowledge are pooled at group level.

OPERATION

Security Controls

Security Controls

  • Prior consent from the customer or user
  • Role-based access permissions for agents
  • Screen restriction and masking on sensitive input fields
  • Auditing of session and resolution history

Operational Risks

  • The habit of connecting without user approval
  • The risk of agents viewing more of the screen than necessary
  • Quick remote fixes that leave no record of root cause or knowledge

PERFORMANCE

Recommended KPIs

Average incident handling timeBaselines and targets to be set from real operational data
First-contact remote resolution rateBaselines and targets to be set from real operational data
On-site visit replacement rateBaselines and targets to be set from real operational data
Time for users to resume workBaselines and targets to be set from real operational data

Rollout Phases

1. Design

The internal support scope, consultation coverage, connection paths and agent groups are defined.

2. Rollout

AnySupport is deployed for PC environments and the operating scenario is validated against the most common inquiry types.

3. Optimization

Consultation data is analyzed around average incident handling time and first-contact remote resolution rate, and the standard resolution playbook is expanded.

Is It Right for Your Company?

We'll propose a remote support model tailored to your industry, users, and security policy.

Blog YouTube Chat
Try Web Viewer Demo
Start Video Support Click →
Try Web Viewer Demo Start Video Support