You will learn

What tools are, what they do, and how they fit alongside skills and content. By the end, you’ll know when a tool is the right building block and when to reach for something else.

Note: Customer Agent comes with tools out of the box, and you can create fully custom tools from scratch. You’ll find them under Customer Agent > Connectors.

What a tool is

A tool is a specific capability Customer Agent can use during a conversation to fetch data or take an action. Tool permissions determine whether Customer Agent can use it directly, only through a skill, or not at all.

For example, when a shopper asks “Where is my order?”, Customer Agent uses the Get Customer Orders tool to pull that shopper’s order data from Shopify, then responds with the tracking info.

What tools do

Tools fall into 3 categories:

  • Fetch data — Look up an order, search your product catalog, pull a customer’s subscriptions or coupons
  • Take action — Cancel a subscription, apply a discount, create a support ticket (via fully custom tools)
  • Integrate with external systems — Call your OMS, CRM, loyalty platform, or another service with a publicly reachable HTTP endpoint (via fully custom tools)

Tools vs. content

Content is static knowledge Customer Agent uses to answer questions — your shipping policy, product descriptions, FAQs. Tools are capabilities that fetch information or take actions. For example, Search Company Knowledge retrieves answers from your content.

A good test: if the answer is a policy or fact you can write down, add it as content. If the answer depends on who is asking or what they’ve done, or requires current data or an action in another system, use a tool.

Tools vs. skills

Tools give Customer Agent capabilities. Custom skills add instructions for handling a specific workflow. Customer Agent can use permitted tools directly without a skill.

A custom skill can include multiple tools, and a tool can be included in multiple skills. For example, you might use Get Customer Orders in separate custom workflows for returns and order changes.

For a deeper decision framework, see Understanding skills vs. tools.

Tools that come with Customer Agent

Customer Agent comes with tools for common tasks. The tools available depend on your connected integrations and their permissions. Some tools also have configuration inputs when inserted into a skill, such as the number of orders to retrieve. Examples:

Tool

What it does

Get Customer Orders

Fetches customer orders from your connected Shopify, Magento, or WooCommerce store.

Search Shop Catalog

Searches for products from the online store, hosted on Shopify.

Search Company Knowledge

Looks up company knowledge across indexed webpages, uploaded files, and snippets of text.

Get Customer Coupons

Fetches customer coupons for the provided profile ID.

Get Customer Subscriptions

Fetches subscriptions for the provided profile ID.

Get Product Recommendations

Fetches relevant products from a connected catalog, including WooCommerce and Magento 2 stores, based on the shopper’s request, preferences, and available history.

Get Profile

Fetches customer profile data.

Send Event (beta)

Records a custom event on an authenticated shopper’s profile using an existing metric. Configure event properties from the agent’s responses, fixed values, or supported profile fields.

Search Shop Catalog searches Shopify’s storefront catalog. WooCommerce and Magento 2 recommendations use the product recommendation tools available for those integrations; they do not require the Shopify-specific Search Shop Catalog tool.

For Send Event prerequisites, configuration, and testing, see the “Record custom events from a skill” section in Customer Agent profile tools.

Get Customer Orders, Get Customer Coupons, Get Customer Subscriptions, and Get Profile require the shopper to be authenticated before they can retrieve that shopper’s data.

To browse tools, go to Customer Agent > Connectors and open a connector, or open Custom for fully custom tools. You can also view which tools a skill uses by opening that skill’s details.

Control when Customer Agent can use tools

Go to Customer Agent > Connectors and open a connector. Use its permissions dropdown to set a shared rule, or choose Custom to review and set permissions for individual tools. Open Custom to manage fully custom tools.

Always allow: Customer Agent can use the tool directly when it is relevant to a request, without a skill.

Only in skills: Customer Agent can use the tool through a skill that includes it. Use this for actions that need workflow-specific instructions, such as refunds or return labels governed by your policies.

Blocked: Customer Agent cannot use the tool, including through a skill.

Permission changes save as you make them. Review them carefully and test the affected workflows in the Playground. Tool permissions do not replace the integration connection, required integration access, or shopper authentication.

You need permission to edit Customer Agent to change tool permissions. You can also ask Composer to adjust permissions and create a custom skill for the behavior you describe.

Fully custom tools

Creating fully custom tools from scratch lets you connect Customer Agent to your OMS, CRM, loyalty platform, or another service with a publicly reachable HTTP endpoint. Use a fully custom tool when the tools Customer Agent comes with don’t cover what you need. The endpoint must use a public hostname, not an IP address or a private-network address.

Any Customer Agent account can create custom tools. See How to create a tool to build one.

How tools get used

Customer Agent chooses tools based on the shopper’s request and the permissions you configure in Connectors. A tool set to Always allow can be used directly. A tool set to Only in skills must be included in a skill.

The flow inside a single conversation:

  1. Shopper sends a message
  2. Customer Agent identifies the request and any matching custom skill
  3. Customer Agent uses the available tools, guidance, and any applicable skill instructions to decide how to respond
  4. Customer Agent uses the tool to fetch data or take an action
  5. Customer Agent generates a response using what the tool returned

Anatomy of a tool

Every tool has these parts:

  • Name — Short identifier (e.g., Get Customer Orders)
  • Description — Natural-language explanation of what the tool does. This matters: it drives whether Customer Agent decides to use the tool for a given request.
  • Input schema — The parameters the tool takes (e.g., profile_id, order_id)
  • HTTP config (fully custom tools only) — The method, URL, headers, query parameters, and body

A good tool description is specific and unambiguous. Vague descriptions cause Customer Agent to skip a tool when it should use one, or use a tool when it shouldn’t.

Additional resources

Create your own tool or use the built-in profile tools.

Was this article helpful?
Use this form only for article feedback. Learn how to contact support.

Explore more from Klaviyo

Community
Connect with peers, partners, and Klaviyo experts to find inspiration, share insights, and get answers to all of your questions.
Partners
Hire a Klaviyo-certified expert to help you with a specific task, or for ongoing marketing management.
Support

Access support through your account.

Email support (free trial and paid accounts) Available 24/7

Chat/virtual assistance
Availability varies by location and plan type