--- title: "Work on your sites from Telegram | Briks" url: https://briks.dev/docs/telegram description: "Connect Telegram to Briks to ask for changes, get answers, approve steps, publish and hear when builds finish, alone or with your team in a group." last_updated: 2026-10-08 --- # Work on your sites from Telegram The Briks bot on Telegram does the same things as the conversation in the studio: you write what you want and Briks builds it. It acts as you, with your role in each workspace, so it can never do more than you could in the studio. 9 minute read Checked against the studio on 8 October 2026 ## Connect your Telegram There are two ways to connect. The button is quickest. The phone number suits people who would rather start from Telegram. With the Connect button 1. Open your profile Where: Profile, Telegram Click your name at the foot of the sidebar to open **Profile**. The **Telegram** section shows whether a Telegram is connected. 2. Press Connect Telegram Where: Profile, Telegram Telegram opens with the Briks bot. A QR code also appears: scan it with your phone's camera to open the bot there. The link works once and only for 10 minutes. 3. Press Start in Telegram Where: Telegram The bot says which Briks account it is linked to and lists your sites. That's it. With your phone number 1. Add your mobile number Where: Profile, Telegram Type it with its country code, such as `+44 7700 900123`, and press **Save number**. Saving it links nothing on its own. 2. Share it with the bot Where: Telegram Message the Briks bot and tap **Share my phone number**. Telegram sends the bot the number it has verified for you. 3. Confirm by email Where: Your inbox If the number matches your profile, Briks emails you a link that lasts 30 minutes. Open it and press the button to link. Opening the link alone does nothing, so a mail scanner can't link anything for you. Why the email step A number typed into a profile is not proof that the number is yours. The email makes sure the account's owner agrees before any Telegram can act for them. The bot gives the same answer whether or not a number is on an account, so nobody can use it to look numbers up. ## Pick the site to work on Send `/sites`. The bot lists every site you can see, across all your workspaces, and you tap the one to work on. The chat remembers it until you pick another. If you only have one site, the bot picks it for you. Send `/status` to see the chosen site's state, its address, whether it's a preview or in production, and when it was last published. If a first build is waiting for you, the buttons to decide it come with it. ## Start a new site Send `/new` and a description, as you would write a brief in the studio. Start with `app` or `dashboard` to make one of those, and put a name before `|` if you want to choose it. Without one, the bot names the project from your first few words, and you can rename it later in the studio. A new site > /new Larder Lane | A small bakery in York. Sourdough, pastries and cakes to order, open Tuesday to Saturday, collection only. The bot starts the project in your workspace, holding 50 credits like New project does, and picks it as the chat's site. Then it asks which pages you want and anything unclear: answer in your own words or tap **Decide for me**. It tells you when the site is published. The project goes into the workspace of the chat's current site if you can change things there, otherwise into your own workspace. Your plan's limit on sites applies, as it does in the studio. To add a site you like or pick a look first, start the project in the studio instead. ## Ask for changes and questions In a private chat with the bot, just write. Briks reads each message the way the studio does: a question is answered at once and is free (a question about your visits uses credits once the site has had its 100 free ones this month), and anything else becomes a change, which sets aside 5 credits like any change. To make sure something is treated as a question, start it with `/ask`. A change A plumber's site > Add our emergency number 0113 496 0000 to the top of every page, in bold. The bot says it's working on it. When the change is published, it replies to your message with what changed and the site's address. A question > /ask Where do my form messages go? An answer from what your site is, straight away, with no build and no credits. If a build is already running, your change waits in line, exactly as in the studio, and the bot tells you so. Everything you send is also kept in the project's conversation, so you can carry on in the studio. ### Photos Send a photo with a caption saying what to do with it, such as "use this in the hero". The photo is placed on the site by that change, the way a picture attached in the studio is. A photo with no caption is not used: the bot asks you to send it again with one. ## Approve steps, undo and publish - **Approval steps.** If a first build stops for your approval (the words, a look or a hero), the bot shows buttons: **Approve the words**, one numbered button per look or hero, or **Decide for me** for the questions before building. **Open in the studio** shows the options side by side. You can also reply with what you want instead. - **Keys and credits.** A change that needs a key for another service shows an **Add** button for each key, which opens the site's Secrets with its name filled in, and **Build** to carry on with the keys saved so far. Keys are never sent through the chat. A first build waiting for credits shows **Get credits**; once you have them, choose **Resume building** in the studio. - **Agent approvals.** When an agent asks before it sends an email, changes your site or publishes a post, the request can reach Owners and Admins here, with **Approve**, **Reject** and **Look first**, which opens it in the studio. In **Profile**, under **Telegram**, **Agent approval requests** chooses **By email**, **On Telegram** or **Both**. Once anyone decides, wherever they did it, the buttons go and the message says who decided. See [Approvals and budgets](https://briks.dev/docs/agent-approvals). - **Undo and redo.** `/undo` goes back to the previous version and `/redo` brings back the one you undid, as in [Versions, undo and redo](https://briks.dev/docs/versions). - **Publish.** `/publish` asks **Publish to production?** with **Publish** and **Cancel**. If the first draft made up facts, such as figures or quotes, they are listed, and **Publish** confirms they are right. Writing "Publish" as a message does the same. The launch check runs first, and the bot tells you how it went. See [Publish to production](https://briks.dev/docs/publish-to-production). - **Agents.** `/agents` lists the site's agents and any waiting for your decision. Owners and Admins can pick one to **Pause** it or **Switch on**, **Run now**, or **Write to it**: your next message, within 15 minutes, goes into its thread, and its answer comes back here. An agent's questions, with **Reply**, and its reports reach Owners and Admins the same way as approval requests. See [AI agents](https://briks.dev/docs/ai-agents) and [Team lead](https://briks.dev/docs/team-lead). Watch out Approving a step sets aside up to 50 credits for the rest of the build, as it does in the studio: what your balance has, down to 5. If you have less than that, the bot says so. See [Approve as it builds](https://briks.dev/docs/approval-steps). ## Alerts Send `/alerts` to choose what this chat is told about its site. Each is off until you turn it on: | Alert | What you get | | --- | --- | | Builds finished or failed | The site's name, what changed and its address, or why it didn't work. A failed build is not charged. A build that was stopped, and GitHub sync needing you, come under this alert too. | | Steps waiting for approval | The step, with the buttons to decide it, and a first build waiting for credits, with **Get credits**. | | Domains live or needing attention | When a custom domain goes live, or something needs fixing, with what to do. | | Credits running low | When the workspace has fewer than 20 credits left after a build, at most once a day. | | New form messages | That a message came in, with the form's subject and a link to read it in the studio. What the visitor wrote is never sent to Telegram. | | Comments in the Visual Editor | Who commented, or named someone in a comment, and on which page, with a link to it in the [Visual Editor](https://briks.dev/docs/visual-editor). The comment's words are never sent to Telegram. People named in a comment also hear it in their own chat with the bot. | | Urgent security findings | An urgent finding of the [Security agent](https://briks.dev/docs/security-agent) or of the checks after a publish, with a link to the security report. | Whatever your alerts, a change, undo or publish you start from a chat is always reported back in that chat. ## Use the bot in a group Add the Briks bot to a Telegram group, so a team or an agency and its client can work on a site together. 1. Add the bot to the group Where: Telegram The bot introduces itself and explains the next two steps. 2. Each person links their own Telegram Where: Telegram, a private chat with the bot Anyone who wants to act must connect their own Telegram first. The bot reminds someone who hasn't. 3. Pick the group's site Where: The group Someone who can see the site sends `/sites` and taps it. The whole group then works on that site. In a group, start a change with `/change` (for example `/change make the Book now button green`), ask with `/ask`, or reply to one of the bot's messages. Telegram only shows the bot commands, mentions and replies to it, so the group's other conversation never reaches Briks. Each person acts with their own role: a Viewer in that workspace can ask questions and check the status, but can't change or publish anything. ## Disconnect and stay safe Press **Disconnect** in Profile, or send `/disconnect` to the bot. Connecting a different Telegram also moves the link and tells the old one. A Telegram can be linked to one Briks account, and an account to one Telegram. - Chats with bots are not end-to-end encrypted. Never send the bot passwords, keys or anything you'd keep secret. Use [Secrets](https://briks.dev/docs/secrets) in the studio for those. A key pasted into a message is cut out before it is kept, and the bot tells you where to add it, with **Open Secrets**. - The bot answers up to 30 messages a minute from each person, and questions are limited to 30 per site every 10 minutes, as in the studio. - The bot is on every plan, and everything costs the same credits as in the studio. - Every message to and from the bot is kept with your account, as the studio keeps its conversation. Deleting your account deletes yours. ### Can I use my Telegram username to connect? No. Usernames can be changed or taken by someone else, so Briks links to Telegram's own number for your account, through the Connect button or your verified phone number. ### The bot says I'm not a member of the workspace. The chat's site is in a workspace you don't belong to, usually in a group someone else set up. Ask its Owner or an Admin to invite you, or pick one of your own sites with /sites. ### Can the bot start a new site? Yes, with /new and a description. To build from a site you like, add your brand or pick a look first, start it in the studio instead. ## Read next - [Working on a project **Making changes** How to change your site by writing to Briks: what to say, adding pictures, what a change holds and costs, inner pages, queued requests and fixing a miss.](https://briks.dev/docs/making-changes) - [AI agents **Approvals and budgets** See what agents ask before they act, approve it in the studio, by email or on Telegram, choose what they may do alone, and set the budgets that cap their spend.](https://briks.dev/docs/agent-approvals) - [Workspaces and account **Members and roles** Invite people by emailed link and give each one a role: Owner, Admin, Editor or Viewer. See what each role can do and how many people each plan holds.](https://briks.dev/docs/members-and-roles) - [Publishing and domains **Publish to production** Take a Briks site from preview to production: what the launch check reads, what blocks a launch, how to fix each finding and how to go back to preview.](https://briks.dev/docs/publish-to-production) Still stuck? Write to [hello@briks.dev](mailto:hello@briks.dev) with your project's name and what you expected to see. A screenshot helps.