Email Channel

The email channel puts your support inbox in the same Telegram group as your widget chats. Someone emails [email protected], it lands as a topic in Telegram, you reply in the topic, and they get a normal email back from your own address.

Nothing changes about how you work. You answer everything in Telegram, whether the person used the widget or sent an email.

How it works

You keep your existing mailbox. We do not replace it, and you do not move your email anywhere. You set up a forwarding rule that sends a copy of incoming mail to a private address we generate for your project. That address is the only piece of plumbing involved.

1. A customer emails your support address.
2. Your mail provider forwards a copy to your Bubblegram address.
3. We create a Telegram topic for that sender and post the message, with attachments.
4. You reply in the topic.
5. They receive an email reply. If your domain is verified it comes from your own address.
6. Their reply comes straight back to the same topic, no forwarding involved.

Setup is two steps. Step 1 gets email flowing into Telegram and is all most people need. Step 2 makes replies go out from your own domain instead of ours, and is optional.

1. Turn on the email channel

Open your project in the dashboard, go to the Email tab, and click Enable email channel. You get an address that looks like this:

[email protected]

It is unique to the project and not guessable. Treat it as private: anyone who knows it can post into your Telegram group. It does not change if you disable and re-enable the channel later, so your forwarding rule keeps working.

2. Forward your support email

Set up forwarding to that address in whatever provider hosts your support inbox. The dashboard shows exact steps for your provider. Gmail is the one worth walking through here, because it takes two settings that look like one.

Gmail and Google Workspace

1. Open Gmail, click the gear icon, then See all settings.
2. Go to the Forwarding and POP/IMAP tab.
3. Click Add a forwarding address, paste your Bubblegram address, then click Next, Proceed, OK.
4. Gmail emails us a confirmation link. It shows up on the Email tab within a few seconds: open it and click Confirm.
5. Go back to the Forwarding and POP/IMAP tab in Gmail settings, select Forward a copy of incoming mail to, then choose the address above from the dropdown next to it.
6. Scroll to the bottom of the page and click Save Changes.

You never have to go hunting for Gmail’s confirmation email. It is sent to an address only we can read, so we watch for it, pull out the link, and put it on the Email tab. It also goes to your Telegram group as a backup.

Google Workspace accounts follow the same six steps. If step 3 fails outright, forwarding is probably disabled for your organization, or restricted to an allowlist of domains that yours needs to be added to.

Other providers

Confirming it works

Nothing arrives on its own. Once forwarding is saved, email your support address from a personal account. Within a few seconds a topic appears in Telegram and the dashboard flips step 1 to done on its own, with no refresh needed. Forwarding only applies to mail that arrives after you saved, so anything already sitting in the inbox stays there.

3. Reply from your own domain

This step is optional. Skip it and everything still works, replies just go out from [email protected] instead of your own address.

Enter your domain and the address you want replies to come from, for example [email protected]. The from address has to be on the domain you are verifying. We generate three DNS records for you to add at your registrar:

The dashboard checks verification for you every few seconds and updates each record as it goes green. DNS changes usually take a few minutes, occasionally a few hours. You can close the tab and come back.

What it looks like in Telegram

Each sender gets their own topic, named with an envelope so you can tell it apart from widget chats at a glance:

📧 [email protected]

The first message in a new topic is preceded by a short info card:

From: [email protected]
Subject: Can't reset my password

Attachments come through as files or photos in the same topic (see attachment limits). Quoted reply chains and signatures are stripped, so you see what the person actually wrote rather than the whole thread. If a message fails sender authentication, we flag it at the top rather than hiding it, since that’s a common sign of a spoofed address.

Replying

Just reply in the topic. A few details worth knowing:

• Several quick replies are bundled into one email rather than sent separately, so you can think out loud without filling someone’s inbox.
• Replies thread properly in the recipient’s client, under Re: their subject.
• When they reply, it comes directly back to us and into the same topic. It does not depend on your forwarding rule, and it works even if they answer from a different address than the one they wrote in with.
• If someone starts in the widget and continues by email, or the other way around, it stays in one topic with the full history.
• /close works the same as it does for widget chats. If they email again later, the topic reopens.

What we filter out

A support inbox receives a lot that isn’t a customer talking to you. Rather than forwarding all of it into Telegram, we drop the following silently:

So a forwarded newsletter is not a useful way to test your setup. Send an ordinary email from a personal account instead.

Limits

• Around 15 emails per minute per project, in short bursts of up to 20.
• 5 emails per sender per 5 minutes, which stops one loop or one angry refresher from flooding the group.
• Up to 20 new conversations at once, then roughly 6 per minute after that.
• Message bodies are capped at 50,000 characters.

These are far above normal support volume. If you are hitting them, something is looping and we should look at it together.

Turning it off

Disable email channel on the Email tab stops delivery. Your address and domain verification are kept, so re-enabling later is one click and your existing forwarding rule still points to the right place. Remember to remove the forwarding rule at your provider too, otherwise your mail is being copied somewhere that ignores it.