Telegram RegisterThe public register of Telegram
Telegram profile photo for Salesforce Geeks

Channel

Salesforce Geeks

@salesforcegeek

On this record: Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry

12,024subscribers

-56 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001422144911
TypeChannel
Username@salesforcegeek
CreatedBetween 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live28 August 2026
Measurements held20
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/salesforcegeek

Growth

12,02412,08112,052.57 August 2026 — 12,080 subscribers7 August 2026 — 12,080 subscribers8 August 2026 — 12,081 subscribers9 August 2026 — 12,077 subscribers11 August 2026 — 12,070 subscribers12 August 2026 — 12,066 subscribers13 August 2026 — 12,064 subscribers14 August 2026 — 12,054 subscribers16 August 2026 — 12,053 subscribers17 August 2026 — 12,047 subscribers18 August 2026 — 12,046 subscribers19 August 2026 — 12,048 subscribers20 August 2026 — 12,051 subscribers22 August 2026 — 12,047 subscribers24 August 2026 — 12,042 subscribers25 August 2026 — 12,040 subscribers26 August 2026 — 12,033 subscribers27 August 2026 — 12,031 subscribers27 August 2026 — 12,027 subscribers28 August 2026 — 12,024 subscribers7 August 202628 August 2026
20 measurements spanning 21 days, net -56. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 12,015–12,090 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 23:4212,024-3
27 Aug 2026, 22:1712,027-4
27 Aug 2026, 00:2412,031-2
26 Aug 2026, 02:2512,033-7
25 Aug 2026, 05:3312,040-2
24 Aug 2026, 04:2412,042-5
22 Aug 2026, 09:5512,047-4
20 Aug 2026, 23:0112,051+3
19 Aug 2026, 22:0712,048+2
18 Aug 2026, 19:2412,046-1
17 Aug 2026, 16:1612,047-6
16 Aug 2026, 08:5412,053-1
14 Aug 2026, 21:1912,054-10
13 Aug 2026, 09:4612,064-2
12 Aug 2026, 12:3912,066-4
11 Aug 2026, 14:2612,070-7
9 Aug 2026, 10:5112,077-4
8 Aug 2026, 14:0412,081+1
7 Aug 2026, 23:3012,080no change
7 Aug 2026, 23:2212,080first reading

Engagement

19 posts held, back to 28 December 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 37 pagesof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 8 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

76 reactions across 17 posts, in 7 distinct kinds. The most used accounts for 53.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4153.9%
👍2228.9%
🔥79.21%
👏33.95%
🙏11.32%
🤔11.32%
🤣11.32%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 17 of the 19 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 76reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 28 December 2025 to 8 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

8 Jul 2026, 06:24 UTC≈1,770 views2 reactionsread 28 August 2026
Photo

How to Automatically delete Salesforce Flow Versions in Bulk | Flow Version Cleaner ⬇️ https://youtu.be/Yinl9fv9MIc for more join @salesforcegeek

2

Signed Shubham Bhardwaj

11 May 2026, 15:59 UTC≈3,470 views9 reactionsread 28 August 2026
Photo

Now you can redirect user to record page without creating LWC component with this new Action in Salesforce Flow Check out the tutorial video - https://youtu.be/PegxoqXz9b8 For more join @salesforcegeek

6👍3

Signed Shubham Bhardwaj

11 May 2026, 06:16 UTC≈2,970 views6 reactionsread 28 August 2026
Photo

Summer 26 New Salesforce Flow Action No more need to create custom component to achieve this Check it out ⬇️ https://youtu.be/Elw19SwxK80 For more join @salesforcegeek

👍51

Signed Shubham Bhardwaj

7 May 2026, 02:27 UTC≈3,010 viewsread 28 August 2026

Now you can add Lightning Web Components on Salesforce Dashboards https://www.linkedin.com/posts/salesforcegeek_salesforce-dashboards-summer26-activity-7457816705915072512-hrVp For more join @salesforcegeek

Signed Shubham Bhardwaj

29 Apr 2026, 01:31 UTC≈3,240 viewsread 28 August 2026

You don't need DKIM Keys for Salesforce Sandbox Just turn on this feature - https://www.linkedin.com/posts/salesforcegeek_you-dont-need-dkim-in-every-salesforce-sandbox-activity-7454932418391687168-qHTB For more join @salesforcegeek

Signed Shubham Bhardwaj

15 Apr 2026, 09:21 UTC≈3,830 views2 reactionsread 28 August 2026
File

Summer 26 Salesforce Flow Features For more join @salesforcegeek

1🤔1

Signed Shubham Bhardwaj

19 Mar 2026, 08:10 UTC≈4,520 views1 reactionsread 28 August 2026

Added New Playlist to the channel for New Flow Videos https://youtube.com/playlist?list=PL9kdg63vJl6A5q7R0KuybyZ6kDv4bcVxs&si=Qr1_h6WqOkiHY3gt For more join @salesforcegeek

1

Signed Shubham Bhardwaj

17 Mar 2026, 05:21 UTC≈4,170 views3 reactionsread 28 August 2026

I started posting the fresh content on Salesforce Flow from scratch ⬇️ Get Records Element in Salesforce | How to fetch data in Salesforce Flow https://youtu.be/b4fjYk8HL-s More detailed tutorials totally indepth Subscribe - youtube.com/salesforcegeek

1👍1🔥1

Signed Shubham Bhardwaj

13 Mar 2026, 04:45 UTC≈3,680 views8 reactionsread 28 August 2026
Photo

Future of Salesforce Developer Roles Official Article by Salesforce https://developer.salesforce.com/blogs/2026/03/future-salesforce-developer-agentic-ai What's your take ? On this For more join @salesforcegeek

5🔥3

Signed Shubham Bhardwaj

13 Mar 2026, 03:18 UTC≈2,940 views1 reactionsread 28 August 2026
Photo

Anthropic shared a report for the the Jobs Most Exposed to AI Risks ⬇️ Computer programmers, customer service representatives and data entry workers face the highest AI displacement risk today. No doubt things are changing we need to prepared. Read full report here - https://www.anthropic.com/research/labor-market-impacts for more join @salesforcegeek

1

Signed Shubham Bhardwaj

4 Mar 2026, 09:59 UTC≈3,010 views9 reactionsread 28 August 2026
Photo

Happy Holi Everyone 🎨

7👍2

Signed Shubham Bhardwaj

3 Mar 2026, 07:06 UTC≈3,390 views12 reactionsread 28 August 2026

If you are in Salesforce Development and still ignoring AI tools like ChatGPT or Claude, thinking they won’t affect your job — that’s risky. Development is already changing. AI won’t replace good developers. But developers who use AI will replace those who don’t. Start learning. Start experimenting. Use it for debugging, code review, documentation, ideas. Adapt early. Don’t wait.

👍9👏21

Signed Shubham Bhardwaj

Showing the 12 most recent of 19 posts we hold for @salesforcegeek. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

CUET Notes Class 12 CBSE NCERT UG PG
@CUET_Notes_Class_12_CBSE_NCERT · 117,820
Telegram ranks this channel #18 of 53 here — alongside 52 others — read 14 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 28 August 2026 — this entry's latest reading, not the date you are reading this.

“Salesforce Geeks” (@salesforcegeek), 12,024 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/salesforcegeek.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.