AI agents are helpers that look after a Briks site once it is live, on every paid plan. Each agent has a job, a schedule and a monthly budget, and asks you before it emails anyone, changes your site or posts to your social accounts.
Weekdays at 17:00, and on each form entry
Before it emails
Leads has prepared something and is waiting for your yes.
Try it: this demo works right here on the page.
Each agent has a job, a schedule and a monthly budget, and asks you before it emails anyone, changes your site or publishes a post. You decide in the studio, by email or on Telegram. Times follow your workspace's time zone.
Plans the crew's week from your goals, hands out the work, and sends you one stand-up.
Asks you first: the week's plan
Answers the questions your site's chat passes on, by email from your site's address.
Asks you first: every reply
Replies to what visitors send through your forms, and sends you a digest.
Asks you first: every reply
Keeps your site's facts current: hours, prices, seasonal text and broken links.
Asks you first: every change
Wakes when your site stops answering or comes back, when a certificate is within 14 days of expiring, or when a scheduled job or webhook fails, and proposes repairs.
Asks you first: any repair
Checks your code and keys after every publish, and the whole site with its live pages every week. Tells you plainly what it found, and has the builder fix only what you approve.
Asks you first: every fix, always
Gets you found and chosen in search: titles, descriptions, headings, picture text, links between pages and speed.
Asks you first: every change
Gets your business named when people ask AI assistants: checks AI crawlers can read your site, asks Claude and ChatGPT what buyers ask, and proposes changes.
Asks you first: every change
Writes a search-friendly post every day, or on the days you choose, in your voice and from your facts.
Asks you first: publishing
Looks at every page on phone, tablet and desktop, finds what a visitor would notice, and has the builder fix it in your design.
Asks you first: every change
Writes next week's posts for your X and LinkedIn accounts from what your business already has, in your voice.
Asks you first: every post
Plans next month on the 25th, turns your offers and events into campaigns, and reports what brought visits and enquiries.
Asks you first: every plan
A one-page week every Monday: results, what each agent did, and what needs you.
Asks you first: nothing, it only reads
Security tells you what it found, what it means for you and what it would change. Its fixes always wait for your approval, and each one is published as a new version you can undo.
Anyone can read every order by changing the number in the address
Describe a job and the studio drafts the agent: its name, job, permissions and schedule. You set its budget and edit everything before it runs.
3 waiting for you.
Team lead, Site keeper, Support, Leads, Site watch, SEO, Designer and coder, Reporter, Articles, Social, Marketing, AI search and Security, or describe one of your own.
Each runs on its own schedule, or when something happens on your site.
Emails, site changes and posts wait for your yes, in the studio, by email or on Telegram.
Each agent has one job and its own schedule, and works on your site between your visits to the studio. Support wakes when your site's chat passes a question on. Leads runs on weekdays at 17:00 and on each new form entry. Site keeper runs on Mondays at 08:00. Site watch wakes when your site goes down or comes back, when a certificate is within 14 days of expiring, or when a job or a webhook fails.
SEO runs on Wednesdays at 09:00, AI search on Tuesdays at 09:00, Articles daily at 09:00, Designer and coder on Thursdays at 10:00, and Reporter on Mondays at 08:00. Times follow your workspace's time zone, UTC unless you set another, shifted by up to 10 minutes, and every agent also wakes when you write to it.
Social writes next week's posts every Thursday at 10:00 for the accounts you connect in the project's Marketing tab. Marketing plans next month on the 25th and runs this week's part of the plan every Monday at 09:00. Today both work with X and LinkedIn profiles, and more platforms follow as they approve Briks.
Security checks your site's code after every publish, and the whole site, live, on Mondays at 07:00. It explains each finding in plain words, and every fix it asks for waits for your approval, always.
The Team lead plans the crew's week every Monday at 08:00 from your goals, hands each task to the teammate who can do it, and sends you one stand-up. Reporter takes no outward actions at all. The others prepare work for you to approve.
More people now ask an AI assistant which business to choose. The AI search agent works to get yours named and quoted there. Every Tuesday it checks that 14 AI crawlers can reach your pages and read them, along with your sitemap, your llms.txt file and the structured data that says who you are and what you offer.
Once your site is in production, it asks assistants the questions your buyers really ask, never with your name in them, and keeps the same questions from month to month so the change is real. It asks Claude and ChatGPT. It also reads the visits that AI assistants sent to your site.
Then it asks you for at most two changes at a time, the ones most likely to get you quoted, such as a page that answers a buyer's question in its first lines. It never promises a place in any assistant's answers, and never hides text that only crawlers would see.
Agents ask before they act outward. Sending an email, editing your site and publishing a post all wait for your approval. Support and Leads ask before they email; Site keeper, SEO and Designer and coder ask before changes; Site watch asks before a repair; Articles asks before publishing, before updating an older article, and before adding a blog to your site; the Team lead asks before it hands out the week's plan.
You decide in the studio, by email, or on Telegram once you connect it.
Trust can grow. After five clean approvals of one kind, an agent offers to do that kind on its own, and you decide whether to let it. Security fixes are the exception: they wait for your approval every time.
Each agent sees only its own workspace, enforced in the database itself, so an agent working on one client's site can never read another's.
Each agent has a monthly budget in credits: 20 by default, 30 for SEO, 30 for the Team lead, 40 for Designer and coder, 60 for AI search, Social and Marketing, and 90 for Articles. When it is reached, the agent stops until the 1st of the month. Three failed runs in a row pause it, and failed runs are not charged.
You can also describe an agent of your own in a sentence. The draft gives it a name, a job, its tools, the events it listens for and a schedule, with a budget you set, 20 credits by default, and you check and change all of it before hiring.
Agents come with every paid plan: Starter includes 3 agents per project, Pro 5, Studio 10 and Agency 15. Their runs are paid from your workspace's credits, within each agent's budget.
Agents are for the work that piles up after launch: answering the questions your chat passed on, replying to enquiries, keeping pages current, writing articles and social posts, getting found in search and by AI assistants, and keeping an eye on the site while you sleep.
They are designed for owners who would rather approve than do. Each agent prepares the work, and you say yes, ask for a change, or say no.
The Reputation agent will answer every Google review and ask every recent customer for one. It arrives once Google has approved Briks's access to Business Profile.
Like the agents above, it will ask you before anything goes out, in batches you can approve all at once, in part, or with changes in plain words.
Three example businesses, and how each would use it. Where a site is pictured, it is a sample Briks built for an example business, not a customer.
A B&B's chat passes a question about late check-in to Support, which drafts an email reply. The reply waits until the owner approves it in the morning, and nothing is sent before then.
Leads runs on weekdays at 17:00 and on each new form entry. For a building firm, that would mean a drafted reply to each quote request, waiting for approval before any email goes out.
Articles runs daily at 09:00 and asks before publishing anything, before updating one of its older articles, and before adding a blog to a site that has none. Its budget of 90 credits a month caps what it can spend.
Every paid plan. Starter includes 3 agents per project, Pro 5, Studio 10 and Agency 15. Free does not include agents.
No. Emails, site changes and posts wait for your approval. After five clean approvals of one kind, an agent offers to do that kind on its own, and you choose.
Their runs are paid from your workspace's credits. Each has a monthly credit budget, 20 by default. When it is reached, the agent stops until the 1st.
No. Each agent sees only its own workspace, and that is enforced in the database itself.
Team lead, Site keeper, Support, Leads, Site watch, SEO, Designer and coder, Reporter, Articles, Social, Marketing, AI search and Security. Reputation is next.
The Team lead. Each Monday it plans the week from your goals, asks you to approve the plan, hands each task to the teammate who can do it, and sends you one stand-up.
X and LinkedIn profiles today, connected in the project's Marketing tab. More platforms follow as each one approves Briks.
It does the work that makes it likelier: a site AI crawlers can read, clear answers to buyers' questions, and facts stated plainly. No one can promise a place in an assistant's answers, and it never does.
Three failed runs in a row pause it, and failed runs are not charged.
Describe it in a sentence and Briks builds it. Start free with the credits you get at sign-up.