Speak and Write Language Series
Unit II — 미디어와 공공 생활 (Media and Public Life) · Chapter 9 of 20
9

공식 이메일과 문의Formal Email and Inquiries

Formal writing, honorific address, and respectful requests · Speak and Write Korean: Independent Communication and Advanced Expression

Chapter Objectives

By the end of this chapter, you will be able to:

  1. Use vocabulary for formal correspondence, inquiries, and email conventions to write and interpret a formal Korean email.
  2. Recognize and use the standard structural conventions of a formal Korean email, including greeting, self-identification, purpose statement, body, and closing.
  3. Use the honorific marker -(으)시- productively with common verbs when referring respectfully to the recipient of a formal email, extending the honorific awareness recycled from earlier volumes.
  4. Use honorific address terms and titles appropriately in formal written correspondence, including 귀하, 선생님, and job-title-plus-님 patterns.
  5. Continue using formal -습니다/-습니까 style, and the formal request patterns from Chapter 8 (-아/어 주시겠습니까, -아/어 주시기 바랍니다), now in a written email genre.
  6. Read a short formal email or inquiry and identify its purpose, its request, and its expected response.
  7. Write a complete formal email making an inquiry or a respectful request, using appropriate structure, honorific address, and closing conventions.
  8. Discuss the differences between an everyday polite message to a friend and a formal email to an institution or unfamiliar person.

This chapter continues the formal-register and formal-request systems from Chapters 6 through 8, now applied to written email correspondence. It introduces the honorific marker -(으)시- as a new productive system and introduces formal email structure and honorific address terms as new productive systems.

Opening Scenario

라일라's residence registration renewal from Chapter 8 has hit a snag: the confirmation notice mentioned a missing document, but the notice did not explain exactly which one. Rather than returning to the district office in person, 라일라 decides to write a formal email to ask. Meanwhile, 민준 needs to email his university's administrative office about a certificate he requested weeks ago that still has not arrived, and 지영 is helping both of them polish their emails so that they sound respectful and professional rather than like a message to a friend. As the group compares drafts, 수아 points out that a well-written formal email in Korean follows a predictable structure — and that honorific verb forms referring to the reader are just as important as the words themselves.

  1. You will build vocabulary for formal correspondence, inquiries, and standard email conventions.
  2. You will learn the honorific marker -(으)시- and honorific address terms appropriate to formal writing.
  3. You will learn the structural conventions of a formal Korean email and apply the formal request patterns from Chapter 8 to written correspondence.
어휘 — Core Vocabulary

Core Vocabulary

The following items support this chapter's formal-email-and-inquiry domain. All items below are productive at the level indicated in each table.

KoreanMeaningCategory / Note
귀하you / dear (formal written address term)noun; formal written register only
담당자님the person in charge (honorific address)noun; recycled from Ch. 6–8 + 님
문의inquirynoun; recycled from Ch. 6–8
문의드리다to (humbly) make an inquiryhumble compound verb; formal written register
답장a reply (to a letter or email)noun
회신하다to reply, to respond (formally)action verb; formal register
첨부하다to attach (a file)action verb
첨부 파일attached file, attachmentnoun
보내다to sendaction verb; recycled
받다to receiveaction verb; recycled
문제가 생기다a problem arises / occursexpression; action verb phrase
지연되다to be delayedpassive-form verb; dictionary form 지연되다
확인 부탁드리다to humbly ask (someone) to checkhumble expression; formal written register
양해understanding, consideration (for an inconvenience)noun; formal register
불편을 드리다to cause (someone) inconveniencehumble expression; formal written register
번거롭다to be troublesome, bothersomedescriptive verb; formal register
시간을 내다to make time (for something)expression
안녕하십니까hello (formal written/spoken greeting)formal greeting; recycled and expanded
다름이 아니라the reason I am writing is... (formal email opening)fixed formal expression
다음과 같이as followsfixed formal expression
참고하다to refer to, to take into considerationaction verb; recycled from Ch. 8
알려 주다to let (someone) know, to informexpression; recycled particle + verb
궁금하다to be curious, to wonderdescriptive verb
바쁘시다to be busy (honorific)honorific descriptive verb; -시- applied
계시다to be, to stay (honorific existential verb)honorific verb; irregular honorific form of 있다
드리다to give, to offer (humble)humble verb; irregular humble form of 주다
여쭤보다to ask (humble)humble verb; irregular humble form of 물어보다
보내 드리다to send (to someone, humbly)compound humble verb
감사드리다to express thanks (formally/humbly)humble compound verb; formal closing expression
수고하다to work hard, to take trouble (with something)expression; often in closing lines

