Prebuilt components are a collection of prebuilt flows provided by Dialogflow for common tasks and scenarios. They can be used to accelerate development for both new and existing agents.
There are two types of prebuilt components:
- Building blocks: components that collect specific parameters, such as name and address
- Use cases: components that represent larger user journeys, like making a payment, which may make use of one or more building blocks
Prebuilt component flows include intents and entities that are ready to use. For components that require integrations with external services, you need to modify the configuration of the flexible webhooks to integrate with the proper endpoints.
The following building block components are available:
- Address collection
- Alphanumeric collection
- Credit card CVV collection
- Credit card expiration date collection
- Credit card number collection
- Date of birth collection
- Feedback
- Greeting
- Name collection
- Numeric collection
- Telephone number collection
- Waiting room
- Zip code collection
The following use case components are available:
- Account balance
- Account statement
- Arrange appointment
- Authentication
- Cancel order
- Credit card enrollment
- Credit card statement
- Disputes
- Exchange order
- Financial services steering
- Lock card
- Lost and stolen card
- Make a payment
- Offers and deals
- Open account
- Order status
- Retail authentication
- Retail fraud and dispute
- Return and refund
- Telecommunications steering
- Transaction history
Limitations
The following limitations apply:
- Prebuilt components currently only support English (en).
Import a prebuilt component
To import a prebuilt component to your project:
- Go to the Dialogflow CX Console.
- Choose your Google Cloud project.
- Select your agent or create a new agent.
- Select the Manage tab.
- Click Prebuilt in the Manage panel.
- Click the component of interest and click Import as flow.
- Refer to each component-specific documentation to determine whether additional setup for webhook is needed.
- Start testing and customizing.
VPC Service Controls
If your project is within a VPC Service Controls (VPC-SC) perimeter, you may need to add an egress rule to enable import of the latest versions of prebuilt components from the external Google-hosted Google Cloud Storage bucket where they are stored. If your VPC-SC rules prevent egress to the Google-hosted bucket, you may see an error message on import that contains "Permission denied while accessing Google Cloud Storage URI 'gs://gassets-api-ai/prebuilt_components/cx-standard-prebuilt-components/resource-name'".
To enable import, you will need to create an egress rule
that allows access to the external Google Cloud project containing the Google
Cloud Storage bucket gs://gassets-api-ai. The following attributes describe the
resource and operations required to enable import from the Google-owned resource:
- Resource:
projects/921279757870 - Service Name:
storage.googleapis.com - Method:
google.storage.objects.get
Customizations and settings
To customize the component and improve settings:
- Edit agent responses and custom entities to meet your business needs.
- For voice agents, the following speech settings are recommended:
- Change STT model
to
latest_short. To see which features are supported by this model for a particular language, check Speech-to-Text supported languages. - Enable auto speech adaptation.
- Change STT model
to
- If you use a telephony integration that allows parameter values extracted from telephone keypad presses, enable DTMF for telephony integrations.
- Test the agent using the simulator.
- To test your component over voice, it is recommended to use Dialogflow CX Phone Gateway.
Handle exit events
Upon successful completion of the task, a prebuilt component will exit with the END_FLOW symbolic transition target.
When a prebuilt component isn't able to complete the task, the following events will be emitted for the calling page that caused the transition to the prebuilt component flow. It is a best practice to handle these events in your agent by creating the corresponding event handlers in the calling page.
See built-in events:
- flow-cancelled
- flow-failed
- flow-failed-human-escalation
Additional functionalities
Some prebuilt components have additional functionality. See the component-specific documentation to check which features are implemented for a particular component.
Repeat functionality
If the end-user has difficulty interpreting the virtual agent or missed hearing an agent response, they can ask for the last prompt to be repeated.
Sample utterances:
- What did you just say?
- Say it again.
- Can you please repeat?
- Pardon.
Waiting room functionality
If the end-user wants to take a minute to get back to the agent and does not have an immediate answer to a prompt, they can ask the virtual agent to hold. When the end-user is ready to continue the conversation, they can tell the agent "I'm ready" to resume the conversation. The waiting room feature is enabled in some prebuilt components by calling the waiting room prebuilt component. The waiting room feature can also be enabled anywhere in the agent by following the setup instructions as described in the waiting room prebuilt component overview.
Sample utterances:
- Please wait.
- Wait a second.
- Please hold, let me check.
- I'm checking, wait.
- I'm ready now.
Playback functionality
If the end user wants to know what the agent has collected so far, they can ask the agent to playback. The agent will then play back the currently captured parameter(s).
Sample utterances:
- Playback.
- Play it back.
- Play that back please?
- Read that back to me.
Common intents
Common intents are intents that are used for common behaviors in multiple components.
| Common intent | Description |
|---|---|
| prebuilt_components_confirmation_yes | Positive phrases used to express affirmation, assent or to mark the addition of something emphasizing and amplifying a statement in response to a question or request |
| prebuilt_components_confirmation_no | Negative phrases used to express dissent, denial, or refusal in response to a question or request |
| prebuilt_components_confirmation_done | Phrases used to express that the end-user is done with a task or request |
| prebuilt_components_escalate_human_agent | Phrases used to request that the virtual agent connect the end-user to a human agent |
| prebuilt_components_start_over | Phrases used to request that the entire experience starts over from the beginning |
| prebuilt_components_playback | Specific phrases to request that the currently collected input is played back to the end-user so that the end-user can give confirmation |
| prebuilt_components_replay | Phrases used to request that the previous prompt is said again |
| prebuilt_components_waiting_room | Phrases used to express the need for time to review, find or provide information in response to a question or request |
| prebuilt_components_ready | Phrases used to notify the virtual agent that the end-user would like to continue an action |