如果您的项目位于 VPC Service Controls (VPC-SC) 边界内，您可能需要添加出站规则，以便从存储预构建组件的外部 Google 托管的 Google Cloud Storage 存储桶中导入最新版本的预构建组件。如果您的 VPC-SC 规则阻止了对 Google 托管的存储桶的出站流量，您在导入时可能会看到一条错误消息，其中包含“在访问 Google Cloud Storage URI ‘gs://gassets-api-ai/prebuilt_components/cx-standard-prebuilt-components/resource-name’ 时被拒绝”字样。
如需启用导入功能，您需要创建一条出站流量规则，以允许访问包含 Google Cloud Storage 存储桶 gs://gassets-api-ai 的外部 Google Cloud 项目。以下属性介绍了启用从 Google 拥有的资源导入所需的资源和操作：
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-18。"],[[["\u003cp\u003ePrebuilt components in Conversational Agents (Dialogflow CX) are ready-to-use flows designed for common tasks and scenarios, accelerating agent development.\u003c/p\u003e\n"],["\u003cp\u003eThese components are categorized into "building blocks" for specific parameter collection and "use cases" for larger user journeys, each utilizing intents and entities.\u003c/p\u003e\n"],["\u003cp\u003ePrebuilt component usage may require configuring flexible webhooks for external service integration.\u003c/p\u003e\n"],["\u003cp\u003eImporting prebuilt components involves navigating the Dialogflow CX console and may require adjusting VPC Service Controls egress rules for projects within a perimeter.\u003c/p\u003e\n"],["\u003cp\u003eThere are prebuilt components for numerous functions, such as the collection of data, like names and addresses, and for carrying out tasks like making payments and checking balances.\u003c/p\u003e\n"]]],[],null,["# Prebuilt components overview\n\nPrebuilt components are a collection of prebuilt flows provided by Conversational Agents (Dialogflow CX)\nfor common tasks and scenarios.\nThey can be used to accelerate development for both new and existing agents.\n\nThere are two types of prebuilt components:\n\n- **Building blocks:** components that collect specific parameters, such as name and address\n- **Use cases:** components that represent larger user journeys, like making a payment, which may make use of one or more building blocks\n\nPrebuilt component flows include\n[intents](/dialogflow/cx/docs/concept/intent)\nand\n[entities](/dialogflow/cx/docs/concept/entity)\nthat are ready to use.\nFor components that require integrations with external services,\nyou need to modify the configuration of the\n[flexible webhooks](/dialogflow/cx/docs/concept/webhook#flexible)\nto integrate with the proper endpoints.\n\nThe following building block components are available:\n\n- [Address collection](/dialogflow/cx/docs/concept/prebuilt-component/address-collection)\n- [Alphanumeric collection](/dialogflow/cx/docs/concept/prebuilt-component/alphanumeric-collection)\n- [Credit card CVV collection](/dialogflow/cx/docs/concept/prebuilt-component/credit-card-cvv-collection)\n- [Credit card expiration date collection](/dialogflow/cx/docs/concept/prebuilt-component/credit-card-expiration-date-collection)\n- [Credit card number collection](/dialogflow/cx/docs/concept/prebuilt-component/credit-card-number-collection)\n- [Date of birth collection](/dialogflow/cx/docs/concept/prebuilt-component/date-of-birth-collection)\n- [Feedback](/dialogflow/cx/docs/concept/prebuilt-component/feedback)\n- [Greeting](/dialogflow/cx/docs/concept/prebuilt-component/greeting)\n- [Name collection](/dialogflow/cx/docs/concept/prebuilt-component/name-collection)\n- [Numeric collection](/dialogflow/cx/docs/concept/prebuilt-component/numeric-collection)\n- [Telephone number collection](/dialogflow/cx/docs/concept/prebuilt-component/telephone-number-collection)\n- [Waiting room](/dialogflow/cx/docs/concept/prebuilt-component/waiting-room)\n- [Zip code collection](/dialogflow/cx/docs/concept/prebuilt-component/zip-code-collection)\n\nThe following use case components are available:\n\n- [Account balance](/dialogflow/cx/docs/concept/prebuilt-component/account-balance)\n- [Account statement](/dialogflow/cx/docs/concept/prebuilt-component/account-statement)\n- [Arrange appointment](/dialogflow/cx/docs/concept/prebuilt-component/arrange-appointment)\n- [Authentication](/dialogflow/cx/docs/concept/prebuilt-component/authentication)\n- [Cancel order](/dialogflow/cx/docs/concept/prebuilt-component/cancel-order)\n- [Credit card enrollment](/dialogflow/cx/docs/concept/prebuilt-component/credit-card-enrollment)\n- [Credit card statement](/dialogflow/cx/docs/concept/prebuilt-component/credit-card-statement)\n- [Disputes](/dialogflow/cx/docs/concept/prebuilt-component/disputes)\n- [Exchange order](/dialogflow/cx/docs/concept/prebuilt-component/exchange-order)\n- [Financial services steering](/dialogflow/cx/docs/concept/prebuilt-component/financial-services-steering)\n- [Lock card](/dialogflow/cx/docs/concept/prebuilt-component/lock-card)\n- [Lost and stolen card](/dialogflow/cx/docs/concept/prebuilt-component/lost-stolen-card)\n- [Make a payment](/dialogflow/cx/docs/concept/prebuilt-component/make-a-payment)\n- [Offers and deals](/dialogflow/cx/docs/concept/prebuilt-component/offers-and-deals)\n- [Open account](/dialogflow/cx/docs/concept/prebuilt-component/open-account)\n- [Order status](/dialogflow/cx/docs/concept/prebuilt-component/order-status)\n- [Retail authentication](/dialogflow/cx/docs/concept/prebuilt-component/authentication-retail)\n- [Retail fraud and dispute](/dialogflow/cx/docs/concept/prebuilt-component/fraud-and-dispute-retail)\n- [Return and refund](/dialogflow/cx/docs/concept/prebuilt-component/return-and-refund)\n- [Telecommunications steering](/dialogflow/cx/docs/concept/prebuilt-component/telecommunications-steering)\n- [Transaction history](/dialogflow/cx/docs/concept/prebuilt-component/transaction-history)\n\nLimitations\n-----------\n\nThe following limitations apply:\n\n- Prebuilt components currently only support English (en).\n\nImport a prebuilt component\n---------------------------\n\n| **Note:** If your project is within a [VPC Service Controls (VPC-SC)](/vpc-service-controls/docs/overview) perimeter, you may need to add an egress rule that authorizes traffic out from the VPC-SC perimeter to the Google-owned Google Cloud Storage bucket where the latest versions of prebuilt components are stored. See VPC Service Controls below for instructions.\n\nTo import a prebuilt component to your project:\n\n1. Go to the [Dialogflow CX console](https://dialogflow.cloud.google.com/cx/projects).\n2. Choose your Google Cloud project.\n3. Select your agent or [create a new agent](/dialogflow/cx/docs/concept/agent#create).\n4. Select the **Manage** tab.\n5. Click **Prebuilt** in the **Manage** panel.\n6. Click the component of interest and click **Import as flow**.\n7. Refer to each component-specific documentation to determine whether additional setup for webhook is needed.\n8. Start testing and customizing.\n\n### VPC Service Controls\n\nIf your project is within a VPC Service Controls (VPC-SC)\n[perimeter](/vpc-service-controls/docs/service-perimeters), you\nmay need to add an egress rule to enable import of the latest versions of\nprebuilt components from the external Google-hosted Google Cloud Storage bucket\nwhere they are stored. If your VPC-SC rules prevent egress to the Google-hosted\nbucket, you may see an error message on import that contains \"Permission denied\nwhile accessing Google Cloud Storage URI 'gs://gassets-api-ai/prebuilt_components/cx-standard-prebuilt-components/\u003cvar translate=\"no\"\u003eresource-name\u003c/var\u003e'\".\n\nTo enable import, you will need to [create an egress rule](/vpc-service-controls/docs/configuring-ingress-egress-policies#updating)\nthat allows access to the external Google Cloud project containing the Google\nCloud Storage bucket `gs://gassets-api-ai`. The following attributes describe the\nresource and operations required to enable import from the Google-owned resource:\n\n- **Resource:** `projects/921279757870`\n- **Service Name:** `storage.googleapis.com`\n- **Method:** `google.storage.objects.get`\n\nCustomizations and settings\n---------------------------\n\nTo customize the component and improve settings:\n\n1. Edit agent responses and [custom entities](/dialogflow/cx/docs/concept/entity-custom) to meet your business needs.\n2. For voice agents, the following speech settings are recommended:\n - [Change STT model](/dialogflow/docs/support/troubleshooting#stt-empty-transcripts) to `latest_short`. To see which features are supported by this model for a particular language, check [Speech-to-Text supported languages](/speech-to-text/docs/speech-to-text-supported-languages).\n - Enable [auto speech adaptation](/dialogflow/cx/docs/concept/speech-adaptation).\n3. If you use a telephony integration that allows parameter values extracted from telephone keypad presses, enable [DTMF for telephony integrations](/dialogflow/cx/docs/concept/parameter#dtmf).\n4. [Test the agent](/dialogflow/cx/docs/concept/console#simulator) using the simulator.\n5. To test your component over voice, it is recommended to use [Dialogflow CX Phone Gateway](/dialogflow/cx/docs/concept/integration/phone-gateway).\n\nHandle exit events\n------------------\n\nUpon successful completion of the task, a prebuilt component will exit with the\nEND_FLOW [symbolic transition target](/dialogflow/cx/docs/concept/handler#symbolic).\n\nWhen a prebuilt component isn't able to complete the task,\nthe following events will be emitted for the calling page\nthat caused the transition to the prebuilt component flow.\nIt is a best practice to handle these events in your agent by creating the\ncorresponding [event handlers](/dialogflow/cx/docs/concept/handler#event) in the calling page.\n\nSee [built-in events](/dialogflow/cx/docs/concept/handler#event-built-in):\n\n- flow-cancelled\n- flow-failed\n- flow-failed-human-escalation\n\nAdditional functionalities\n--------------------------\n\nSome prebuilt components have additional functionality.\nSee the component-specific documentation to check which features\nare implemented for a particular component.\n\n### Repeat functionality\n\nIf the end-user has difficulty interpreting the virtual agent\nor missed hearing an agent response,\nthey can ask for the last prompt to be repeated.\n\nSample utterances:\n\n- *What did you just say?*\n- *Say it again.*\n- *Can you please repeat?*\n- *Pardon.*\n\n### Waiting room functionality\n\nIf the end-user wants to take a minute to get back to the agent\nand does not have an immediate answer to a prompt,\nthey can ask the virtual agent to hold.\nWhen the end-user is ready to continue the conversation,\nthey can tell the agent \"I'm ready\" to resume the conversation. The waiting room\nfeature is enabled in some prebuilt components by calling the\nwaiting room prebuilt component. The waiting room feature can also be\nenabled anywhere in the agent by following the setup instructions as\ndescribed in the\n[waiting room prebuilt component overview](/dialogflow/cx/docs/concept/prebuilt-component/waiting-room).\n\nSample utterances:\n\n- *Please wait.*\n- *Wait a second.*\n- *Please hold, let me check.*\n- *I'm checking, wait.*\n- *I'm ready now.*\n\n### Playback functionality\n\nIf the end user wants to know what the agent has collected so far, they can ask\nthe agent to playback. The agent will then play back the currently captured parameter(s).\n\nSample utterances:\n\n- *Playback.*\n- *Play it back.*\n- *Play that back please?*\n- *Read that back to me.*\n\nCommon intents\n--------------\n\nCommon intents are intents that are used for common behaviors\nin multiple components."]]
