G32CONTENT

Brand monitoring and reputation tracking

Continuously watches where the firm and its products get mentioned across public sources — news, social, review sites, podcasts, industry forums — classifies each mention by sentiment, topic, and influence, and surfaces what needs attention. Different from a generic mention-tracker because the pattern weights mentions by source authority and audience reach, distinguishes real reputational signals from noise, and routes the few mentions that genuinely need response to the right team. The pattern's value is ensuring that the firm sees what's being said about it without anyone needing to scroll through hundreds of low-signal mentions to find the meaningful ones.

WHERE THIS FITS

BUSINESS SHAPES

B2B servicesProduct companyDirect-to-consumerNon-profit / mission-driven

VOLUME THRESHOLD

Below 50 monthly brand mentions a month, the payback rarely earns the build. Patterns this shape reliably pay back at 1,000+.

REQUIREMENTS · 7 REQUIRED

Requirements describe capabilities the pattern needs in your environment, not the vendors you must buy. Any system that fills a requirement satisfies it — that’s what makes the catalog portable across the long tail of SMB tooling.

mention_source_feeds
REQUIREDREADbatch
The streams of public mentions the pattern monitors.
DATA SHAPE
Per-mention: source, URL, content, author, timestamp, optionally engagement metrics from the source.
COMMONLY FILLED BY
- social listening tool feeds
- news monitoring service
- review platform feeds
- podcast mention monitoring
- industry forum monitoring
brand_entity_definitions
REQUIREDREADcorpus
What counts as a mention of the firm. Disambiguation matters: 'Apple' the brand vs. apple the fruit.
DATA SHAPE
Brand and product names with disambiguation hints, alternative spellings, related entities (executives, products).
COMMONLY FILLED BY
- entity configuration maintained by communications team
- structured brand monitoring rules
- trained classifier for disambiguation
source_authority_scoring
REQUIREDREADcorpus
How influential or reputation-relevant each source is. Lets the pattern prioritize a tier-1 publication mention over a random blog mention.
DATA SHAPE
Per-source: authority score, audience reach estimate, industry relevance, historical credibility.
COMMONLY FILLED BY
- source authority database from a monitoring vendor
- structured authority list maintained by PR or communications
- external authority signals (domain authority, publication tier)
response_routing_destination
REQUIREDWRITEevent
Where mentions needing action go: PR for press, customer success for customer complaints, executive team for high-stakes issues.
DATA SHAPE
Per-mention requiring action: classification, suggested handler, urgency, suggested response approach.
COMMONLY FILLED BY
- communications team workflow
- alert routing to PR, customer success, executive team per type
- structured response workflow per mention category
reputation_dashboard_destination
REQUIREDWRITEevent
Where the ongoing landscape view lives for the communications and executive team to consult.
DATA SHAPE
Aggregate views: sentiment trend, share of voice, top mentions, emerging topics, period-over-period changes.
COMMONLY FILLED BY
- communications team dashboard
- executive reputation summary
- weekly brand health digest
crisis_escalation_route
REQUIREDWRITEevent
When a mention signals genuine reputational risk — viral negative thread, factually wrong public report, regulatory mention — route to crisis communications immediately.
DATA SHAPE
Crisis alert with full context, propagation estimate, suggested immediate actions, escalation path.
COMMONLY FILLED BY
- direct alert to communications lead and executive team
- structured crisis communications workflow
- phone and chat escalation for severe events
signal_false_positive_loop
REQUIREDREAD + WRITEevent
How communications team flags noise vs. real signal, used to tune classification.
DATA SHAPE
Per-flagged-mention: was it really relevant, was the sentiment right, was the urgency right.
COMMONLY FILLED BY
- dismissal reasons captured in the routing destination
- weekly review session with communications
- thumbs feedback on each routed item

RUNTIME FLOW · 8 STEPS

01
Continuously ingest mentions from source feeds
mention_source_feeds
02
Filter to actual brand mentions using entity definitions and disambiguation
brand_entity_definitions
03
Score each mention: sentiment, topic, source authority, audience reach
source_authority_scoring
04
Classify into action categories: needs response, monitor, ignore
DECISION Three branches plus a crisis override for severe events.
05
Route mentions needing response to the appropriate destination with suggested handler and approach
response_routing_destination
06
If a mention triggers crisis criteria (severe sentiment + high reach + spreading), escalate immediately
crisis_escalation_route
07
Update reputation dashboard with current state and trends
reputation_dashboard_destination
08
Capture false-positive feedback for tuning
signal_false_positive_loop

EMISSIONS · 3

Structured outputs this pattern produces. Other patterns and client systems can subscribe to them, which is how the catalog composes over time.

brand_health_signal
Aggregate sentiment, share of voice, and topic trends over time. The headline reputation view.
CONSUMED BY
- communications leadership
- executive brand reviews
- investor relations narrative
competitive_share_of_voice
Where competitors are getting attention and where the firm is, by topic.
CONSUMED BY
- competitive intelligence
- marketing strategy
- executive market reviews
issue_propagation_signal
Tracking how specific narratives spread, useful for both proactive management and post-incident analysis.
CONSUMED BY
- crisis communications
- PR strategy
- comms team retrospectives