Productive lexical load: approximately 29 items above, within the Volume III range of 35–60 once recycled cumulative items are included.

발음 — Pronunciation Focus

Pronunciation Focus

Pronunciation — The honorific marker -(으)시- in connected speech and reading

When the honorific marker -(으)시- attaches to a verb stem ending in a consonant, the linking vowel 으 appears and is fully pronounced, as in 읽으시다 → 읽으세요. When the stem ends in a vowel, 시 attaches directly, as in 가시다 → 가세요. Practice noticing which pattern applies as you read formal email vocabulary such as 계시다, 바쁘시다, and 보내시다.

Also practice the rhythm of longer formal closing lines such as 확인 부탁드립니다 and 감사드립니다, which combine several Sino-Korean syllables. Read them slowly in syllable groups before increasing speed, keeping the batchim of each syllable connected smoothly into the next.

Grammar and Sentence Patterns

This chapter introduces the honorific marker -(으)시- as a new productive system, introduces honorific address terms for formal writing, teaches the standard structure of a formal Korean email, and continues the formal request patterns from Chapter 8 in this new written genre.

1. The Honorific Marker -(으)시-

Grammar — Subject honorification with -(으)시-

The honorific marker -(으)시- attaches to a verb stem to show respect toward the subject of the sentence — that is, toward the person being talked about or written to. In a formal email, the subject is very often the reader, so this marker appears constantly when describing what the recipient has done, is doing, or should do.

  • Consonant-final stem: stem + -으시-, e.g. 받다 → 받으시다.
  • Vowel-final stem: stem + -시-, e.g. 보다 → 보시다.
  • The honorific stem then takes ordinary endings: 받으세요, 받으셨습니다, 받으실 수 있습니다.

Some very common verbs have irregular honorific forms rather than adding -(으)시- to the plain stem: 있다 → 계시다 (to be, honorific), 먹다/마시다 → 드시다 (to eat/drink, honorific), 자다 → 주무시다 (to sleep, honorific). This chapter activates 계시다 productively because of its frequency in formal email closings; the remaining irregular honorific verbs are introduced for recognition only at this stage.

  • 이메일을 받으셨습니까? Did you receive the email? (honorific, respectful of the reader) 받다 + -으시- (honorific) + -었습니까 (past formal question)
  • 바쁘시겠지만 확인해 주시면 감사하겠습니다. I imagine you are busy, but I would appreciate it if you could check. 바쁘다 + -시- (honorific) + -겠지만 (concession); 확인하다 + -아/어 주시면 (conditional formal request)
  • 담당자님께서 자리에 계시면 문의드리고 싶습니다. If the person in charge is available, I would like to make an inquiry. 담당자님 + 께서 (honorific subject particle); 계시다 (honorific existential verb) + -(으)면 (condition)

Note the honorific subject particle 께서, the honorific counterpart of 이/가, used with an honored subject such as 담당자님 or 선생님. It regularly co-occurs with -(으)시- on the verb.

2. Honorific Address Terms in Formal Writing

Grammar — 귀하, 선생님, and title + 님 in formal correspondence

