One Ending, Four Jobs: 해요 by Intonation

Here is a fact about 해요체 that saves an enormous amount of memorization and creates one very specific new problem: the same written string 가요 can be a statement ("I'm going"), a question ("are you going?"), a command ("go ahead"), or an invitation ("let's go"). One ending, -아/어요, does all four jobs. What tells them apart is not the grammar — it is intonation and context. This page is about how that works, why English speakers get half of it for free and the other half wrong, and the small toolkit Koreans use to keep the four apart when intonation is invisible.

One string, four speech acts

The formal register 합니다체 gives each sentence type its own ending: 갑니다 (statement), 갑니까? (question), 가십시오 (command), 갑시다 (proposal). Four moods, four forms. 해요체 does the opposite — it collapses all four onto one shape and lets your voice and the situation carry the difference.

Statement — the falling default

Said with a plain falling pitch, -아/어요 is a statement. This is the reading your listener assumes unless something pushes them elsewhere, so it is the safe home base.

Question — the rising one you already know

The question reading is the one English speakers pick up instantly, because English does the same thing. We turn a statement into a yes/no question with rising pitch alone — "You're going↗", "You already ate↗" — no change to the words. Korean 해요체 works identically: keep the words, lift the final pitch, and 가요 becomes 가요?

Because you already have this instinct from English, the question use rarely trips learners up. The problems live in the other two functions — the ones English does not mark with intonation.

Command / request — the surprising one

Here is where English intuition runs out. In English, a command is a different grammatical form: we drop the subject and use the bare verb — "Go," "Sit down," "Wait here." Korean 해요체 has no separate polite imperative built from -아/어요 — the very same 가요 / 앉아요 that means "I go / (someone) sits" also serves as a gentle command, told apart only by context (who is being directed to do what).

Notice these work only because the situation makes the directive obvious: an instructor gesturing at a chair, a host seeing a guest off. Strip the context and 앉아요 could just as well be a statement ("she's sitting down"). This ambiguity is exactly why, in practice, the most common polite command in everyday Korean is not bare -아/어요 at all but the honorific -(으)세요 (앉으세요, 가세요, 드세요) — a form that is unmistakably a request. Reaching for -(으)세요 is itself the first move in a pattern you will see all over this page: when the bare form is ambiguous, Koreans add morphology to nail the mood down.

Proposal — "let's," carried by 같이 and tone

The fourth job is the invitation — English "let's." Again 해요체 has no dedicated "let's" ending in -아/어요; the same 가요 does it, propped up by an inviting tone and, almost always, the adverb 같이 ("together") or an included 우리 ("we").

Without 같이 or 우리, a bare 먹어요 tilts back toward its default statement reading ("I eat / I'm eating"). The proposal reading has to be invited into existence. This is why Korean also offers the dedicated proposal ending -(으)ㄹ까요? (같이 갈까요? "shall we go together?"), which removes all doubt — another instance of adding grammar to disambiguate.

The core problem: prosody carries the meaning

Put the four together and the defining property of 해요체 falls out: the speech act rides on prosody, not on the verb. That is liberating in live conversation, where your voice does the work automatically. But it has a sharp consequence the moment the voice disappears — in a text message, a chat, a note — where a flat 가요 is genuinely ambiguous. A friend texting you just 지금 가요 could mean "I'm on my way," "are you going now?", or "let's go now," and there is no tone to decide.

Native speakers feel this ambiguity too, and they solve it with a small set of disambiguating cues — and copying these cues is one of the highest-value habits a learner can build:

• 같이 / 우리 to force the proposal reading: 같이 가요 reads as "let's go," not "I'm going."
• 좀 ("a bit," softening) to mark a request: 창문 좀 열어요 leans on 좀 to read as "open the window, would you," softening what would otherwise sound like a flat report.
• -나요? / -(으)ㄴ가요? to mark a gentle question in writing, where rising intonation can't be heard: 언제 오나요? ("when are you coming?") is unmistakably a question on the page.

The classic misfire: "let's go" heard as "I'm leaving"

The single most common breakdown for learners comes from the proposal function. You mean "let's go," you say a bare 가요 with no 같이 and no inviting lift, and your listener hears the default statement — "I'm off." You have just announced your own departure instead of inviting them along. The fix is not more politeness; it is the cue.

Common Mistakes

1. Assuming every 해요 sentence needs rising intonation. Beginners who learned "요 = polite question" sometimes lift the pitch on everything, turning plain statements into unintended questions. -아/어요 is a statement by default (falling); raise the pitch only when you actually mean to ask.

2. Making a proposal with no cue. A bare -아/어요 defaults to a statement, so "let's" needs 같이 / 우리 or the -(으)ㄹ까요? ending to be heard as an invitation.

3. Using bare -아/어요 as a command to someone you should defer to. Because -아/어요 as an imperative is direct and a touch familiar, use the honorific -(으)세요 for anyone you'd normally treat with distance; bare 앉아요 to an elder or a customer sounds abrupt.

4. Expecting the written form to carry the tone. In a text, a flat -아/어요 has no intonation to disambiguate it, so a question can read as a statement. Add -나요/-은가요 (or a clear "?") in writing.

Key Takeaways

• One 해요체 ending, -아/어요, serves statement, question, command, and proposal — disambiguated by intonation and context, not by different endings (the mirror image of 합니다체's four forms).
• The question reading (rising pitch) comes free to English speakers; the command and proposal readings do not, because English marks those with different grammar.
• Because meaning rides on prosody, a flat written -아/어요 is genuinely ambiguous — which is why Koreans add cues: 같이/우리 for proposals, 좀 for softened requests, -나요/-은가요 for written questions.
• The go-to polite command is usually the honorific -(으)세요, and the clearest proposal is -(으)ㄹ까요? — both are morphology added precisely to pin down a mood that bare -아/어요 leaves open.