AI

​

Providers

​

Completion fields

​

Snippets

• Manually - New snippet, title and content.
• Import from URL - libredesk fetches the page, keeps the readable content, and adds it as a snippet you can edit afterwards.
• Suggestions - mined from resolved conversations, see below.

​

Learn from resolved conversations

​

Assistants

​

Settings

​

Handoff

• decides it cannot help, or the customer asks for a human
• hits its max turns
• errors out or times out
• sees someone other than the contact reply on the thread

​

Test and Performance

• Test - send a sample customer message and see the reply it would draft, plus the snippets and articles it used. Nothing is saved or sent.
• Performance - conversations, replies, resolution rate, handoff rate, reopen rate, replies per conversation, and CSAT for that assistant.

​

Tools

{
  "type": "object",
  "properties": {
    "order_id": { "type": "string", "description": "The order ID to look up" }
  },
  "required": ["order_id"]
}

​

Identity headers

​

Require verified contact

• The contact passed the one-time code check in the last 30 minutes.
• The live chat contact was identified with a signed JWT. See Identity verification.
• An agent made the call from copilot or Generate reply.

​

Writing a custom tool

1. Check your own secret first. Configure a header like X-Api-Key on the tool and reject any request that does not carry it. Your endpoint is on the internet; the tool config is the only thing that proves the call came from libredesk.
2. Take the customer’s identity from the headers, never from the arguments. libredesk injects the headers server-side and the model cannot see or change them. Anything in the request body was written by the model, from what the customer typed, so treat it as untrusted input. If the model asks for account_id=99999, look up the account that belongs to the contact in the header and ignore the number.
3. Require X-Libredesk-Contact-Verified for sensitive data. A visitor can claim any email address in chat. On assistant calls that header is true only after the contact proved the address with a one-time code, or was identified with a signed live chat JWT, so require it before returning anything you would not show a stranger, and before anything that changes their account: a cancellation, a refund, an address update.

const apiKey = "your-shared-secret"

func handleBalance(w http.ResponseWriter, r *http.Request) {
	if r.Header.Get("X-Api-Key") != apiKey {
		http.Error(w, "unauthorized", http.StatusUnauthorized)
		return
	}
	if r.Header.Get("X-Libredesk-Contact-Verified") != "true" {
		http.Error(w, "contact not verified", http.StatusForbidden)
		return
	}

	// Identity comes from the header. Nothing in the body decides whose data this is.
	email := r.Header.Get("X-Libredesk-Contact-Email")
	account, ok := lookupByEmail(email)
	if !ok {
		http.Error(w, "no account for this contact", http.StatusNotFound)
		return
	}

	json.NewEncoder(w).Encode(map[string]any{
		"balance":  account.Balance,
		"currency": "INR",
	})
}

​

For your agents

• Copilot - a panel in the conversation sidebar, named Juno. Ask it anything about the conversation. It searches your knowledge base and the contact’s history. Insert its answer into the reply box or add it as a private note.
• Generate reply - describe what you want to say in the reply box and let AI write the reply.
• Editor prompts - fix grammar and spelling, and the other prompts in the reply box AI menu. Add, edit, or delete them under Admin → AI → Editor prompts.
• Summarize with AI - drops an AI summary into the conversation as a private note.
• Suggest tags - suggests tags from your existing tag list.

​

Limits

[ai_agent]
# Number of workers running autonomous AI assistant responses
worker_count = 10
# Maximum number of AI assistant response jobs that can be queued
queue_size = 1000
# Maximum number of tool calls the assistant can make while working on one reply. (1-20)
max_steps = 6
# Conversation messages sent to the model as history. (5-100)
max_history_messages = 30