CupidBot on Telegram: Complete Setup Guide (Install to First Converted Sub)

This is the most-asked topic in OFM Telegram groups: people buy the bot, open the extension, and hit a wall on step two or three. The install itself isn't hard; the problem is that the setup is spread across three things at once (browser, Telegram account, bot license) and all three have footguns. Work through this in order.

---

1. Prerequisites checklist

Before you open the Cupid dashboard, have these ready:

• A Telegram account that isn't your personal one. Fresh or aged, both work if warmed up properly (see Guide 03 on warm-up). Do not run the bot on the phone number you DM friends from.
• The model's OnlyFans link, ideally the tracking link you actually want to measure against. Not just "the OF page".
• A preset / persona for the model (3-5 photos, a first-line intro, tone notes, a CTA). Don't improvise this at step 5.
• A supported browser environment: Chrome, Sunbrowser, or an antidetect like AdsPower. Not the Telegram desktop app.

The Telegram-desktop-app confusion is the single most repeated mistake in the chats. When people say "desktop" they think of the native .exe they installed. CupidBot on Telegram runs on web.telegram.org inside a browser, the "desktop" in the docs means "your desktop computer running Chrome", not the native app. If you open the Telegram .exe to run the bot, nothing will happen.

---

2. License types, Telegram ≠ Snap ≠ Bumble

Another persistent confusion: licenses don't transfer.

The Cupid product line has separate purchases for Bumble, Snapchat, Tinder, and Telegram. Buying the Bumble license does not unlock the Telegram bot, even though it's the same extension on the surface. Same for people who bought the Snap version "by mistake".

If you buy the wrong one:

• The extension will only show the platform your license covers, this is why people ask "why does my extension only give me the Bumble option?"
• Contact Cupid support to swap the license or refund, they do it, but don't expect an instant answer.

The $30 web license you see on the main website is typically the base dashboard access, not a per-platform unlock. You still need the Telegram-specific add-on.

---

3. Installing the extension and loading your token

1. Install the Cupid browser extension from the link in the dashboard (Chrome Web Store or sideload for Sunbrowser).
2. Pin the extension, open it.
3. Copy the token from your Cupid dashboard (not your email, not your login, the dashboard shows a specific API token).
4. Paste it into the extension.

The "Ctrl+Shift+R infinite loop" bug. This is asked over and over: you paste the token, and the extension tells you to press Ctrl+Shift+R, you do, and it asks again. Fix:

• Make sure you pasted the token with no trailing spaces or newlines (copying from a chat usually brings a trailing newline, backspace once).
• After Ctrl+Shift+R, wait 5-10 seconds before doing anything else. The extension needs the cleared cache to be fully rebuilt.
• If still looping, log fully out of the dashboard → close browser → reopen → paste token fresh.

If the extension still shows only the Bumble option, you're on a Bumble-only license, see Section 2.

---

4. The Telegram account inside the browser

Open web.telegram.org in the same browser profile where the extension is installed. Log in with the Telegram account you prepared.

Do not use your personal TG. Two reasons:

• When Cupid starts DMing leads, your personal contacts will be visible in the same account.
• If the bot account gets frozen (see Guide 02), you lose a throwaway, not your life.

Keep the browser tab open. CupidBot operates inside the web Telegram session, close the tab, the bot stops. That's why a VPS setup (Guide 13) matters once you're running more than one or two accounts.

If you need to verify a fresh SIM at this step, see Guide 05.

---

5. Creating the model preset

In the Cupid dashboard, create a preset for your model. Required:

• 3-5 photos (Telegram compresses hard, send at max resolution, but the first photo shouldn't be the most explicit one you have, because it's what leads see first).
• A first-line intro (20-40 chars). Something believable, not "hey baby 😘".
• Tone notes, how the bot should reply. Short, playful, teasing vibe works. Avoid anything that reads as obviously AI.
• The CTA (see next section).

Running multiple models. Yes, just create a new preset per model. Each preset is one persona. You can have as many presets as your license allows; switch between them at the preset-picker at the top of the dashboard. You do not need a new Cupid purchase per model, just a new preset.

---

