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.
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.
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.
| Daniel Lee | 5 deals | S$248,000 |
| Siti Rahman | 4 deals | S$171,000 |
| Kenji Sato | 3 deals | S$118,000 |
| Arif Hakim | 2 deals | S$75,000 |
| Total | 14 deals | S$612,000 |
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.
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.
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.
The agent can use the tools ticked below. Turn this off to block them all at once. Built-in tools above keep working. Each workplace below has its own switch. Changes apply to new conversations only.
It can do what is ticked below. Turn this off to stop all its work in Google Workspace.
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.
Glimmer looks for tickets with the same error and the Jira issue that covers them, before the shift lead reads the ticket.
Glimmer drafts the customer release notes from the merged pull requests and the Jira fix version.
Glimmer lists the vendor bills due this month in NetSuite and flags any amount that changed since the last one.
Glimmer reads the error, finds the change behind it and files the Jira bug, then tags the engineer on call.
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.
Glimmer runs in your own cloud account and connects to Slack on its own, so nothing new opens in your network.
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.
| Slackbot | Agentforce in Slack | Claude Tag | ||
|---|---|---|---|---|
| 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. |
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.
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.
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.
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.
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.
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.
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.
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.
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.