시설
“시설” means a facility or building-related installation here, as part of the maintenance context. It is commonly used when talking about facilities that need management or repair, such as those in a building.
관리
“관리” means maintenance or management here. In “시설 관리,” it identifies the work of looking after building facilities, and the same noun is useful for describing an organization or service responsible for upkeep.
요청
“요청” means a request, specifically the maintenance request in this dialogue. It is used for something submitted to another person or service, as in a request sent through an app.
앱이
“앱이” means the app as the subject of the sentence, the thing that froze. The ending marks the app as the thing being described, and this form is useful when reporting what an app did or failed to do.
보내기를
“보내기를” names the sending action or send command as the object of pressing. In this dialogue, it refers to the send control in the app, and it can be used when describing an action selected through a button or menu.
누른
“누른” means pressed here and describes the action before “뒤.” It connects pressing the send command with the later freezing, so it is useful when explaining what happened after an earlier action.
뒤
“뒤” means after in “누른 뒤,” referring to the time following the pressing action. This pattern is useful for placing one event after another in a sequence.
멈췄어
“멈췄어” means froze or stopped here, describing the app becoming unresponsive. It is a casual way to report a problem to someone you are speaking with, especially after an app or device stops responding.
다시
“다시” means again and shows that the action may be repeated. Here it refers to trying the request another time, and it is commonly used before an action that is being repeated.
시도하기
“시도하기” means trying, presented as an action before “전에.” In “다시 시도하기 전에,” it identifies the action that should not happen until another check is completed.
전에
“전에” means before and sets the earlier time for the check in relation to trying again. It commonly follows an action expression to say that something should happen before that action.
네
“네” means your and refers to the listener’s history. It is used here to identify something belonging to the person being addressed, especially in direct conversation.
기록에
“기록에” means in your history or record, the place where the request might appear. The ending marks the location, and this pattern is useful when checking whether information appears in a record or list.
요청이
“요청이” means the request as the subject of “나타나는지.” It identifies the request as the thing whose appearance is being checked, a useful pattern when asking whether an item appears somewhere.
나타나는지
“나타나는지” means whether it appears here. It presents the request’s appearance as something to check, and this form is useful inside an indirect yes-or-no question.
확인해
“확인해” means check or confirm in “확인해 봐.” It asks the listener to inspect the history or app, and it is commonly used when verifying information or a current status.
봐
“봐” adds the idea of trying or seeing in “확인해 봐.” Together with the preceding action, it gives a practical suggestion to try checking something, which is useful when giving informal advice.
아직
“아직” means still here, showing that the loading has not finished. It is useful for reporting that a situation continues at the time of speaking.
로딩
“로딩” means loading, referring to the app’s ongoing process. It is a common technology term used when a screen or service has not finished processing.
중이라서
“중이라서” means because it is in progress, and in “로딩 중이라서” it gives the reason for not knowing whether the message was sent. This pattern is useful when an ongoing process explains a problem or delay.
메시지가
“메시지가” means the message as the subject of the question about transmission. It identifies the message as the thing whose status is uncertain, useful when discussing whether information was sent.
전송됐는지
“전송됐는지” means whether it was sent or transmitted here. It places the message’s delivery status inside an indirect question, useful when the speaker cannot confirm whether a message went through.
알
“알” means know or tell as part of “알 수가 없어.” It refers to knowing the result of the message’s transmission, and this form commonly appears in expressions about whether someone can know something.
수가
“수가” is the possibility or ability part of “알 수가 없어.” Together with the surrounding words, it helps express that the speaker has no way to know, a useful pattern for describing inability.
없어
“없어” means there is not, and in “알 수가 없어” it gives the meaning cannot tell or cannot know. This expression is useful when the available information is insufficient to determine an answer.
문제를
“문제를” means the problem as the object of explaining. It identifies what should be explained clearly, and this object-marked form is useful when describing an issue to another person.
분명하게
“분명하게” means clearly and describes how the problem should be explained. It is useful when asking someone to make information easy to understand.
설명할
“설명할” refers to the action of explaining in “설명할 수 있게.” It is linked to an ability expression and identifies the action that should be made possible.
수
“수” expresses ability or possibility in “설명할 수 있게.” It is used with an action to say that someone can do it, and here it appears in a purpose expression.
있게
“있게” means so that it is possible to do something in “설명할 수 있게.” It connects the screenshot to the purpose of making a clear explanation possible.
화면을
“화면을” means the screen as the object of capturing. It identifies what should be saved, and this form is useful when describing an action performed on a device display.
캡처해
“캡처해” means capture the screen in this dialogue. It introduces the action of making a screenshot, useful when preserving visible information for later explanation.
둬
“둬” means leave or keep it in place after the capture action. In “캡처해 둬,” it adds the idea of saving the result for later use, which is useful when preparing evidence or information in advance.
같은
“같은” means same and modifies the request in “같은 요청.” It shows that the speaker does not want to repeat the identical request, and it is commonly placed before the noun being compared.
요청을
“요청을” means the request as the object of sending. Here it refers to the same maintenance request, and this form is useful when describing what is submitted or sent.
보내고
“보내고” means send and connects that action to the following expression of desire. In “보내고 싶지는 않아,” it identifies the action the speaker does not want to repeat.
싶지는
“싶지는” expresses wanting to, with the ending adding contrastive focus in “보내고 싶지는 않아.” It helps present the speaker’s reluctance about sending the same request again, a useful pattern for contrasting a desire with another possibility.
않아
“않아” negates the desire expressed before it in “싶지는 않아.” It makes the meaning that the speaker does not want to send the request, and this casual ending is suitable for conversation between familiar speakers.
잠깐
“잠깐” means briefly or for a short time. Here it limits how long the listener should wait, and it is commonly used when asking someone to pause for a moment.
기다렸다가
“기다렸다가” means wait and then, showing that waiting comes before the next action. This form is useful for giving a sequence in which one action is completed before another begins.
새
“새” means new and modifies the request in “새 요청.” It distinguishes a newly started request from the earlier one, and it is commonly placed directly before a noun.
시작하기
“시작하기” means starting, presented as an action before “전에.” In “새 요청을 시작하기 전에,” it identifies the action that should wait until the app has been checked.
앱
“앱” means app here, referring to the maintenance request application. It is a common technology noun and can be used when discussing checking, opening, or using an application.
계속
“계속” means continuously or still, showing that the freezing continues. It is useful for describing a problem that has not stopped or a state that keeps occurring.
멈추면
“멈추면” means if or when it freezes or stops. In “계속 멈추면,” it introduces the condition for contacting maintenance, and this pattern is useful for discussing what to do if a problem continues.
건물
“건물” means building here, specifying the building connected with the maintenance team. It is commonly used to identify a physical building and the services associated with it.
관리팀에
“관리팀에” means to the maintenance team, the recipient of the contact. The ending marks the team as the destination of communication, useful when saying whom to contact.
직접
“직접” means directly, indicating that the speaker should contact the maintenance team without relying on the app. It is useful when emphasizing immediate communication with the responsible person or team.
연락해야
“연락해야” means need to or should contact in “연락해야 할까?” It presents contacting the team as the action under consideration, and the pattern is useful when discussing an obligation or recommended next step.
할까
“할까” asks should I or shall I in “연락해야 할까?” It turns the proposed action into a question about what the speaker ought to do, useful when asking another person for advice.
연락해서
“연락해서” means contact and then, linking contact with the following explanation. It presents contacting the maintenance team as the step that should come before explaining the app problem.
작동하지
“작동하지” means not work as part of “작동하지 않을 수도.” It describes the app’s failure to function and is useful when reporting that a device, app, or system is not operating normally.
않을
“않을” contributes the meaning not work in “작동하지 않을 수도.” It presents the possible non-working state before the expression of possibility, useful when describing a condition that may not hold.
수도
“수도” expresses might or could in “작동하지 않을 수도.” It presents the app’s failure as a possibility rather than a certain fact, useful when explaining an uncertain cause or status.
있다고
“있다고” introduces the content being explained in “작동하지 않을 수도 있다고 설명해.” Here it reports that the app may not be working, and this pattern is useful when conveying a statement or possibility to someone else.
설명해
“설명해” means explain and gives the instruction to describe the app’s possible failure. It is useful when telling someone to communicate a problem or situation clearly to another person.
무슨
“무슨” means what or what kind of in “무슨 일이 있었는지.” It asks about the nature of the event, and this form is commonly placed before a noun when identifying an unknown situation.
일이
“일이” means the thing or event as the subject in “무슨 일이 있었는지.” It refers broadly to what happened, a useful expression when asking about an unclear incident.
있었는지
“있었는지” means what happened here as part of the indirect question “무슨 일이 있었는지.” It places the past event inside the sentence about knowing, useful when trying to understand an earlier problem.
때까지
“때까지” means until and sets the endpoint for keeping the screen open. It is useful when an action should continue up to a specified time or event.
열어
“열어” means open and is linked to “둘” in “열어 둘.” It describes opening the screen and keeping it that way, useful when preserving the current display for later inspection.
둘
“둘” means leave or keep in “열어 둘.” Together with the preceding action, it expresses maintaining the screen in an open state, useful when something needs to remain available.
있어
“있어” expresses can or be able to in “둘 수 있어.” It completes the ability expression, showing that the speaker is able to keep the screen open until the situation is understood.
그러면
“그러면” means then or in that case and connects the proposed action with its result. Here it introduces what the maintenance team can do after the screenshot is kept available.
관리팀에서
“관리팀에서” identifies the maintenance team as the group carrying out the next action. The ending marks the team as the acting side in the sentence, useful when describing who will inspect or use something.
화면
“화면” means screen here and forms the basis of the screenshot expression. It is a common technology word for the visible display of an app or device.
캡처를
“캡처를” means the screenshot as the object used by the maintenance team. It identifies the saved image as the information they will examine to understand the problem.
보고
“보고” means looking at or seeing and connects that action with understanding what went wrong. In this dialogue, it explains how the maintenance team can use the screenshot, and the pattern is useful for linking observation to a later result.
무엇이
“무엇이” means what as the subject of the indirect question. It asks which thing or part was wrong, useful when identifying an unknown cause or problem.
잘못됐는지
“잘못됐는지” means what went wrong or what was wrong here. It places the problem inside an indirect question after looking at the screenshot, useful when investigating the cause of a failure.