Formal Korean emails typically open with an honorific address term rather than a plain name or a casual greeting. Three common patterns are:

  • 귀하 — a formal written term meaning roughly "you" or "dear," used mainly in official letters, notices, and highly formal correspondence when the writer does not know the reader personally.
  • 선생님 — literally "teacher," but widely used as a respectful address term for any adult whose exact title is unknown, including in formal email.
  • job title + 님 — such as 담당자님 ("the person in charge," honorific) or 교수님 ("professor," honorific), used when the recipient's role is known.

Avoid addressing an unfamiliar recipient by first name alone in a formal email; this reads as overly casual and disrespectful in this register.

3. Formal Email Structure

Building Block — The formal email frame

[greeting: 안녕하십니까/안녕하세요] + [self-identification: 저는 ~입니다] + [purpose statement: 다름이 아니라 ~] + [body: request or inquiry, often with -(으)시-, -아/어 주시겠습니까?, or -아/어 주시기 바랍니다] + [closing: 감사드립니다/수고하십시오]

This frame gives a reliable structure for writing a formal Korean email from opening to closing, regardless of the specific topic.

  • 안녕하십니까? 저는 지난주에 등록증을 신청한 라일라입니다. Hello. I am 라일라, who applied for a registration card last week. formal greeting + self-identification with -입니다
  • 다름이 아니라, 확인 과정에서 어떤 서류가 부족한지 여쭤보고 싶어서 문의드립니다. The reason I am writing is that I would like to ask which document is missing during the confirmation process. 다름이 아니라 (formal opening expression); 여쭤보다 (humble verb) + -고 싶다 (desire, recycled)

4. Continued Formal Requests in Email Closings

Grammar — -아/어 주시겠습니까? and -아/어 주시기 바랍니다 in email bodies and closings

The formal request patterns introduced in Chapter 8 continue to apply directly to email writing. A polite request in the body of an email typically closes with one of these patterns, often followed by a brief thanks line.

  • 필요한 서류를 알려 주시겠습니까? — "Could you let me know the documents I need?"
  • 가능하시면 이번 주 안에 회신해 주시기 바랍니다. — "If possible, please reply within this week."
  • 번거롭게 해 드려 죄송하지만, 확인 부탁드립니다. — "I'm sorry for the trouble, but I would appreciate your checking on this."
Dictionary formEveryday polite -아요/어요Formal email equivalents
알려 주다알려 줘요알려 주시겠습니까? / 알려 주시기 바랍니다
회신하다회신해요회신해 주시겠습니까? / 회신해 주시기 바랍니다
확인하다확인해요확인 부탁드립니다 / 확인해 주시기 바랍니다

You are expected to produce -(으)시- with common verbs, the honorific address terms above, the formal email structure, and the Chapter 8 formal request patterns, all within this chapter's controlled tasks.

Practice — Recognizing honorific forms and email structure

  1. Read the Model Email Exchange and underline every verb marked with -(으)시-.
  2. Label each part of 라일라's email according to the formal email frame (greeting, self-identification, purpose, body, closing).
  3. Find the honorific address term used in each email and explain, in English, why it is appropriate for that recipient.

Model Email Exchange

라일라 writes to the district office about the missing document mentioned in her confirmation notice, and receives a reply.

내용 이해 — Comprehension questions:

  1. What does 라일라 want to know, and what has already been submitted, according to her email?
  2. Identify two honorific verb forms marked with -(으)시- in 라일라's email and explain who is being shown respect.
  3. According to the reply, why was the document confirmation delayed, and what does 라일라 need to do next?
  4. Find the closing line of each email and describe, in English, the tone each conveys.

Guided Practice

  1. Rewrite three sentences from 라일라's email using everyday polite -아요/어요 style, and explain in English why each would be inappropriate in an actual formal email.
  2. Add the honorific marker -(으)시- to five plain verb forms provided by your instructor or textbook partner, adjusting for consonant- and vowel-final stems.
  3. Write two original formal email opening lines using 안녕하십니까 and a self-identification sentence, addressed to two different honorific recipients (e.g., 교수님, 담당자님).
  4. Identify every use of 께서 in the Model Email Exchange and state which honorific verb form it pairs with.

