Reply to the Agent from anywhere

Buron's Agent sends you things: scheduled reports, automated digests, alerts. Now every one of those messages is a real thread you can reply to. Reply in your normal email, Slack, or WhatsApp client, and the actual workspace Agent wakes up, runs scoped to the right workspace, and answers back in the same thread.

Your reports used to be one-way. A number looked off, and you had to leave the message, open the app, and dig. Before this, replying to a Buron message went nowhere. The reply hit a placeholder and nothing answered. Now you just reply where the message already is, and the Agent answers with your real data, in-thread. The same mechanism works the same way across all three channels.

This is the same Agent you chat with in the app. A reply just wakes it in a different place. To learn what it can do, see Meet the Agent. This page covers replying from outside the app.

Before you begin

• A Buron workspace, with a team slug set. Email turns on automatically once your team has a slug.
• For Slack: admin access to your Slack workspace, so you can install the Buron app.
• For WhatsApp: your own WhatsApp Business number and Meta app credentials. This one's for teams who run their own number.

You'll find all three channels in Settings → Integrations, alongside your ad platforms, CRMs, and data sources. Once a channel is connected, it shows up in the Installed group at the top of the page, each with a green check.

Step 1: Turn on email (it's automatic)

Open Settings → Email. There's no connect step. Email is "connected" as soon as your team has a slug.

Under Your agent reply address, you'll see your team's address. Emails from Buron are sent from it, and replies route back to your workspace Agent. It looks like this:

acme.ab12cd34ef5@agents.buron.ai

The part before the dot is your team slug. The part after is a signature Buron uses to confirm the reply really belongs to your workspace.

If you don't see an address yet, the page tells you: your team needs a slug before the email channel is active. Set one in workspace settings, then come back.

There's also an Automated email updates toggle. It controls whether you get scheduled reports and digests by email. Turning it off stops those proactive sends, but it doesn't affect replies to a thread you started: you can always reply and get an answer.

Step 2: Connect Slack

Open Settings → Slack. Under Workspace connection, click Connect Slack and approve the consent screen. It's the same one-click OAuth flow as connecting a CRM. When you come back, you'll see a Slack connected confirmation and a green Connected badge.

The connection card shows a green dot, the word Connected, your workspace name, and how long ago it connected. The ⋮ menu (Connection options) lets you Reconnect or Disconnect.

If Slack ever needs attention, the dot turns amber and the label reads Needs reconnect, with a note that Buron's Slack access was revoked or expired. Reconnect from the same menu to restore messaging.

If your deployment hasn't set up Slack yet, the page says Slack isn't configured on this deployment, and the connect button stays disabled. An admin needs to set the Slack app credentials first.

Step 3: Connect WhatsApp

WhatsApp is more hands-on than Slack. Instead of one-click OAuth, you paste your own WhatsApp Business credentials, so it's built for teams running their own WhatsApp Business number.

Open Settings → WhatsApp. First, copy the Webhook callback URL from the page. In the Meta app's WhatsApp configuration, set this as the webhook callback URL, and use the verify token you enter below.

Then fill in the Connect fieldset:

• Phone number ID is the WhatsApp Business phone number ID, not the phone number itself. This is the routing key Buron resolves inbound messages on.
• WABA access token is a WhatsApp Business System User access token.
• App secret is the Meta app secret. It keys the X-Hub-Signature-256 verification on every inbound webhook.
• Webhook verify token is the verify token you set in the Meta webhook configuration. Used for the GET handshake.
• Display label (optional) is a human label for this number, like +1 555 010 0000, shown on the connection card.

Click Connect WhatsApp. The button enables once the phone number ID, access token, app secret, and verify token are all filled in. Once connected, the same fieldset reads Update connection so you can re-save anytime.

If the connection errors, the page tells you that Buron's WhatsApp access was revoked or the webhook signature failed. Re-save the connection to restore messaging.

How a reply wakes the Agent

The loop is the same on every channel:

1. Buron sends a message (a scheduled report, digest, or alert) as a tracked, repliable thread.
2. You reply in your normal client with a real question, like "Why did cost-per-lead jump on Brand last week?"
3. Buron verifies the reply, figures out which workspace the thread belongs to, and confirms you're an active member.
4. It sends a quick acknowledgement, then runs the real workspace Agent out of band (so it doesn't block your reply) under the team's service identity.
5. The Agent answers back into the same thread, grounded in your workspace data.
6. You can keep replying. The conversation keeps full context, even days later.

The acknowledgement looks a little different per channel. On Slack, you'll see a working signal within seconds (a 👀 reaction or a status indicator) that resolves to ✅ when the answer lands, or ❌ if something goes wrong. On email, there's no reaction. The threaded reply itself is the acknowledgement.

The Agent is read-only when you reply. It can pull data, dashboards, and reports to answer you, but it can't push changes from a reply. If you ask it to change something, it explains what it would do, so you can confirm in the app or in a follow-up.

What Buron captures

Each channel becomes a durable conversation thread, so:

• The thread keeps full context across replies, even 30+ days later.
• Each reply is matched back to the originating message's thread and the correct workspace.
• The Agent's answer is grounded in your workspace data, the same evidence the in-app Agent cites.

When the Agent shows a chart or table, it does so by citing a link that renders inline. Charts are delivered privately, per channel: an authenticated, in-workspace upload on Slack, and inline image bytes in email. Never a public URL.

Where to see it

• Settings → Integrations, where your connected channels appear in the Installed group.
• Each channel page (Email, Slack, WhatsApp) shows live connection status.
• The threads themselves live in your email client, Slack, or WhatsApp, wherever Buron messaged you.

Frequently asked questions

Who can reply and get an answer? Messaging is members-only. Only active team members can message the Agent, matched by their email to a Buron member. Non-members and service accounts can't, and Buron only ever runs scoped to the workspace the thread belongs to. If someone who isn't yet a member replies, they can request access, and an admin approves it in-app.

Can the Agent change my campaigns when I reply? No. On a reply the Agent is read-only. It can pull data, dashboards, and reports to answer you, but it can't push changes. If you ask it to change something, it'll explain what it would do so you can confirm in the app.

Do I have to set anything up for email? No. Email is on as soon as your team has a slug. Your reply address (like acme.ab12cd34ef5@agents.buron.ai) is shown on the Email page, and replying to any Buron email just works.

Are the charts in messages public? No. Charts are delivered privately: an in-workspace upload on Slack and an inline image in email, never a public link.

What's the difference between connecting Slack and WhatsApp? Slack is a one-click connect: click Connect Slack and approve. WhatsApp is for teams running their own WhatsApp Business number. You paste your phone number ID and Meta credentials on the WhatsApp page.

How long does the Agent remember a thread? The conversation context is stored durably, so a follow-up reply days later still continues coherently.

Next steps

• Meet the Agent: the same Agent that answers your replies
• Build an automation to set up the scheduled reports and alerts that become repliable threads