Prebuilt Agents

Prebuilt agents are a collection of agents developed by the Dialogflow team. In the developer console, you can download agents to your account that fit your use case and use them as a base for building a conversational interface for your app, bot, or device.

How to Import Prebuilt Agents

In the developer console, click Prebuilt Agents in the left hand menu. You can search the agents by keywords related to your desired use case. Click on the card of a specific agent for more information and examples. To import a specific agent to your account, click the IMPORT button.

Prebuilt Agents Structure

Prebuilt agents are ready to use for user input classification, that is, transforming a user's natural language into actionable data.

Agent responses are not provided since they either may depend on particular use cases or may need to be retrieved from external sources (from a web service connected to your agent via a webhook or from external APIs or databases connected to your web service). For example, for providing weather forecast for the users, you need to retrieve it from a 3rd party Weather API.

How to Customize Prebuilt Agents

Prebuilt agents are fully customizable, as you’ll have access to edit everything.

Customizing the Small Talk prebuilt agent

The Small Talk prebuilt agent, provides causal conversation responses. This agent can be fully customized to include branding or product specific information and responses. See more info on Small Talk.

Customize Topics Coverage and Classification Model

Prebuilt agents cover the most popular user inputs. You may want to cover additional topics related to the same area or, on the contrary, cover less user questions. For these purposes, you can add or delete intents and entities.

You can copy or move intents and entities between agents, as well as delete intents and entities in bulk. For more information, read the respective sections about batch operations with intents and entities.

Customize Agent’s Responses

Defining Responses in Intents

For simple use cases, you can define agent responses directly in intents. If you use our one-click integrations with some messaging platforms (currently, Actions on Google, Facebook Messenger, Kik, Slack, Telegram, Viber, and Skype), you can define responses not only as text, but as Rich Messages as well.

Defining Responses in Your Fulfillment Service

You can consider creating your web service and connecting it to your agent via webhook. In your web service, you can define responses based on the actionable data received from your agent, perform operations, and retrieve information from external sources (databases or 3rd-party APIs).

If you already have your backend service, you may prefer sending query requests to your agent and defining responses in your business logic. See the list of our SDKs designed for sending query requests and getting responses in different platforms/languages.