All templates

Automated Community.com Reply Triage

Every morning, WebRun opens Community.com, reads the inbound member replies that arrived overnight, groups them into questions, complaints, and positive feedback, logs each one to an Airtable table with its member and topic, and sends you a short Telegram list of the ones that actually need a human answer today.

Runs on WebRun · Strict Lockdown policy
Every day at 8:00 AM WebRunorchestrates each step
1 Community.com read overnight inbound replies
2 Airtable log and classify each reply
3 Telegram send the triage list
In short

How do I triage inbound replies in Community.com every morning?

WebRun reads your Community.com inbox every morning, groups the overnight member replies into questions, complaints, requests, and fan mail, and logs each one to Airtable with a topic tag. It then sends a Telegram triage list with complaints first, and leaves every suggested reply unsent for a human.

  • Complaints surface first thing instead of hours later
  • Every reply is logged and tagged for trend spotting
  • No message is ever sent to a member without a human approving it

Built for creators · artist teams · DTC brands · community managers

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens dashboard.community.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Community.com - read overnight inbound replies
    community.com
    WebRun in Community.com: read overnight inbound replies
    WebRun opens Community.com to read overnight inbound replies.
    • Open the Community.com dashboard and go to your inbox
    • Read every inbound reply received since the last run
    • Capture the member, the message text, and the broadcast it responded to
    • Skip anything already answered by a teammate
    • Draft a suggested reply for the ones that clearly need one and leave it unsent

    Done when Every overnight reply has been read and left unsent for review.

  3. 2
    Airtable - log and classify each reply
    airtable.com
    WebRun in Airtable: log and classify each reply
    WebRun opens Airtable to log and classify each reply.
    • Open your inbound replies table in Airtable
    • Add one row per reply with the member, the date, and the message
    • Tag each row as a question, a complaint, a request, or positive feedback
    • Add a topic tag so recurring themes are easy to count later
    • Leave the status column set to unanswered

    Done when Every reply is logged and tagged in Airtable.

  4. 3
    Telegram - send the triage list
    telegram.org
    WebRun in Telegram: send the triage list
    WebRun opens Telegram to send the triage list.
    • Send your team a short Telegram triage list
    • Put complaints and time-sensitive questions first
    • Show the count by category so you can see the shape of the morning
    • Note the top recurring topic from the last seven days

    Done when You have today's triage list in Telegram.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
dashboard.community.com
ScheduleRuns automatically on this cadence
Every day at 8:00 AM
DeliveryHow each run's result reaches you
Reply triage list · Telegram
OutputWhat each run produces - A tagged Airtable log of every inbound reply plus a morning Telegram list of the ones that need a human answer, complaints first.
Text
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it text members back on its own?

No. Suggested replies are drafted in Community.com and left unsent. A human reads and sends every message, so nothing goes out to a member without approval.

How does it classify a reply?

It reads the message text and tags it as a question, complaint, request, or positive feedback, then adds a topic tag. You can rename the categories to match how your team already sorts the inbox.

What if a teammate already answered?

That reply is skipped. WebRun checks the live conversation state in Community.com each morning, so anything already handled stays off the triage list.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.