Skip to main content

What is this?

Capabilities are buttons the agent may press. Without them, it can only talk. With them, it can also update a contact, hand a chat to a person, or start one of your automations. Each one is a pre-built, tested action — turning one on doesn’t require writing any code, just deciding this agent should have that power.

What can I do here?

Capabilities are grouped into category tabs across the top of the tab — Contacts, Conversation, Knowledge, Catalog, Events, Booking Studio, Automation, Integration Capabilities, External Capabilities, and Channel-specific — each showing how many capabilities it holds. Open a tab, then use the switch beside a capability to turn it on or off.
Handoff to Human, Create Label, Add Note, Get My Orders, and every Integration Capability start off on a new agent — turn them on if you want the agent to have them. The rest start on.
For any enabled capability, you can turn on Require customer confirmation — the agent asks “Shall I go ahead?” before it acts. For Handoff to Human specifically, set the Handoff Assignment: Unassigned, Fixed team member, Round robin, Least busy, or First to claim (the chat is offered to a group and the first person to click Claim lead gets it — you choose who can claim, an optional expiry in minutes, and whether to offer it again or leave it unassigned if nobody claims in time).

How to use it

Turn on only what this agent actually needs

Each capability already comes with its own built-in description telling the model when it’s appropriate — you don’t write that part. You’re deciding which powers this particular agent should have, not how it should use them.

Set Custom Field only writes to fields you’ve already created

The agent can save information a customer shares — a name, an email, a budget — into a custom field. It can only write into fields that already exist for this channel, and it checks the value against that field’s type (a real email for an Email field, an allowed option for a Dropdown). It cannot create a new custom field on its own (it can create a new label when Create Label is on, but not a custom field) — create the field first, then tell the agent when to save into it in Instructions, for example: “If the customer mentions their company name, save it to the matching custom field.”

Create Label, Add Note, and Get My Orders

  • Create Label lets the agent create a new contact label when none of your existing labels fits, then tag the customer with it. It is meant for clear, reusable categories (for example “Wholesale”), not one-off details. It creates at most one new label per conversation, names are 1–30 letters, numbers, or spaces, and an existing label with the same name is reused instead of duplicated. Labels it creates are credited to the channel owner.
  • Add Note lets the agent leave internal notes on the conversation for your team. Customers never see them. Notes are credited to the channel owner.
  • Read Notes lets the agent read the internal notes your team has left on the current conversation, so it can use that context when replying. The agent never quotes a note directly or tells the customer that notes exist — it just uses the information silently. Only notes with the AI can read toggle turned on are visible to the agent; Warning notes are always excluded regardless of the toggle. See Notes for how to mark a note as readable.
  • Get My Orders lets the agent tell a customer the status of their own orders — their latest orders, or one order by number (for example ORD-1042). It can only ever see that customer’s orders, never anyone else’s.

Integration Capabilities

The Integration Capabilities tab holds tools that work through an app you’ve connected. Each card shows a Works with label (for example Works with Shopify, WooCommerce), and the agent only gets the tool while one of those apps is connected on the Integrations page (or, for Google, in Channels → Google). All of them start off. Because they act on a real customer’s data, they only ever use what the platform has proven about the person in the chat:
  • Their phone number, when the conversation is on WhatsApp (the chat runs over that number).
  • Their email address, once they have typed back a one-time code emailed to it. On Instagram, Facebook or Web Chat, a number the customer simply types is only a claim and is not trusted.
If neither is available, the agent asks for the customer’s email and verifies it first.

Verify an email — Send Email Code and Confirm Email Code

These two live in the Contacts tab (they aren’t tied to one app). Send Email Code emails the customer a 6-digit code; Confirm Email Code checks what they type back and, if it matches, saves the address on their contact as the verified email. The code is never shown to the agent, expires after 10 minutes, and is limited to 3 codes per contact per hour (5 wrong tries cancels the code). Turn these on whenever you turn on a tool that looks things up by email — Get My Store Orders on a non-WhatsApp channel, Get My Meetings, Cancel My Meeting, or Get My Appointments.

Stores — Get My Store Orders and Cancel My Store Order

For Shopify and WooCommerce.
  • Get My Store Orders answers “where is my order?” with the customer’s latest orders, or one order by number — status, payment and delivery state, items, total and tracking. It searches every connected store at once and labels each order with its store name. If one number matches orders in two stores, the agent asks which store. Only orders carrying the customer’s proven phone or email are ever shown.
  • Cancel My Store Order cancels the customer’s own order, but only if it is unpaid and not shipped — it never refunds, so a paid order still needs a person. It re-checks that the order belongs to this customer before cancelling. We recommend turning on Require customer confirmation for it.
  • Stores this agent can use — under the capability, tick the stores this agent may look in. Leave all unticked to allow every connected store.

Meetings — Calendly