Listening Practice

Ask your instructor, a language partner, or a text-to-speech tool to read the following passage aloud at a measured pace. Listen twice without reading, then complete the tasks below.

안내: 공식 이메일 작성 요령

대학 행정실 관계자에 따르면, 학생들이 이메일로 문의할 때 몇 가지를 지켜 주시면 좋겠다고 밝혔습니다. 먼저 제목에 문의 내용을 간단히 적어 주시고, 본문에서는 본인이 누구인지 먼저 밝혀 주시기 바랍니다. 또한 원하는 답변이 무엇인지 정확히 적어 주셔야 담당자가 빠르게 회신할 수 있습니다. 마지막으로, 격식을 갖춘 인사말과 마무리 인사를 잊지 말아 주시기 바랍니다.

듣기 과제 — Listening task: Listen and answer in English.

질문답
What should students write in the subject line?______
What should students state first in the body of the email?______
Why must students state exactly what response they want?______

Reading Practice

Read the two short formal emails below, then answer the questions that follow.

내용 이해 — Comprehension questions:

  1. Why does 민준 write this email, and how long ago did he originally apply?
  2. What went wrong with 민준's original application, according to the reply?
  3. What does 민준 need to do next, and how long will the new process take?
  4. Identify one honorific verb form and one formal request pattern in each email, and explain in English what each signals about the relationship between the writer and the reader.

Writing Workshop

This chapter's writing task asks you to produce a complete formal email making an inquiry or a respectful request, demonstrating control of formal email structure, honorific address, the honorific marker -(으)시-, and the Chapter 8 formal request patterns.

  1. Choose a formal-email situation. Pick a plausible scenario: following up on a delayed document, asking a professor a question, inquiring about a service, or requesting information from an office.
  2. Draft the greeting and self-identification. Open with 안녕하십니까 or 안녕하세요, then identify yourself with 저는 ~입니다.
  3. State your purpose. Use 다름이 아니라 or a similar formal opening expression to introduce your reason for writing.
  4. Write the body. Explain the situation clearly, using at least one verb marked with -(으)시- referring respectfully to the reader, and make your request using -아/어 주시겠습니까? or -아/어 주시기 바랍니다.
  5. Close politely. End with a thanks line such as 감사드립니다 or 수고하십시오.
  6. Revise. Check your draft against the checklist below.

체크리스트 — Editing checklist:

  • The email follows the formal email frame: greeting, self-identification, purpose, body, closing.
  • An honorific address term (귀하, 선생님, or title + 님) is used appropriately.
  • At least one verb is correctly marked with -(으)시- when referring to the reader.
  • The draft uses -습니다/-ㅂ니다 style consistently throughout, with no everyday polite endings.
  • At least one formal request pattern from Chapter 8 is used correctly.
  • Only Hangeul is used; no romanization appears.
  • Spacing and particles are accurate throughout.
  • No grammar or vocabulary beyond Volume III, Chapters 1–9, appears productively.

Speaking Practice

통제 연습 — Controlled practice: 이메일 소리 내어 읽기

Read the Model Email Exchange aloud at a slow, deliberate pace, maintaining the measured rhythm of formal spoken and written Korean, and paying attention to the pronunciation of -(으)시- forms.

의사소통 과제 — Communicative task: 문의 전화하기

With a partner, role-play a phone call that follows up on a formal email inquiry. One partner plays the person who sent the email, restating the request aloud in formal style; the other plays the staff member, responding with an honorific verb form and a clear next step.

혼자 하는 연습 — Solo alternative

Record yourself reading aloud the formal email you wrote in the Writing Workshop, then record a second version in which you restate the same inquiry as if speaking on the phone to the recipient.

Culture and Communication

Culture in Context — Why formal emails open with self-identification

