Questions BD leads ask first

Any account that messages strangers can be limited by Telegram, whatever tool you use, and nobody can honestly promise otherwise. Hilsen keeps the odds down with daily limits that are ceilings (messages you send by hand count too), random gaps between sends, sending windows, sequences that stop on reply, a safety check on every first message and a profile checklist for every sender. If Telegram limits an account anyway, Hilsen checks @SpamBot straight away, shows the release time, keeps your replies going and resumes by itself. It never raises volume after a limit.

Hilsen opens @SpamBot as that account right away, which starts Telegram’s release timer, and shows the release time with a live countdown. Replies to people who wrote first keep going. New conversations wait and resume by themselves once @SpamBot reports the account is clear. If @SpamBot gives no end date, the account is marked as needing action, with how to appeal.

Yes. A safety check reads every first message and follow-up as you write it, in campaigns and in the reply box. It flags links in a first message, too few or near-identical variations (about 5 per 100 recipients), long or pushy wording, money amounts, yields and token-sale, meme-coin or gambling talk, and says how to fix each one. Risky findings ask you to confirm at launch, and one click suggests a friendlier version.

Yes, when the person has never written to that account. A first message from the lead page or the Inbox uses the same daily limit and waits for the same gap between sends as a campaign, and the reply box shows how many are left today. At 0 it’s refused, with the time the limit resets. Replies to people who wrote first never count.

Tell Hilsen which kind of account it is. A personal account can stay on your phone, with a lower daily limit, and Hilsen never signs its devices out. A dedicated outreach account is best used only in Hilsen: the account shows where else it’s logged in, you can sign out a stray device, and a new login notifies the team. Only device, app and country are shown, never IP addresses.

From a fixed IP, so each account keeps one consistent location. You can give an account its own SOCKS5 or MTProto proxy, ideally in the country of its phone number. Hilsen tests it, shows where Telegram sees it, and if the proxy stops working the account waits for a person instead of quietly connecting another way. Proxies keep a location steady. They don’t get around Telegram’s limits.

Regular Telegram user accounts, signed in with your phone number and login code, two-step password included. Connect as many as your team uses; each has its own daily limits and sending window. Bots can’t message people first, so Hilsen doesn’t use them for outreach.

Not the way it’s built. Hilsen helps you reach a short list of people whose role fits, one conversation at a time, from your own accounts. Opt-outs are honoured automatically and sequences stop the moment someone replies. If your plan is thousands of identical messages a day, Hilsen is the wrong tool.

Explicit requests like “stop”, “don’t message me again” or “remove me from your list”, including common Nordic, German, Spanish, French and Portuguese phrasings, mark the lead Do not contact, stop all automation and notify the owner. Admins can undo it. A soft “not interested” is left to you.

As fast as a person would, and no faster. Each account keeps a random gap between sends (90 to 300 seconds by default), sends only inside the hours you set and never goes past its daily limit of new conversations, which tops out at 50 and includes first messages sent by hand. Telegram is likely to flag an account at around 30 new DMs a day, and new or rarely used accounts should start around 5 to 10 a day and build up over two to three weeks. Personal accounts are safer at about 10 to 15. Everyone else waits for the next window.

Always the account that started the conversation. If that account is paused, the lead waits instead of being handed to another account, so nobody hears from a stranger halfway through a thread.

Yes, per account: chats you pick, a Telegram folder or all direct messages, with a preview before anything is imported. Imported chats are private to you until you share them. Sync only reads: it never sends, never marks messages as read and never changes your online status.

No. Admins can change an account’s sync mode, but they never see the owner’s synced chats or folders. Private chats are also hidden from the API and from AI agents. The database enforces this, not just the interface.

Inside Hilsen, only members of your workspace, and only what their role allows. Synced chats are visible to their owner alone. Telegram sessions and keys are encrypted, two-factor sign-in is available to everyone, and sensitive changes go to the audit log.

Yes. Admins can forget a person: Hilsen deletes the lead and removes the copies it synced to Notion, Airtable, HubSpot and Google Sheets, and tells your webhooks.

No. Without a key, qualification, summaries and Autopilot run on rules with the same outputs. Add a key for Anthropic, OpenAI, Gemini, DeepSeek, Kimi, Qwen or any OpenAI-compatible endpoint when you want sharper results. Keys are encrypted and only their last four characters are ever shown.

No. Hilsen’s MCP server and API keys can search, read, summarise and draft, but there is no send tool. A person approves every draft. Autopilot is the only part of Hilsen that replies on its own, and only inside the rules of your Playbook.

The one you choose: your workspace default or a model just for Autopilot. Without a model it runs in rules mode, answering only questions that match your Playbook’s FAQs, word for word, and handing everything else to a person.

Hilsen is free while in beta. Create a workspace, load sample data and try every feature on simulated accounts before you connect a real one.

Sign up, name your workspace and switch on sample data. You get simulated accounts, sample leads, campaigns and conversations to explore. Connect a real Telegram account when you’re ready; bringing in your existing chats is an optional step right after.

Calendly and Cal.com links are tracked, so bookings update the lead by themselves. Leads sync to Notion, Google Sheets, Airtable and HubSpot, and Slack gets alerts for replies and booked calls.

Yes: a REST API and an MCP server with scoped keys (read, write or draft), plus signed webhooks for events like a lead replying or a call being booked.

Hilsen is Danish and Norwegian for ‘greetings’. It’s how people in the Nordics sign off a message, as in “Hilsen, Alex”, which suits a tool whose job is starting conversations. The two waves in the logo are a wave hello.