Work on your sites from Telegram

#Connect your Telegram

There are two ways to connect. The button is quickest. The phone number suits people who would rather start from Telegram.

#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.

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.

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.
• Undo and redo. /undo goes back to the previous version and /redo brings back the one you undid, as in Versions, undo and redo.
• 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.
• 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 and Team lead.

#Alerts

Send /alerts to choose what this chat is told about its site. Each is off until you turn it on:

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.

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 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.