Phone: 02-839-7500
Finance · ANYSUPPORT · Internal + Citizen support
Financial Supervisory Service
· ANYSUPPORT Customer Stories / Financial Supervisory Service

CUSTOMER STORY

Removing frequent disconnections and delays for a stable remote supervision environment

Internal supervision work and external e-filing/civil-service use are supported separately by purpose. By limiting the screen-viewing scope and permissions per consultation purpose, sensitive information is better protected while authentication, attachment, and browser issues are resolved on a screen basis.

ClientFinancial Supervisory Service
ProductANYSUPPORT · PC
Use TypeFinance · Internal + Citizen support

BACKGROUND

Background

UsersInternal supervisory staffFinancial institutions and public filersE-government service operators

Challenge

Electronic filings and public inquiries can contain sensitive financial information, so the scope of remote support must be explicit.

Key Objective

Screen and permission policies must be granular enough that support covers technical usage problems only, not the content of the filing itself.

After

  • Better accessibility for e-government services
  • Stronger protection of sensitive information
  • Consultation, resolution and completion records are kept as standard history and used to improve operations

SCENARIO

Remote Scenario

Internal supervisory staff

Identify who the inquiry concerns

Inquiry ID and consent record

Financial institutions and public filers

Separation of internal and external consultations

Session ID and agent record

Financial institutions and public filers

Verify consent and permissions

Issue classification and resolution log

E-government service operators

Filing, public inquiry or business resolution

Approval, handoff and change records

Detailed Scenario

Internal supervision work and external e-filing/civil-service use are supported separately by purpose. By limiting the screen-viewing scope and permissions per consultation purpose, sensitive information is better protected while authentication, attachment, and browser issues are resolved on a screen basis. Screen and permission policies must be granular enough that support covers technical usage problems only, not the content of the filing itself.

OPERATION

Security Controls

Security Controls

  • Network separation between internal and public-facing services
  • Screen restriction on sensitive information
  • Access based on approval and consent
  • Auditing and retention of consultation history

Operational Risks

  • Citizen support and internal support records kept together
  • Insufficient identity verification for public filers
  • The risk of internal network permissions being used for external consultations

PERFORMANCE

Recommended KPIs

Completion rate for citizen-facing servicesBaselines and targets to be set from real operational data
Re-filing rate for public inquiriesBaselines and targets to be set from real operational data
Internal incident handling timeBaselines and targets to be set from real operational data
Compliance rate for personal data and permission controlsBaselines and targets to be set from real operational data

Rollout Phases

1. Design

The internal and citizen-facing 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 the completion rate for citizen-facing services and the re-filing rate for public inquiries, 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