6. Configuring the CTA (funnel link)

The CTA is where most leaks happen. The bot will send this link when it detects a lead is warm enough.

Options people use:

• Raw OnlyFans URL (onlyfans.com/modelname). Works but Telegram sometimes shows the "Premium Telegram" link-preview garbage over it, which looks suspicious.
• Tracking link (Beacons, OnlySocial, your agency's tracker). Recommended for attribution, you want to know which subs came from this specific bot run.
• Bouncy.ai / deeplinks, short-code layer that hides the destination until click. Good for avoiding Telegram's link preview. Works for some people and not others; if it doesn't work for you, alternatives are linktr.ee, allmylinks.com, or a plain .link domain you own.
• "onlyfans .com" with a space, the old trick of breaking up the domain so Telegram's auto-link-preview doesn't trigger. Still works in 2026, but it hurts click-through because the lead has to copy-paste. Only use if you're actively trying to dodge Telegram's preview crawler.

To specifically avoid the "Premium Telegram" preview, either use a shortener that doesn't trigger Telegram's OG-image fetch (Bouncy, Beacons) or the space trick.

---

7. Daily caps and conversation limits

The caps exist because Telegram bans accounts that DM strangers at high volume. Settings that commonly work on a warmed account:

• New conversations per day: 30-60 for weeks 1-2, then ramp to 100-150 over a month.
• Reply cap: 80-150 messages/day per account.
• If you're asking "can we not change how many new convos per day on telegram?", yes, it's in the preset settings, sometimes hidden under "advanced".

Accounts that aren't warmed (Guide 03) should start at 10-20 new convos/day and climb slowly. Go hard on a cold account and you'll be frozen by day 2.

---

8. First-run verification

When you enable the bot, the extension will show a status panel. Healthy signs:

• "Listening for messages" or similar.
• You can manually send a test message from the model's TG to another of your accounts and see it captured.

"Waiting, Telegram is loading…" is not always a problem, it means the web session is slow. Give it 60 seconds. If it persists beyond 5 minutes, usually the cause is:

• Bad VPS / slow proxy, not a bot issue.
• Telegram itself rate-limiting the session (happens after bulk joins).
• Browser profile corrupted, open a clean profile and re-login.

---

9. What the bot actually does on incoming DMs

The bot watches your Telegram inbox. When a stranger messages the model's account, it:

1. Detects the language (EN / ES / PT / DE are solid; others patchy).
2. Replies using your preset tone.
3. Escalates over 3-8 messages.
4. Fires the CTA when the conversation hits the "warm" threshold, detected via keywords, emoji intensity, and message cadence.

You can manually intervene at any time, type in the chat yourself and the bot pauses for that conversation. Useful when a whale lead shows up.

---

10. Common first-day errors

• "Infinite tabs bug", extension opens a new tab every few seconds. Cause: the bot tries to authenticate via a username that conflicts with the browser profile. Fix: log out of web.telegram.org entirely, clear site data for web.telegram.org, log back in.
• "Edge keeps refreshing", Edge's anti-fingerprinting aggressively reloads sessions. Switch to Chrome or Sunbrowser. Edge is not officially supported.
• "Bot can't detect model/preset", the preset wasn't saved or the token points to a different dashboard user. Re-select preset in the extension after saving.
• "I chose the wrong Telegram username during purchase", the Cupid license binds to a username at purchase. Contact support; they can re-bind once per license.

---

Pausing and resuming cleanly

Before you hit any of the "ban-triggering" activities covered in Guide 02 (changing preset, swapping SIM, etc.), pause the bot via the extension's toggle, don't just close the tab. A clean pause keeps the session state; a hard close makes the bot think it crashed, which sometimes triggers re-authentication and wastes warmup.

---

Scaling beyond one account

If you're running 3+ bots at once, you'll need proxy rotation, antidetect profiles, and eventually a VPS, see Guide 13 (Infrastructure). Trying to run 5 bots off your home laptop on the same IP will get all 5 frozen within a week.

---

Next in this pillar: Guide 02, Stopping account freezes/bans, Guide 03, Warm-up, Guide 13, Infrastructure.