Your own jobs channel

Build a branded Telegram jobs channel with Remotera data—under your name, in your format, for your audience.

Remotera keeps it supplied with fresh matching jobs. You control the name, avatar, audience, editorial voice, message format, and every link your readers see.

This works for a public niche job board, a private hiring-team feed, a local community, or several channels that need different editorial formats.

0:00 / 0:20

The actual Remotera template builder: inspect the live Telegram message, open code mode, add a custom branded block, and watch the production renderer update its preview.

Chapters

Transcript

Connect your channel

Create or open the channel in Telegram. Set its public identity there: name, avatar, description, and handle.

Open Alerts, choose Add channel, and follow the Telegram handoff. The person connecting it must be a channel administrator with a linked Remotera account.

Add the Remotera bot as an administrator with permission to publish messages. Return to Remotera and confirm that the destination is connected.

Create an alert from the job feed or the alert editor. Define the roles, skills, location eligibility, salary, and exclusions, then select the channel as its destination.

See Job alerts for the complete filter and delivery rules.

Make the posts look like your channel

Open the channel destination and choose Settings → Message template. The builder has a palette on the left and the delivered Telegram message on the right. The message itself is the editing canvas.

You can:

drag ready-made blocks into the message for title, company, pay, eligibility, summary, skills, alert reason, and other job facts;
move a block inside the message or drag it out to remove it;
open any block to edit its Telegram Markdown, {{ }} variables, pipes, and block-specific settings;
add a Custom block for a static brand header, editorial note, byline, disclosure, or footer;
switch to Edit as code to work on the entire template as one document;
save a block for reuse in another destination's template;
change the sample job to check how the format handles different data.

The preview is rendered locally with the same template package used by the delivery path. It is the message structure and inline keyboard that Telegram will receive, not an unrelated mockup.

Add branding without inventing job data

Put fixed brand language in a Custom block and keep job facts in variables. For example:

**NOMAD ENGINEERING**
_Remote roles, selected daily._

> {{alert.why}}

Telegram controls the chat chrome. Your channel controls its identity, and the template controls the words, order, formatting, sections, and buttons inside each post. There is no custom CSS layer.

Keep static claims separate from job fields. A salary, company, eligibility rule, or skill should come from a {{ }} variable so a post does not retain a fact from the previous job.

Choose a useful format

A public channel usually benefits from:

a short brand header;
title and company;
disclosed pay and work eligibility;
a concise summary;
a focused skill list;
a note explaining why the alert selected the job;
view and apply buttons.

An internal feed can be much shorter: title, pay, eligibility, and apply. Each destination stores its own template, so two channels can publish the same kind of search in different formats. Create one alert per destination that should receive it.

Test before publishing

Use the sample selector to inspect jobs with and without salary, summary, language, or company data. Empty variable-driven lines remove themselves, but the surrounding copy still needs to make sense when a field is absent.

Send a test from the destination settings before routing a live alert to the channel. Then check the actual Telegram post on both mobile and desktop.

Shared-channel privacy

Channels and groups are shared destinations. Remotera omits a viewer's profile match, personal account links, and other account-specific fields from their messages. A custom template does not turn those personal fields back on.

See Privacy and data for the boundary between personal and shared destinations.