The AI agent for Slack that does the work your channels ask for

Tag @Glimmer in #cx-escalations and it reads the Zendesk ticket, matches the Sentry issue, files the Jira bug and posts the key in the thread. It answers from Confluence with the source linked, runs jobs on a schedule or a trigger, builds small tools and remembers how each channel works. It runs in your own cloud, on the model you choose.

One agent for the whole channel

Salesforce sells Slackbot as "your personal agent for work". Glimmer works for the team. Anyone in the channel can @mention it, everyone sees the work in the thread, and channel membership decides who can ask. Pick what it does below.

Lantern Pay
Unread messages
Threads
Drafts & sent
Channels
announcements
random
Agents
Glimmer
# people-ops
212
LN
Linh Nguyen11:02 AM
@Glimmer how many days of annual leave does a new hire in Ho Chi Minh City get?
GlimmerAPP11:02 AM

12 days a year for staff on Vietnam contracts, plus 1 day for every 5 years of service.

Singapore and Indonesia staff follow their own policies, on the pages next to this one.

People handbook › Vietnam › LeaveVN offer letter template
🙏 2
LN
Linh Nguyen11:03 AM
Perfect, sending that to our new joiner
Message #people-ops
# finance-ap
9
WJ
Wei Jie Lim10:38 AM
@Glimmer annual renewal from our monitoring vendor. Match it and draft the bill
INV-2026-0311.pdfPDF
GlimmerAPP10:39 AM
  • Read INV-2026-0311.pdf
  • Matched PO-1187 in NetSuite
  • Compared with last year's bill, US$16,430.00
Drafted vendor bill VB-4471 in NetSuite with the PDF attached. The amount is 12% above last year, and PO-1187 covers it.
NetSuiteVendor bill VB-4471
AmountUS$18,400.00
Purchase orderPO-1187
Due31 Dec 2026
Message #finance-ap
# revops
27
GlimmerAPP9:00 AM
Scheduled every Monday at 9:00 AM
14 deals in Proposal with no activity for 14 days, S$612,000 in total.
Daniel Lee5 dealsS$248,000
Siti Rahman4 dealsS$171,000
Kenji Sato3 dealsS$118,000
Arif Hakim2 dealsS$75,000
Total14 dealsS$612,000
Created a follow-up task in HubSpot for each deal, assigned to its owner and due Wednesday.
PN
Priya Nair9:07 AM
Thanks. Daniel, let's go through your five in our 1:1
👍 2
Message #revops
# growth
41
DL
Dewi Lestari8:52 AM
@Glimmer can you build us a page with payout failures by bank for the last 7 days? We check this every morning
GlimmerAPP8:58 AM
Built Payout failures by bank. It reads the payout records every hour, so the page stays current. Ask me here to change it.
Payout failures by bankLast 7 days · updated 9:00 AM
BCA4.8%
Mandiri1.9%
BRI1.2%
BNI0.7%
Vietcombank0.4%
DL
Dewi Lestari9:01 AM
Pinned to the channel. That BCA bar is the one from last night
Message #growth
# product-updates
64
ML
Mei Ling TanWed 4:10 PM
@Glimmer for release notes from now on, put VietQR items first and send the draft to me before it goes to the help centre
GlimmerAPPWed 4:10 PM
Noted. VietQR items go first, and each draft comes to you.
Saved to the memory of #product-updates
GlimmerAPPFri 6:12 PM
Release 4.12 is out. I read the 18 merged pull requests and the 23 tickets in fix version 4.12 . Draft for @Mei Ling Tan, VietQR first:
Release notes 4.12 (draft)
  • New. Merchants in Vietnam can take VietQR payments at checkout.
  • Faster. Payout reports for Indonesia load in under 2 seconds.
  • Fixed. QRIS payouts that stayed pending after a bank timeout.
Message #product-updates

Glimmer answers from Confluence and Google Drive and links the page it used, so anyone can check the answer.It reads the file in the thread, then does the job in NetSuite, Jira, Zendesk or HubSpot with only the access the channel's job needs.A schedule or a trigger starts the job, and the run lands as a thread in the channel the team picks.Ask for a small tool in the channel, such as a dashboard or a form, and Glimmer builds it and keeps it running.Tell it once how the channel works. It saves that to the channel's memory and follows it next time.

A Sentry alert becomes a triaged incident thread

Glimmer watches #inc-payments. When Sentry posts a new error, Glimmer replies in its thread, finds the code change behind it in GitHub, files the bug in Jira, and has a summary and a draft fix waiting when the engineer on call opens Slack. Press a step to open what it found in that system.

Connect the systems your teams already use

Your admin connects each system once in the Glimmer console. Then each agent gets the tools its channel's job needs. The #cx-escalations agent reads Sentry, files bugs in Jira and works in Google Workspace, which has its own switch.

Also connects to HubSpotNetSuiteXeroSalesforceNotionGrafana

It starts work before anyone asks

Schedules and triggers start a job on their own. Each run opens a thread in the channel the team picks, so people reply to it like any other message.

TRIGGER

A Zendesk ticket is tagged “bug”

Glimmer looks for tickets with the same error and the Jira issue that covers them, before the shift lead reads the ticket.

#cx-escalations
New thread with the matches
TRIGGER

A release is published on GitHub

Glimmer drafts the customer release notes from the merged pull requests and the Jira fix version.

#product-updates
Draft for CX to edit
SCHEDULE

The 1st of the month, 8:00 AM

Glimmer lists the vendor bills due this month in NetSuite and flags any amount that changed since the last one.

#finance-ap
Bills due, with changes flagged
TRIGGER

