General
The General tab has three cards: Agent details (Agent ID, Size, Name), Credits limit, and Danger zone (Delete all conversations, Delete AI agent).


- Agent email address - your AI agent’s dedicated
agent@….chatbase-mail.comaddress for receiving and replying to customer emails, with a copy button next to it. - Email configuration - the addresses on your own domains that send and receive email. Click New email address to add one. Existing addresses are listed under their domain, with the domain’s authentication status, each address’s Automatic forwarding status, and edit and delete icons per row.
Helpdesk
The Helpdesk tab has its own sub-navigation. Each entry opens the settings for one part of your Helpdesk:- Email - the address that receives tickets and sends replies, and who is alerted about delivery failures. See Email sub-tab below.
- Members - every AI agent with their teams and availability status. See Assignment algorithm.
- Teams & assignment - create teams and set each team’s auto-assignment rules. See Teams.
- Scheduling - shifts, AI agent schedules, and time off. See Scheduling.
- Triggers - automation rules that run when tickets are created or updated. See Triggers.
- Ticket statuses - add your own statuses alongside the built-in ones. See Helpdesk overview.
- Tags - define the labels your team applies to tickets. See Tags.
- Translation - detect and translate customer messages automatically. See Translation.
- AI draft replies - generate suggested responses that AI agents review before sending. See AI draft replies.
Email sub-tab
The Email sub-tab opens on the Configuration card, which controls which addresses receive and create support tickets:- Helpdesk email address - the address tickets arrive at and replies are sent from. Until you add your own domain, this is the auto-generated Chatbase address (
agent@….chatbase-mail.com), shown with a copy button next to it. Click Configure email settings to add and verify your own domain so replies come from your email instead. Once you have verified addresses, this card lets you pick one or more of them as Helpdesk inboxes. See Email settings. - Deliverability alert contact - the team member who is notified when outgoing Helpdesk emails bounce or fail to deliver. Defaults to None, in which case nobody is alerted.
- Display name - the name recipients see in the “From” field: the responding support associate’s name, or a custom name. See Display name.
- Signature - a rich-text signature appended to every email your Helpdesk sends. See Email signature.
- Preview - a sample email showing how the sender name, address, and footer will look to recipients. See Preview.
Custom fields
The Custom fields tab lists the details your AI agent collects from customers, such as an order number or a company size. Define a field once, then add it to the actions that should ask for it.- Built-in fields: Subject and Description are always available and can’t be edited or archived.
- Your fields: Click New field to add one. Each row shows the field’s name, description, and type, with edit and archive icons.
- Archived: Archived fields are kept for history, and data already collected stays intact.
Custom domains
White label the embed script so it loads from a domain you own instead of a Chatbase URL. See Custom domains.Webhooks
The Webhooks tab POSTs AI agent events and Helpdesk trigger notifications to your own endpoints. It has two cards:Event webhooks
Fires a POST when a subscribed event occurs. Today the available events are custom form submissions, so the Events list is empty until you create and enable at least one custom form Action.- Under Events, tick the form submissions you want to listen for.
- Enter the URL that receives them in Endpoint.
- Click Create webhook.
Webhooks for collected leads and collected data are not configured here. Open the Action itself and use its Destinations section. See Collect Leads.
Helpdesk webhooks
Reusable connections that Helpdesk Triggers POST to when their conditions match. Click Create webhook on the card and set the endpoint URL, optional custom headers, and a request body template (insert ticket fields with{{ticket.*}} placeholders). When you create one, Chatbase shows a signing secret once - every delivery carries an X-Chatbase-Signature header your endpoint can verify with it.
Existing connections are listed on the card, where you can edit or delete them. To actually send a webhook, pick the connection in a trigger’s Send webhook action.

Notifications
From this page, you can configure the notifications you get from the AI agent. You can either opt for getting one email per day that contains all the leads submitted for that day. You can also opt for another email that sends you a daily email with the conversations done on that day. You can add multiple email addresses to receive these emails if needed.