Rebooking & refund guidance during cancellations/delays
When a cancellation, delay, or weather issue occurs, rebooking and refund questions surge at the same time.
Fast cancellation notices aren't the finish line. Passengers on hold write a post on social media, not to your call center.
When a cancellation, delay, or weather issue occurs, rebooking and refund questions surge at the same time.
Questions about change eligibility and fees repeat.
Tier, accrual, and usage-condition questions flow in repeatedly.
When a cancellation, delay, or weather issue occurs, rebooking and refund questions surge at the same time.
Questions about change eligibility and fees repeat.
Tier, accrual, and usage-condition questions flow in repeatedly.
태풍으로 결항이 뜨는 순간, 콜센터는 한 시간 만에 무너집니다. 재예약과 환불을 묻는 전화가 한꺼번에 몰리고, 정작 오늘 떠나야 하는 승객이 대기음만 듣습니다.
Even when thousands of calls arrive within a minute right after a cancellation notice, it takes them concurrently without letting a single passenger slip into a hold queue.
Different refund rules by fare and alternate-flight priorities during cancellations are guided exactly as the policy document states, without wavering.
Which routes and reasons draw the most questions and complaints is gathered in real time so the ops team can prepare for the next cancellation in advance.
사람 손이 꼭 필요한 통화만 남기면 대기열이 짧아집니다.
상담사는 화가 난 승객 한 명, 보상이 걸린 한 건에 시간을 씁니다.
정책 문서에 답이 이미 적혀 있는 전화입니다. 상담사가 받아도 같은 문장을 읽습니다.
평시 대기열의 상당 부분을 조회·변경 문의가 차지합니다
본인 확인부터 변경 접수까지 한 통화로 마칩니다. 밤에도, 한꺼번에 몰려도
대기가 길어지면 불만은 콜센터가 아니라 SNS로 갑니다. 첫 응답이 늦은 만큼 수습이 커집니다.
결항 통보 직후 콜이 몰리면 연결음만 듣다 끊는 승객이 생깁니다
인입 즉시 받아 대체편 후보와 환불 조건부터 안내합니다
It guides against fare conditions and policy documents, and hands off cases with compensation, exception-approval, or complaint potential to a human consultation.
For booking lookups and changes we first define the integration scope with your booking system, and confirmed changes are processed after identity verification.
Answering in major languages beyond Korean can be configured, with complex cases handed to an agent in that language.
It takes concurrent intake 24 hours a day, handling rebooking and refund guidance first and passing only compensation cases to the queue.
It doesn't start with cancellation response. One flow of routine booking-lookup and change guidance runs first for one to two weeks, stabilizing policy-guidance accuracy and handoff rules. Until then, disruption calls go to existing staff, and once verification ends, it widens into cancellation and delay response.