For a connected Calendly account. Booking directly needs a Calendly plan that includes it; if Calendly refuses, the agent gives the customer the meeting type’s booking page instead. At most 5 bookings per contact per hour. For appointments booked through Booking Studio, use the Booking Studio capabilities instead.

Google Sheets — Look Up Sheet

Lets the agent answer from the business’s own spreadsheet — stock, prices, sizes, delivery charges. The agent passes the key words of the customer’s question and gets back rows that contain every word (up to 10 per tab). Under the capability, Sheets this agent can read:
  1. Choose a sheet and a tab (up to 5 tabs per agent; Add another tab for more).
  2. Tick the columns the AI may share. With none ticked, every column is shown. A column you don’t tick is never returned or matched, so it can’t be guessed at.
Nothing is readable until you choose a tab, and only sheets from this channel’s own connected Google account are offered. The agent answers only from the rows returned and says so when nothing matches.

Google Calendar — Get My Appointments

For businesses that put appointments in Google Calendar and invite the customer by email. The agent can tell a customer when their appointment is — their upcoming events in the next 60 days. Under the capability, tick Calendars this agent can look in (up to 10); nothing is read until you do. It shows only events the customer’s verified email is invited to, and only the title, time, location and video link — never your notes or the other guests. It is read-only: it can’t book, move or cancel. Bookings stay with Booking Studio.
Get My Orders (in the Catalog tab) covers orders placed in the platform’s own storefront. Get My Store Orders covers orders in your connected Shopify and WooCommerce stores.

Trigger Automation

This is the capability people find least obvious, so here’s exactly how it works. The moment you enable Trigger Automation, the agent is handed a live, always-current list of this channel’s active automations — each with its own name and Description — every time a customer messages. This happens automatically. It has nothing to do with what you wrote in Instructions. The agent compares the customer’s message against each automation’s Description and starts whichever one fits. If nothing matches clearly, it’s told not to guess — it simply doesn’t call anything.
Write each automation’s Description like a one-sentence instruction to a new employee — “Use this when the customer asks for a demo” — not just a name. A vague or blank description is the most common reason an agent never uses an automation you expected it to.

What happens once a triggered automation is running

Control passes to the automation completely. If it includes an Ask step — collecting an email, a concern, anything — the agent steps entirely aside and isn’t consulted again until that automation reaches an end (Submitted or Not Submitted). Every reply the customer sends in that window goes to the automation, not the agent. This is deliberate: it’s what keeps a structured flow — say, collecting a name, email, and issue before raising a support ticket — from being interrupted halfway through. The trade-off is that the automation won’t recognize an unrelated question while it’s mid-flow; it treats whatever the customer sends next as the answer to its current question. Keep automations the agent triggers narrow and focused, and always connect the Not Submitted path so a customer who goes off-script isn’t left stuck — see Ask Questions.

Triggering a sequence

Trigger Automation also works for Sequence-type automations — the agent starting one counts as an Assign Sequence action, including the same protection against enrolling a contact who’s already in that sequence twice.

Channel-specific capabilities

Some capabilities only make sense on one channel — for example, Send WhatsApp Flow sends an interactive in-chat form, which WhatsApp supports but Instagram does not. These live in the Channel-specific tab and show a badge — Only on WhatsApp — so it’s clear where they apply. If the agent is not set up to answer on the required channel, a warning appears on the card: “This agent does not answer on WhatsApp, so it will not use this.” To fix it, open the Channels tab and add the channel there.
Channel-specific capabilities are only active during conversations on the matching channel. In conversations on other channels the agent ignores them, even when they are switched on.

Troubleshooting / Technical Notes

  • The agent isn’t using an automation I expected. Check that automation is Active, bound to this agent, and has a specific, clear Description — not the agent’s Instructions.
  • It asked something unrelated to what I just said, mid-conversation. A triggered automation with an Ask step is running and has taken over — see “What happens once a triggered automation is running” above.
  • I can’t find Create Label, Add Note, Handoff to Human, or Get My Orders switched on. They are off by default on a new agent. Open the right category tab and turn them on.
  • The agent created a label I didn’t want. Turn Create Label off, or tell the agent in Instructions when not to create labels. It limits itself to one new label per conversation.
  • The agent never uses an Integration Capability. It only gets the tool while a matching app is connected — Shopify or WooCommerce for the store tools, Calendly for the meeting tools, a connected Google account for Look Up Sheet and Get My Appointments. Connect the app, then try again.
  • The agent says it needs the customer’s email. The lookup needs a proven phone or a verified email. Turn on Send Email Code and Confirm Email Code so the agent can verify the address in the chat.
  • Look Up Sheet or Get My Appointments finds nothing. Open the capability and check you have chosen a tab (or ticked a calendar) — nothing is readable until you do. For appointments, the customer’s verified email must be invited to the event.
  • No capabilities are listed, or the tab looks locked. Save the agent on the General tab first, then reopen it.
Last modified on November 3, 2026