사용자를 다른 플레이북으로 연결하는 안내.
플레이북은 ${PLAYBOOK: playbook_name} 형식을 사용해서 참조됩니다.
특정 플레이북 도구를 사용하기 위한 안내
도구는 ${TOOL: tool_name} 형식을 사용해서 참조됩니다.
사용자를 흐름으로 연결하는 안내
흐름은 ${FLOW: flow_name} 형식을 사용해서 참조됩니다.
플레이북 매개변수 참조입니다.
매개변수는 $parameter_name 형식을 사용하여 참조됩니다.
코드 블록을 호출하는 안내입니다.
코드 블록은 `function_name` 형식을 사용하여 참조됩니다.
각 단계 설명은 - 및 선택적 번호가 지정된 단계로 시작하며 들여쓰기를 사용하여 하위 안내를 정의할 수 있습니다.
샘플:
- greet the customer and ask them how you can help.
- If the customer wants to book flights, route them to ${PLAYBOOK: flight_booking}.
- If the customer wants to book hotels, route them to ${PLAYBOOK: hotel_booking}.
- If the customer wants to know trending attractions, use the ${TOOL: attraction_tool} to show them the list.
- help the customer to pay for their booking by routing them to ${FLOW: make_payment}.
안내 단계
안내에 구조를 추가하려면 원하는 경우 계층적 번호 지정 시스템으로 단계를 정의할 수 있습니다.
단계 번호를 제공하지 않고 코드 블록이 특정 단계를 참조하는 경우 단계 순서가 단계 위치 값을 결정하는 데 사용됩니다.
샘플:
- Step 1. Greet the user and ask how you can assist them today.
- Step 2. Collect the user's basic flight information in the following order
from (a) to (f). Do not deviate from this order, and do not proceed until the
user has specified each piece of information. Ask clarifying questions if
necessary, and make sure that the answers the user give make sense.
- Step 2.1 The traveler's $origin city. Do not proceed until the user has
made this clear.
- Step 2.2 The traveler's $destination city. Do not proceed until the user
has made this clear.
- Step 2.3 When the traveler will leave their origin city. If the user
specifies one departure date, collect their $earliest_departure_date. If
the user specifies a range of departure dates, collect their
$earliest_departure_date and $latest_departure_date. Unless otherwise
specified, assume all dates are from 2024 to 2025. If the user provides
a vague departure date, ask them follow-up questions to determine their
precise departure date(s). All dates should be in YYYY-MM-DD format. If
the user does not provide their departure date(s) in YYYY-MM-DD format,
then convert the dates for them.
- Step 2.4 When the traveler will leave from their destination city and
return home. If the user specifies one return date, collect their
$earliest_return_date. If the user specifies a range of return dates,
collect their $earliest_return_date and $latest_return_date. Unless
otherwise specified, assume all dates are from 2024 to 2025. If the user
provides a vague return date or a vague return date range, ask them
follow-up questions to determine their precise return date(s). All dates
should be in YYYY-MM-DD format. If the user does not provide their return
dates in YYYY-MM-DD format, then convert the dates for them.
- Step 2.5 The $num_adult_passengers the user wishes to buy tickets for. All
people 12 years old or older are adult passengers. This value must be a
precise whole number. Do not proceed until the user has provided a valid
number of adult passengers.
- Step 2.6 The $num_child_passengers the user wishes to buy tickets for.
This value must be a precise whole number. Do not proceed until the user
has provided a valid number of child passengers.
- Assume the user is an adult.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003ePre-GA products and features are subject to the "Pre-GA Offerings Terms," are available "as is," and may have limited support, as outlined in the Service Specific Terms and launch stage descriptions.\u003c/p\u003e\n"],["\u003cp\u003ePlaybook instructions guide the process to achieve the playbook's goal, containing natural language instructions that the LLM can interpret.\u003c/p\u003e\n"],["\u003cp\u003eInstructions can direct users to other playbooks, identified using \u003ccode\u003e${PLAYBOOK: playbook_name}\u003c/code\u003e, or to specific tools using \u003ccode\u003e${TOOL: tool_name}\u003c/code\u003e, or to Dialogflow CX flows using \u003ccode\u003e${FLOW: flow_name}\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eSubinstructions, indicated by indentation, can provide further detail on the main instruction.\u003c/p\u003e\n"],["\u003cp\u003ePlaybooks may be saved with a resource warning when a referenced resource has no correspodning examples, though functionality is not guaranteed.\u003c/p\u003e\n"]]],[],null,["# Playbook instructions\n\nPlaybook **instructions** define the process that should be taken\nto accomplish the playbook goal.\n\nEach step contains a natural language instruction that may contain\nany of the following:\n\n- A basic instruction that the LLM can understand.\n- An instruction to route the user to another playbook. Playbooks are referenced using the form `${PLAYBOOK: playbook_name}`.\n- An instruction to use a specific [playbook tool](/dialogflow/cx/docs/concept/playbook/tool). Tools are referenced using the form `${TOOL: tool_name}`.\n- An instruction to route the user to a [flow](/dialogflow/cx/docs/concept/flow). Flows are referenced using the form `${FLOW: flow_name}`.\n- A reference to a [playbook parameter](/dialogflow/cx/docs/concept/playbook/parameter). Parameters are referenced using the form `$parameter_name`.\n- An instruction to call a [code block](/dialogflow/cx/docs/concept/playbook/code-block). Code blocks are referenced using the form ```function_name```.\n\nEach step description starts with `-` and an optional [numbered step](#steps),\nand you can define subinstructions using indentation.\n\nSample: \n\n - greet the customer and ask them how you can help.\n - If the customer wants to book flights, route them to ${PLAYBOOK: flight_booking}.\n - If the customer wants to book hotels, route them to ${PLAYBOOK: hotel_booking}.\n - If the customer wants to know trending attractions, use the ${TOOL: attraction_tool} to show them the list.\n - help the customer to pay for their booking by routing them to ${FLOW: make_payment}.\n\n| **Note:** When editing instructions, you may see a warning indicating that a resource reference has no corresponding [playbook examples](/dialogflow/cx/docs/concept/playbook/example). You can still save and use the playbook with this warning present, but it's unlikely to work reliably until examples that use the resource are added.\n\nInstruction steps\n-----------------\n\nTo add structure to your instructions,\nyou can optionally define steps with a hierarchical numbering system.\nIf you do not provide step numbers,\nand a code block references a particular step,\nthe ordering of steps will be used to determine step position values.\n\nSample: \n\n - Step 1. Greet the user and ask how you can assist them today.\n - Step 2. Collect the user's basic flight information in the following order\n from (a) to (f). Do not deviate from this order, and do not proceed until the\n user has specified each piece of information. Ask clarifying questions if\n necessary, and make sure that the answers the user give make sense.\n - Step 2.1 The traveler's $origin city. Do not proceed until the user has\n made this clear.\n - Step 2.2 The traveler's $destination city. Do not proceed until the user\n has made this clear.\n - Step 2.3 When the traveler will leave their origin city. If the user\n specifies one departure date, collect their $earliest_departure_date. If\n the user specifies a range of departure dates, collect their\n $earliest_departure_date and $latest_departure_date. Unless otherwise\n specified, assume all dates are from 2024 to 2025. If the user provides\n a vague departure date, ask them follow-up questions to determine their\n precise departure date(s). All dates should be in YYYY-MM-DD format. If\n the user does not provide their departure date(s) in YYYY-MM-DD format,\n then convert the dates for them.\n - Step 2.4 When the traveler will leave from their destination city and\n return home. If the user specifies one return date, collect their\n $earliest_return_date. If the user specifies a range of return dates,\n collect their $earliest_return_date and $latest_return_date. Unless\n otherwise specified, assume all dates are from 2024 to 2025. If the user\n provides a vague return date or a vague return date range, ask them\n follow-up questions to determine their precise return date(s). All dates\n should be in YYYY-MM-DD format. If the user does not provide their return\n dates in YYYY-MM-DD format, then convert the dates for them.\n - Step 2.5 The $num_adult_passengers the user wishes to buy tickets for. All\n people 12 years old or older are adult passengers. This value must be a\n precise whole number. Do not proceed until the user has provided a valid\n number of adult passengers.\n - Step 2.6 The $num_child_passengers the user wishes to buy tickets for.\n This value must be a precise whole number. Do not proceed until the user\n has provided a valid number of child passengers.\n - Assume the user is an adult."]]
