Honorific Mismatch in a Written Complaint
A student drafts a 200-word email to a Seoul language school complaining that a homestay room was not as advertised. The draft opens: "안녕하세요, 저는 학생이에요. 방이 너무 나빠서 화가 났어요. 빨리 고쳐 주세요." The teacher's feedback says the register is wrong for the genre and the recipient. The student must revise while keeping the complaint clear. Constraints: the email must stay under 200 words, must include one specific factual claim (the room lacked a desk promised in the listing), must request a response within five working days, and must not sound so indirect that the request is lost. The student has studied 해요체 and 합쇼체 but is unsure which to use and where.
1. Identify the register problems in the opening and rewrite the first two sentences in an appropriate style.
Read the worked answer
The draft mixes casual evaluation (너무 나빠서, 화가 났어요) with a blunt imperative (빨리 고쳐 주세요) in 해요체. In a first-contact written complaint to an institution, this reads as either too familiar or too demanding, and 화가 났어요 foregrounds the writer's emotion rather than the service failure. A formal written register - 합쇼체 with hedged statements - is expected. Rewrite: "안녕하세요. 귀 기관의 홈스테이 프로그램을 이용한 학생입니다. 안내된 내용과 달리 방에 책상이 없어 불편을 겪었습니다." This keeps the complaint factual, uses the formal 입니다/습니다 ending, and replaces emotional language with a stated inconvenience. Note that the writer should not over-correct into archaic honorifics; standard formal polite style is sufficient. The specific claim (책상이 없어) is retained, satisfying the factual-claim constraint, and the tone invites resolution rather than confrontation.
2. Draft the request-and-deadline sentence and explain how it balances politeness with clarity.
Read the worked answer
Model sentence: "이 문제에 대해 5영업일 이내에 답변해 주시기 바랍니다." This uses the formal request pattern -아/어 주시기 바랍니다, which is polite but unambiguous - it is a request, not a suggestion. The deadline is stated with a specific unit (5영업일, five working days) rather than vaguely (빨리), which satisfies the constraint and prevents the request from being lost in hedging. Politeness is carried by the honorific 시 and the formal 바랍니다 ending; clarity is carried by the explicit timeframe and the noun 답변. A weaker alternative, "가능하시면 연락 주세요," is polite but removes the deadline and makes the request optional. Students should recognise that in Korean institutional writing, indirectness is expressed through honorifics and hedges like 혹시 or -시면, not by deleting the actual request. The best answers keep the request verb visible and sentence-final.
3. The student worries the email sounds rude. Explain one feature that would make it ruder and one that would make it too soft, using the draft's own wording.
Read the worked answer
Rudeness would come from dropping honorifics and using bare imperatives: 빨리 고쳐 주세요 already leans this way, and 고쳐 would be harsher still. Removing 주세요 and the honorific 시 from 주시기 바랍니다 would turn a request into a command. Excessive softness would come from stacking hedges and removing the deadline: "혹시 괜찮으시다면 나중에 연락 주시면 좋겠습니다" apologises for asking and gives no timeframe, so the school can defer indefinitely. The draft's 화가 났어요 sits at the rude end because it makes an emotional demand; too-soft writing would instead bury the desk problem in an apology. The productive middle ground keeps the concrete fact (책상이 없었습니다), one clear request with a timeframe, and formal honorific endings. Students should be able to point to specific morphemes - 시, -습니다, 주시기 바랍니다 - as the levers of register rather than judging tone impressionistically.