Answers from your own docs, with the source linked
It reads your guides in Google Docs and Notion and your sheets. A driver asks what to do when a shop turns away dented cartons and gets the steps from the returns guide.
Glimmer joins your Telegram group as your company's own bot and finishes the job in the topic where it belongs. On a trading desk it posts the 18:00 reconciliation with every mismatch listed. When a driver posts a delivery photo, it adds the delivery to the sheet and flags missing items. When an alert fires, it tells your engineers in plain words which change caused it. Tag it in any topic and it answers from your own documents, with the source linked.
In the Recon topic of the Meridian Digital desk group, the Meridian Ops bot posts the 18:00 reconciliation: 3 breaks, USDT 42,150 unmatched, with a table of the breaks and the file. A trader then asks about one break and the bot answers with the exchange fill.
In the Deliveries topic of the Kirana Haul ops group, Budi, a driver, posts a photo of the signed delivery note for DO-2231 and tags the bot. Glimmer reads the photo, adds row 418 to the delivery sheet in Google Sheets and flags 2 items the customer, Toko Sari Rasa, did not receive: 4 cartons of cooking oil and 5 cases of instant noodles. Dewi from the ops team replies that she is calling the customer.
In the Incidents topic of the Tessel Labs engineering group, a Grafana alert fires and the Tessel Ops bot posts on its own: about 1 in 12 customers cannot pay since 14:20. The likely cause is Arif's 14:18 change to the checkout page, number 482 in GitHub, which renamed a field the payment provider still sends under its old name. Arif replies that he is undoing it, and at 14:29 the bot posts that checkout is back to normal.
Pick a group to see the job Glimmer finishes there.
"Much of crypto's business still runs on consumer messaging apps like Telegram."The Tie, 12 Nov 2025
64.9×
Blockchain services firms are 64.9 times as likely as the base population to put Telegram on their website. That counts public channels across 29,961 companies.
BloomberryIn your topics
Each team tags the bot in its own topic. Glimmer reads your systems, does the job inside them and posts the result where the question was asked.
It reads your guides in Google Docs and Notion and your sheets. A driver asks what to do when a shop turns away dented cartons and gets the steps from the returns guide.
After an incident, Kai asks for a ticket. Glimmer opens it in Jira with the cause, the change behind it and the timeline, and assigns it.
At 21:00 Glimmer checks the delivery sheet and posts the deliveries still missing a photo, tagging each driver.
Ask for a tool in the topic and use it the same day. Glimmer builds it, hosts it and keeps its data fresh.
Glimmer keeps what a team tells it, such as who looks after which part of the product, and uses it the next time it is asked.
Topics
On a trading desk, Glimmer watches the exchanges, custody platform, Grafana and GitHub through the night and posts each alert to the topic that owns it. At 06:00 it reconciles, and at 07:30 it posts one report for the desk. Click any topic to read it.
☀️ Morning report, Fri 21 Nov
| Desk | Overnight |
|---|---|
| Incidents | 2 alerts, both cleared. Exchange 2 withdrawals queued 40 min. Orders slow for 6 min after the 03:50 update. |
| Treasury | Ops hot wallet USDC 18,400, under the 20,000 top-up line. |
| Recon | 2 breaks, USDT 17,150. 1,412 of 1,414 trades match. |
| BD | 3 counterparty replies we owe: Northline, Arcadia, Tidewater. |
Today: Northline call at 11:00. Friday USDC cut-off is 16:00.
| Ref | Break | USDT |
|---|---|---|
| OTC-4502 | Fill missing from blotter | 12,150 |
| CUS-0915 | Withdrawal pending | 5,000 |
3 alerts and the recon, in one message at 07:30.
Telegram does not show a bot what other bots post, so Glimmer takes each alert from the system that raised it. (Bot FAQ)
Press Rerun recon above. Glimmer updates the report and marks it edited, so the topic gets one message instead of a stream.
Telegram bots can send tables inside a message, so the report reads in Telegram without opening a file. (Telegram, 11 Jun 2026)
Your own bot
You add Glimmer to the groups you choose, the same way you would add any member. Telegram marks it as a bot in the member list, so everyone in the group can see what it is.
Each agent is its own Telegram bot, separate from any staff member's account. Its keys stay in your own cloud account.
In a group, Glimmer gets the messages that tag it and the replies to its own messages. It does not get the rest of the chat, and it works only in the groups you switch on for it.
Telegram does not show a bot what other bots post (Bot FAQ), so Glimmer takes alerts from the system that raised them.
Connect your systems
Google Workspace is one card with its own switch and a grid of Read and Change per app. Exchanges, custody, Grafana, GitHub, Notion, HubSpot and Xero each get a row of actions you tick. Click Connected systems in the sidebar to see the list.
Agents / desk-ops
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.
The systems and databases your agents can use, such as your helpdesk or CRM.
| System | Status | Set up by | Agent |
|---|---|---|---|
Exchange balancesCustom connector | Connected | Priya Nair | desk-ops |
CustodyCustom connector | Connected | Priya Nair | desk-ops |
| Connected | Wei Ming Tan | desk-ops | |
| Connected | Wei Ming Tan | desk-ops | |
| Connected | Priya Nair | desk-ops | |
HubSpotSign in with the vendor's account | Connected | Marcus Lee | desk-ops |
XeroSign in with the vendor's account | Connected | Aisyah Rahman | desk-ops |
| Setup incomplete | Aisyah Rahman | desk-ops |
Glimmer's access to your exchanges is view-only unless you decide otherwise. It does not hold private keys, sign transactions or place trades.
Treasury's agent reaches custody and the blotter. The engineering agent reaches Grafana and GitHub. Each sees only what its card ticks.
Any exchange, custody platform or in-house system can connect. Glints engineers set it up with you.
Staying in control
For a call you mark, Glimmer posts the exact request with Approve and Deny under it. Press one.
October contributor payouts: 14 transfers, USDC 86,400
From the ops hot wallet, USDC on Ethereum. 13 addresses match the address book. Tomás Ruiz's changed to 0x7a3f…c41e, flagged in the batch note.
What else is out there
The search turns up three kinds of tool: writing help inside Telegram, Telegram CRMs and customer-facing bot builders. Glimmer works in your staff groups and does the back-office job.
In Telegram itself
Fixes grammar, rewrites and translates the message you are typing, in the message bar.
Telegram, 31 Mar 2026Telegram CRMs
Track deals and partnerships across your Telegram chats, with AI on top, for crypto teams and funds.
Crypto Daily, 9 Jul 2026Bot builders
Answer customers who message your bot. Make keeps one history per user chat; SleekFlow puts Telegram in a shared customer inbox.
Make · SleekFlowYour staff groups
Your cloud, your model
The bot's keys, the files Glimmer reads, its memory and its AI model calls stay in your account. Telegram carries the group messages.
Glimmer, its keys and its data live in your own cloud account.
Glimmer reads balances and fills on your exchanges. It does not hold private keys, sign transactions or place trades. Your signers sign in custody.
Telegram keeps group chats on its own servers, encrypted between your app and Telegram. Only 1:1 secret chats are end-to-end encrypted. The group gets the summary and the breaks. The full records stay in your systems, where Glimmer reads them.
Telegram FAQBuilt with Glints engineers
Glints engineers build it with your team as a build partner. Glimmer is the AI teammate Glints itself runs on, across about 300 staff.
One job your team does every day, such as the 18:00 recon or logging delivery photos, and the topic it reports to.
We create your bot with @BotFather, keep its token in the vault in your cloud account, and add it to the groups you choose.
Read-only exchange API keys, custody, the blotter, the runbooks, and the schedule it runs on.
Within a week. Then the next job, and the next team's agent.
FAQ
Each Glimmer agent is its own Telegram bot, created with @BotFather and connected through the Telegram Bot API. The bot token sits in the vault in your own cloud account. It does not use a phone number, a SIM or a logged-in staff session. You add the bot to the groups you switch on for it. Telegram allows a bot about 20 messages a minute in a group (Bot FAQ), so Glimmer edits one progress message in place instead of posting a stream.
Glimmer keeps Telegram's privacy mode on. In a group it receives messages that @mention it and replies to its own messages, and it does not receive the rest of the conversation. It works only in the groups you switch on for it.
Google Workspace, Notion, Jira, GitHub, Grafana, HubSpot, Xero and NetSuite, plus your exchange and custody APIs or in-house systems as custom connectors. In the Glimmer console you tick the tools each agent may use, system by system.
No. Glimmer prepares transfers and payout batches. Your signers sign in your custody platform as they do today. Exchange API keys are read-only unless you decide otherwise.
Telegram group chats are cloud chats with client-server encryption, stored on Telegram's servers. Only 1:1 secret chats are end-to-end encrypted (Telegram FAQ). Glimmer's side stays in your cloud account: the bot token, the files it reads, its memory and its model calls.
Telegram bots do not see messages from other bots (Bot FAQ), so Glimmer subscribes to the source itself: exchange and custody APIs, Grafana webhooks, GitHub, the inbox or a schedule. It then posts to the right supergroup topic.
Glints engineers set up Glimmer with your team as a build partner. The first job works within a week, in the topic where your team needs it.
Tell us the job your team does every day. In 20 minutes our engineers show you how the bot does it, and which systems it reads.