Who we help · Social media & community teams

Manage conversations and moderation with the record preserved.

Your team posts, replies, moderates and escalates on the accounts your organisation runs. Brolly keeps the conversation and the decisions behind it, so the record survives edits, deletions and busy weekends.

30-day free trial · no credit card · unlimited accounts and users

The job

What this team is accountable for.

Five responsibilities sit with the people who run the channels, whatever the org chart calls them.

Publish

Posting and campaigns

Announcements, service updates and campaigns go out on the official accounts, on schedule and in the organisation’s voice.

Engage

Replying to the community

Questions get answered where they were asked. A reply on a public thread is part of the organisation’s public record of what it said.

Moderate

Applying the moderation policy

The policy your organisation wrote gets applied the same way on every channel, on the quiet days and during the pile-ons.

Escalate

Spotting what needs escalation

Threats, legal exposure and brewing issues get routed to comms leadership, legal or the service owner before they grow.

Preserve

Keeping the record intact

What was posted, what was said back, what was moderated and when. If it happened on your channels, someone will eventually ask about it.

The current process

Where the usual workflow breaks.

Most teams cover these gaps with effort and memory. Both run out.

Screenshots

Screenshot before deleting

Someone grabs an image of the comment before acting on it. The screenshot lands in a folder with no timestamp trail and none of the surrounding thread.

Memory

Decisions live in heads

Why a comment was hidden, who made the call and which rule applied lives with whoever was on shift. Six months later, nobody is sure.

Edits

Threads shift after you reply

A resident edits their comment after your answer, and the exchange stops making sense. The version you actually responded to is gone from the platform.

Weekends

Spikes hit off-hours

The pile-on starts Friday at 11 PM. By Monday the thread has moved, comments have been deleted, and the cleanup starts with guesswork.

A better operating workflow

Run the channels; the record keeps itself.

Examples show the product with fictional demonstration data.

Capture

The conversation is captured as it happens.

Supported posts, comments, edits and deletions from your connected Facebook, Instagram, Threads, X, YouTube, LinkedIn and TikTok accounts are captured in near real time. When a comment is edited after you replied, the version you answered is retained alongside the new one, so your reply keeps its context without anyone taking a screenshot.

  • Supported posts, comments, edits and deletions from connected accounts
  • Edited content keeps its earlier versions; deleted content stays in the archive
  • Capture runs in near real time, not as an end-of-day chore
Moderation

Moderate with the original kept.

Hidden is not deleted. Customer-configured rules act on supported content on your connected accounts, automatically where configured, and every action keeps the original comment, the rule that matched and the time. Authorised users then review: false positives are released back into view and the rules that produced them are adjusted, with both steps recorded. This is review after the action, never pre-approval of what your community can say. Moderation here is content-level; it is not designed to track, profile, ban or restrict individuals across unrelated accounts or services.

  • Hiding a matching comment removes it from public view, not from your record
  • Authorised review releases false positives and adjusts the rules, on the record
  • Rules are configured by your organisation and apply only to supported content on connected accounts
Handoff

Hand a thread over without reconstructing it.

When records or legal needs a thread, you hand over the thread as captured: the post, the comments and replies, any edits, any moderation actions and the times, together. The Friday-night incident is a lookup on Monday morning, not an afternoon of piecing screenshots into a sequence and hoping nothing was missed in between.

  • The thread as captured, with actions and times attached
  • Export-ready for FOI requests, reviews and legal questions
  • No rebuilding the sequence from screenshots and recollection
Relevant solutions

The workflows behind this role, in depth.

Each part of the operating workflow has its own solution page.

Solution

Moderation Governance

Apply the policy consistently on connected accounts, keep the original behind every action, and review from evidence.

Explore moderation governance
Solution

Official Channel Governance

Coverage, record, access and activity evidence across the channels your organisation owns, in one governance picture.

See the full picture
Solution

Social Media Recordkeeping

The preserved record behind the day-to-day: supported posts, comments, edits and deletions from connected accounts, searchable and export-ready.

Explore recordkeeping
Working with other teams

The record makes the handoffs easy.

Three teams regularly need what yours holds. With the record preserved, each ask becomes a lookup.

Comms leadership

Show the policy at work

When leadership asks how a thread was handled, the actions, reviews and times are already together. Reporting on moderation becomes reading the log, not writing it after the fact.

Records

Answer requests from the archive

Records officers pull the thread as captured instead of asking your team for screenshots. Your part of a FOI request shrinks to pointing at the right conversation.

Legal & risk

Ground disputes in evidence

When a moderation call or a deleted comment is questioned, legal starts from the original content, the action and the time, material designed to support their review.

Straight answers

Community team questions, answered.

If we hide a comment during a pile-on, is it gone?
No. Hiding removes the comment from public view on the platform, but the archive keeps the original comment, the action taken and the time it happened. When the thread calms down and someone asks what was removed and why, you answer from the record instead of reconstructing the night from memory.
What happens when a post is edited after we replied?
Supported edits from connected accounts are captured, so the version you replied to is retained alongside the later one. Your reply keeps its context: you can show what the comment said when you answered it, not just what it says now.
Do we have to pre-approve posts or comments?
No. Nothing in this workflow is pre-approval. Your team publishes and the community comments as normal; customer-configured rules act on supported content on connected accounts after it appears, and authorised users review actions afterwards, releasing false positives and adjusting the rules.
Can records or legal get a thread without us rebuilding it?
Yes. The thread as captured from the connected account, with the original content, any moderation actions and the times attached, can be handed to your records officer or legal team directly. No screenshot folders, no asking whoever was on shift to remember the sequence.
Which platforms and accounts does this cover?
Capture covers supported posts, comments, edits and deletions from the organisational accounts you connect on Facebook, Instagram, Threads, X, YouTube, LinkedIn and TikTok. Moderation applies customer-configured rules to supported content on those connected accounts; it is not designed to track, profile, ban or restrict individuals across unrelated accounts or services.

Run the channels. Keep the record.

See capture, moderation and the handoff on your own channels in a 20-minute walkthrough.