Charla
for LuumenAI
Read Charla chats and contacts, then draft knowledge base articles for review
Connect Charla and Luumen can read the contacts, conversation exports, and knowledge base of your property on request. Ask what customers keep writing in about, pull the message history behind a recurring issue, and check which categories already cover it. When the answer belongs in the knowledge base, Luumen drafts the article and shows it to you before anything is published.
The Charla toolbox
9 tools: 6 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet ContactReturn one contact in the connected Charla property by UUID.
- ReadGet Knowledge Base ArticleReturn the full content and metadata of one knowledge base article by ID.
- ReadList ContactsReturn one page of contacts for the connected Charla property, ordered by most recently modified.
- ReadList ConversationsExport one page of conversations grouped by contact for the connected Charla property, including message history.
- ReadList Knowledge Base ArticlesReturn one page of knowledge base article summaries for the connected Charla property, newest first.
- ReadList Knowledge Base CategoriesReturn all knowledge base categories available in the connected Charla property.
- WriteCreate Knowledge Base ArticleCreate a knowledge base article. Approval by default
- WriteDelete Knowledge Base ArticlePermanently delete one knowledge base article by ID. Approval by default
- WriteUpdate Knowledge Base ArticleReplace every writable field of an existing knowledge base article. Approval by default
One prompt, start to finish
What a governed Charla run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create knowledge base article, delete knowledge base article, update knowledge base article — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Charla — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
SlackRead the incident thread; post updates and approvals back.
GmailVendor and alert mail as context; replies drafted for review.
Microsoft TeamsRead Teams channels and chats for context, then make membership changes as approved steps.
DiscordRead Discord command permissions and app context, then change them with approvalPut Charla to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.