[null,null,["최종 업데이트: 2023-05-17(UTC)"],[[["\u003cp\u003eBuilt-in intents represent common user tasks and information needs, like ordering food or booking appointments, to help build Conversational Actions.\u003c/p\u003e\n"],["\u003cp\u003eWhile most built-in intents are in developer preview, \u003ccode\u003eactions.intent.PLAY_GAME\u003c/code\u003e is generally available.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers creating Conversational Actions should utilize implicit invocations and register for built-in intents, with further guidance available in the Built-in intents guide.\u003c/p\u003e\n"],["\u003cp\u003eApp Actions developers should refer to the App Actions built-in intent reference for relevant information.\u003c/p\u003e\n"]]],[],null,["# Conversational Action built-in intents (Dialogflow)\n\nBuilt-in intents model some of the common ways that users express tasks they're\ntrying to do or information they seek, such as ordering a meal, booking a ride,\nor checking an account balance.\n| **Note:** The `actions.intent.PLAY_GAME` intent is the only built-in intent that is generally available at this time. The other intents listed are available in developer preview.\n\nYou can use these built-in intents to build [Conversational Actions](/assistant/conversational/overview), but we\nare still fine tuning Action discovery and ranking. Note that built-in intents\nintended for App Actions won't work for Conversational Actions and vice versa.\n\n- If you are building Conversational Actions, you should create and test implicit invocations in addition to registering for built-in intents. To learn more about using and deploying these intents, see the [Built-in intents guide](/assistant/df-asdk/discovery/built-in-intents).\n- If you are building App Actions, see the [App Actions built-in intent reference](/assistant/app/reference/built-in-intents) instead."]]
