Gabster in your AI assistant

Gabster has a connector (an MCP server) that links your Gabster account to AI assistants such as Claude and ChatGPT. Once it's connected, you ask your assistant in your own words and it works in Gabster for you. It reads your website, writes up your business, tests your AI Agent with your customers' questions, puts it live on your channels, and then helps you run it day to day: replying to customers, reporting, campaigns, bookings, tickets and your team.

Everything it does happens in your real Gabster account, on your live AI Agent. What you build from the chat shows in your dashboard.

How a request worksCopy Anchor Link

1. You ask in a normal chat, with Gabster turned on. For example: "Build my Gabster agent from our website, test it, and give me a link to try it on my phone."
2. Your assistant picks the Gabster actions it needs. Gabster has close to two hundred, grouped in thirteen areas, from knowledge to bookings.
3. Reading changes nothing. Looking at conversations, numbers, settings or knowledge runs at once and changes nothing. A list of customers with their contact details is the exception: your assistant asks you first.
4. Changes follow the approval rules. Any change that reaches your customers, your team or your money is shown to you first and waits for your OK. See Control and approval.
5. You can take most changes back. Ask "Undo the last change."

What it can and can't doCopy Anchor Link

More, with example requests, is in What you can ask.

Control and approvalCopy Anchor Link

It acts as you, only in your account. It never reaches any organization but yours, and each teammate who connects gets only what their Gabster role allows.

Always shown first and waits for your OK: anything that reaches beyond your AI Agent's setup. That covers messages to customers, campaigns, customers' details, teammates, bookings, tickets, channels and anything that uses one of your plan's slots, such as a web page, a file or a channel.

Setup changes (knowledge, instructions, tone, goals and the website chat's look) are shown first only while customers use your AI Agent, meaning a channel is connected or there was a conversation in the last 30 days, or when the change uses a plan slot. On an AI Agent nobody uses yet, they apply at once and your assistant tells you so. You can undo most of them, but not removed knowledge: add it again instead.

Without a confirm step: asking your live AI Agent a single test question runs at once and uses about 1 credit, and so does the one test message your assistant sends after you add a rule. Your team is alerted to these messages as to a customer's. Saving test questions doesn't change your AI Agent.

When an instruction conflicts with one you already have, your assistant always shows you both and asks which to keep: the new one, the existing one, a merge, or both.

Undo: ask "Undo the last change." It takes back up to 10 changes at a time, made through the connector, and shows you what it will take back first. It can't take back, among others:

• sent replies, campaigns and notifications, closed conversations, and a conversation handed back to your AI Agent;
• a deleted AI Agent or project, removed knowledge (web pages, files or text), and unanswered questions you answered or dismissed;
• deleted customers, tags, folders and departments, removed teammates, and internal notes;
• a disconnected channel (you connect it again yourself);
• cancelled bookings, some moved bookings (the preview says so), and closed calendars or branches;
• a WhatsApp template once it's submitted to Meta, and an update of your products from your store;
• a ticket once it's created (undo only closes it), taken or transferred.

A scheduled campaign is cancelled instead, and a test link is turned off instead.

In Claude, you also choose per tool group. In Gabster's connector settings in Claude, each group of Gabster tools, including undo, can be set to always allow, to ask you first (Needs approval, the default) or to block. Gabster's own approval rules apply on top of this.

Your card goes on Stripe's page only. Your assistant never charges anything in the chat. Anything you pay, you pay on Stripe's own page, through a link you open.

What the AI app sees: only the results of what it runs, kept in that app's chat history. Never passwords or cards. When you ask for a list of customers with their contact details, your assistant asks you first, because those details leave Gabster and go into the chat.

Stop any time. Remove Gabster from your app's connectors, or ask your assistant to disconnect. Your AI Agent stays as it is.

Tests are realCopy Anchor Link

Tests run on your live AI Agent, and what it does in a test really happens. A ticket it opens is resolved as a test afterwards, but still uses 1 credit. The test conversations your assistant runs are deleted afterwards; chats on a test link stay in your inbox. Gabster can't mark a conversation as a test yet, so each test message alerts your team as a customer's message does, and a handoff alerts them too. An alert can't be taken back.

Credits and costsCopy Anchor Link

Saving a new rule uses no credit; your assistant then tests it once on your live AI Agent, which uses about 1 credit. A test of two or more questions shows its cost before it runs. To check your balance, ask "How many credits are left?"

PlansCopy Anchor Link

If your account hasn't started a plan yet, you choose one when you connect. Only the account owner, or a teammate with full access, can choose it; other teammates ask the owner to start one first. In ChatGPT, nothing is sold: you sign in with an account that's already set up, and plans and payments are managed in Claude or in your dashboard.

Where your knowledge livesCopy Anchor Link

Your assistant keeps the knowledge it writes in one Excel workbook per AI Agent, with one topic per row, next to anything your AI Agent already knew. You can see and download it in Knowledge Base, under Documents. To change it, ask your assistant: if you replace the file in the dashboard, your assistant's next publish overwrites your changes. The first time it's published, it uses one of your plan's file slots; later updates replace it in the same slot.

Get startedCopy Anchor Link

1. Connect your assistant.
2. Ask: "Build my Gabster agent. My business: [one line about your business, or your website]. Add what my customers need to know, test it with the questions they really ask, fix anything it can't answer, then give me a link to try it on my phone."
3. When it's ready, put it live.

RelatedCopy Anchor Link

• What you can ask
• Use cases
• Workflows with your other tools