Formal Korean emails to institutions, offices, and unfamiliar recipients typically open by stating who the writer is and how they are connected to the situation, even when this information appears elsewhere (such as a student ID or application number). This convention helps the recipient quickly place the request in context and reflects the broader Korean pragmatic pattern of establishing relationship and context before making a request.

Culture in Context — Softening a request with an apology phrase

Phrases such as 번거롭게 해 드려 죄송하지만 ("I'm sorry for the trouble, but...") are common in formal Korean requests, even when the request itself is entirely reasonable and the recipient's job is to respond to such inquiries. This softening convention signals awareness of the reader's time and effort rather than genuine apology for wrongdoing.

Institutional Awareness — Email conventions vary by institution and context

The exact greeting, closing, and level of formality in a Korean email can vary depending on the institution, the recipient's role, and the existing relationship between writer and reader. A first-time inquiry to an unfamiliar office typically calls for more formal language than a follow-up message to someone the writer has already corresponded with. Always adjust register to the specific relationship and context.

Common Mistakes to Avoid

Common Mistake — Omitting the honorific marker -(으)시- when referring to the reader

Error: Writing 이메일을 받았습니까? when respectfully asking whether the reader received an email.

Correction: Use the honorific form: 이메일을 받으셨습니까?, adding -(으)시- before the past-tense ending whenever the subject is the honored reader.

Common Mistake — Applying -(으)시- to the writer's own actions

Error: Writing 제가 이메일을 보내셨습니다, incorrectly adding the honorific marker to describe the writer's own action.

Correction: The honorific marker -(으)시- shows respect toward the subject of the sentence, not toward the writer describing their own actions. Use the plain form for the writer's actions: 제가 이메일을 보냈습니다. Reserve -(으)시-, humble verbs like 드리다 and 여쭤보다, and honorific address terms for the recipient and for third parties being respected.

Common Mistake — Opening a formal email with a casual greeting

Error: Opening a formal email to an unfamiliar office with 안녕! or a first-name-only address.

Correction: Open with 안녕하십니까? or 안녕하세요? followed by an honorific address term such as 담당자님 or 귀하, as modeled in this chapter.

Chapter Review

Section A — 어휘 (Vocabulary)

1. Give the meaning of 문의드리다, 회신하다, and 지연되다, and identify which one is a passive-form verb.

Section B — 문법 (Grammar)

1. Add the honorific marker -(으)시- to five verbs of your choice, adjusting correctly for consonant- and vowel-final stems.

2. Write one sentence using an honorific address term and one sentence using a formal request pattern from Chapter 8, both in a formal email context.

3. Explain, in English, why the honorific marker -(으)시- should not be applied to the writer's own actions.

Section C — 독해 이해 (Reading Comprehension)

1. Summarize 민준's email exchange in three to four English sentences, naming the problem and what he must do next.

Section D — 쓰기 (Writing)

1. Write your own formal email following the Writing Workshop steps and checklist.

Section E — 말하기 (Speaking)

1. Perform the follow-up phone call role-play with a partner or record both roles yourself, following the Speaking Practice guidance above.

누적 복습 — Cumulative review

This chapter recycles formal -습니다/-습니까 style, passive-form verb recognition, and the formal request patterns introduced in Chapters 6 through 8, now applied to written email correspondence. It introduces the honorific marker -(으)시-, honorific address terms, and formal email structure as new productive systems.

Practical Performance Task

수행 과제

공식 이메일 쓰고 설명하기 — Writing and Explaining a Formal Email

You will write a complete formal email making an inquiry or a respectful request, then explain your choices aloud, using formal email structure, honorific address, the honorific marker -(으)시-, and a formal request pattern.

  • Reading: Read the Reading Practice email exchange between 민준 and the international office (or similar passages your instructor provides).
  • Written pair: Write a complete formal email following the formal email frame, including a greeting, self-identification, purpose statement, body with at least one honorific verb form, a formal request, and a closing.
  • Spoken restatement: Explain your email's situation and request aloud in formal style, as if speaking to the recipient on the phone.
  • Reflection: Write one to two English sentences identifying one honorific verb form you used and explaining why -(으)시- was appropriate in that sentence.