A new Sentry error in the payout service

Glimmer reads the error, finds the change behind it and files the Jira bug, then tags the engineer on call.

#inc-payments
Triage thread for the engineer on call

You decide what it may change

Each agent can use only the tools ticked for it in the console. For a change you flag, such as a customer email or a payment, Glimmer asks first in the thread, with Approve and Deny buttons. Only the person who asked can press them, and the message records who decided and when.

GlimmerAPP3:04 PM
The reply to the 6 merchants on PAY-2291 is ready.

Send this reply to 6 merchants in Zendesk?

Thanks for flagging the stuck QRIS payout. Your funds are safe, and our payments team is fixing the delay. We will update this ticket by 6 PM today.
Only Andre Wijaya can approve this reply

It runs in your cloud and connects out to Slack

Glimmer runs in your own cloud account and connects to Slack on its own, so nothing new opens in your network.

RegionSlack has offered Singapore data residency since 6 Nov 2024. Teams that chose it can run Glimmer in Singapore too.
CredentialsThe agent, its memory and its tool credentials live in your cloud account.
ModelPick Claude, GPT, Gemini, DeepSeek or Qwen, and change it per agent.ClaudeGPTGeminiDeepSeek

How it compares with the AI already in Slack

Slack's own agent, Salesforce's agents and Claude Tag all work in Slack. They differ in who the agent serves, what you have to buy and which systems it can change.

SlackbotAgentforce in SlackClaude TagGlimmer
Built for Each person: "your personal agent for work". Salesforce Salesforce data, and contacts, leads and deals in Slack CRM. Salesforce Anyone in a paired channel who tags @Claude. Claude docs The team in each channel it joins, with the tools that team's job needs.
What you need Slack Business+ at US$18 per user per month, or Enterprise+. Slack pricing Agentforce agents, bought separately, on any paid Slack plan. Slack A Claude Team or Enterprise plan, and it runs Claude only. Channel work is billed by usage. Claude docs The Slack plan you already have. Glints engineers set it up, on Claude, GPT, Gemini, DeepSeek or Qwen.
What it does Finds answers, drafts content, schedules meetings and pulls Salesforce customer context. Salesforce The Employee Agent creates contacts and tracks leads and deals inside Slack. Salesforce Works through the connectors an Owner sets up, in an ephemeral sandbox. Claude docs Answers with sources, makes the change in Jira, Zendesk, Sentry, GitHub, HubSpot and NetSuite, runs on schedules and triggers, and builds small tools, from your own cloud.

Glints engineers set it up as your workspace's own Slack app

We build the first job with your team, in your workspace and your cloud. Your Slack admin approves the install on Slack's own permission screen, which lists everything Glimmer can see and do.

  1. Pick the jobWith the lead who owns it, we agree the channel, the systems it touches and what it may change.
  2. Create your Slack appInside your workspace, from an app manifest, with Socket Mode on and only the bot scopes the job needs.
  3. Connect the systemsYour admin connects Jira, Zendesk, Sentry or NetSuite in the Glimmer console and ticks the tools the job needs.
  4. First job working in a weekIn the team's channel, with the team using it. Then the next team.

Questions from CTOs and Slack admins

What does an AI agent for Slack do?

It is an app in your Slack workspace that a team @mentions in a channel. Glimmer reads the request and the thread, does the job in your other systems, such as filing a Jira bug from a Zendesk ticket or matching a vendor invoice in NetSuite, and reports back in the same thread. It answers questions from Confluence and Google Drive with the source linked.

How is Glimmer different from Slackbot?

Salesforce sells Slackbot as your personal agent for work, on the Business+ and Enterprise+ plans. Glimmer is the channel's agent. Anyone in the channel can @mention it, and everyone sees the work in the thread. It makes changes in Jira, Zendesk, HubSpot, NetSuite and GitHub, runs on the Slack plan you already have, and runs in your own cloud with the model you choose.

Which Slack plan does Glimmer need?

The plan you already have. Glimmer runs as your workspace's own Slack app, so it works on Pro, Business+ and Enterprise+. You do not need to upgrade to Business+ for it.

Can Glimmer start work without someone asking?

Yes. A schedule, such as every Monday at 9:00 AM, or a trigger, such as a new Sentry issue, a Zendesk ticket tagged bug or a published GitHub release, starts a job. Each run opens a thread in the channel the team picks, so people reply to it like any other message.

Where does Glimmer run, and how does it connect to Slack?

In your own cloud account, in the region you pick. It receives messages and button presses over Socket Mode, a WebSocket that the instance opens to Slack, and posts and edits messages through the Slack Web API over HTTPS. Both connections start from your side, so the instance does not need a public URL or an open inbound port. The app asks only for the bot scopes app_mentions:read, channels:history, chat:write, reactions:write, files:read and files:write, and your Slack admin approves them at install. If your workspace uses Slack's Singapore data residency, you can run Glimmer in Singapore too.

Which tools and AI models does Glimmer work with?

Glimmer works inside Jira, Confluence, Zendesk, Sentry, GitHub, HubSpot, NetSuite and Xero through their vendors' MCP servers and APIs, and inside Google Workspace through its workplace connector. Your admin connects each system once in the Glimmer console and ticks the tools each agent may use. It runs on Claude, GPT, Gemini, DeepSeek or Qwen.

How long does it take to set up?

Glints engineers set Glimmer up with you as your workspace's own Slack app, scoped to the channels and tools the first job needs. The first job is working within a week. See how we start.

Give your team's channel an agent that does the work

Bring one job and the channel it lives in. In 20 minutes we will tell you how Glimmer would do it and which systems it connects to.