CriterionWhat is evaluated
Reading comprehensionPurpose, problem, and next steps of each email are correctly identified
Formal email structureWritten email follows the greeting–identification–purpose–body–closing frame
Honorific marker control-(으)시- is used correctly with the reader as subject, and not with the writer's own actions
Honorific addressAn appropriate honorific address term is used for the recipient
Formal request controlAt least one Chapter 8 formal request pattern is used accurately
Register disciplineNo mixing of everyday polite and formal endings within the same email
Register shift (spoken)Spoken restatement is delivered in consistent formal style
Hangeul and spacing accuracyAccurate spelling and level-appropriate spacing throughout, no romanization
Scope disciplineNo structures used productively beyond Volume III, Chapters 1–9

Answer Key

Model Email Exchange — Comprehension

  1. 라일라 wants to know exactly which document is missing from her renewal application; she states that she already submitted both the application form and a copy of her ID.
  2. Sample answer: 받으셨습니까 and 바쁘신 both show respect toward the reader through -(으)시-.
  3. The signature was missing from the application form; 라일라 needs to sign the form, scan it, and send it again as an attachment.
  4. 라일라's closing (감사드립니다) expresses humble thanks for the reader's time; the office's closing (수고하십시오) is a polite, respectful sign-off common in formal institutional replies.

Listening comprehension

  • Students should briefly write the content of their inquiry in the subject line.
  • Students should first state who they are in the body of the email.
  • Because stating the exact response wanted allows the staff member to reply quickly and accurately.

Reading comprehension

  1. 민준 applied for a certificate of enrollment two weeks earlier and still had not received it, even though the stated processing time was five days.
  2. A system error meant that his application was never properly received.
  3. He must resubmit the application form; the office will issue the certificate within two days after that.
  4. Sample answer: 확인해 주시겠습니까? in 민준's email is a polite indirect spoken-style request; 연락해 주시기 바랍니다 in the reply is a formal written request; both show respect toward the person being addressed.

Chapter Review — Section B

1. Sample answer: 가다 → 가시다; 읽다 → 읽으시다; 쓰다 → 쓰시다; 앉다 → 앉으시다; 듣다 → 들으시다.

2. Sample answer: 선생님께서 확인해 주시겠습니까? / 서류를 다시 제출해 주시기 바랍니다.

3. Sample answer: -(으)시- shows respect toward the subject being described, and a writer describing their own actions is not showing respect to themselves; applying it to one's own actions is grammatically and pragmatically incorrect.

Section D — Sample response

안녕하십니까? 저는 지난달에 도서관 카드를 신청한 지영입니다. 다름이 아니라, 카드를 아직 받지 못하여 문의드립니다. 처리 상황을 확인해 주시겠습니까? 바쁘신 중에 시간을 내 주셔서 감사드립니다.

Check that: the email follows the full formal email frame, includes an honorific verb form referring to the reader, uses a Chapter 8 formal request pattern, and stays in -습니다/-ㅂ니다 style throughout.

Looking Ahead

지금 할 수 있는 것 — What you can do now

You can write and interpret a complete formal Korean email, including greeting, self-identification, purpose statement, body, and closing; use the honorific marker -(으)시- correctly when referring respectfully to a reader; use honorific address terms appropriate to formal writing; and make formal requests within written correspondence. These skills prepare you for Chapter 10, where you will bring together the public-information and formal-communication systems from Chapters 6 through 9 in a cumulative Unit II assessment.

Chapter 10종합 과제 2: 공공 정보 활용

Chapter 10 is the Unit II assessment. It consolidates news and public-information reading, institutional procedures, passive-form and causative recognition, and formal email writing from Chapters 6 through 9, without introducing major new productive systems.