Siftsy Docs
Team Guides

Siftsy for PR and Communications

Siftsy helps PR and communications teams monitor public response, catch emerging issues early, and back up reporting with real audience language. This guide walks through how to use Siftsy across the communications workflow, from message testing to crisis monitoring to stakeholder reporting.


Before the launch – test your message

Use Siftsy to understand how audiences react to your spokespeople, campaigns, and announcements so you can refine messaging before going wide.

Steps:

  1. Upload recent posts from your brand, past campaigns, or spokesperson accounts

  2. Create an analysis filtered to those posts

  3. Explore the comments to see the exact words audiences use when they react

  4. Check the Breakdown section for personality or tone-related themes – are people responding to the message itself or focused on the messenger?

  5. Use the keyword filter to search for mentions of specific messaging terms or product claims

What to look for:

Recurring language patterns in how people describe your brand or campaign. Are they using your intended language, or something else entirely? Note the gaps between what you say and what they repeat back.


During the launch – monitor in real time

As announcements go live, track audience response across owned, earned, and influencer posts. Watch for early signals that your brand monitoring tools might miss.

Steps:

  1. Create a campaign for the launch or announcement

  2. Upload all relevant posts – press coverage, creator reactions, owned channels, and any viral shares

  3. Create an analysis filtered to the campaign

  4. Resync posts regularly during the launch window to pull in new comments

  5. Explore the comments and search specific questions like "What questions are people asking?" or "Is anyone raising concerns?"

  6. Watch the Breakdown for emerging themes and tone patterns – look for emotional spikes, coordinated criticism, or unexpected conversation drift

What to look for:

Audience questions that aren't being answered, sentiment shifts that indicate confusion or frustration, and any themes gaining traction that weren't part of your planned message. Comment sections often surface frustration that never makes it into mention alerts.


Crisis monitoring – catch issues early

When a situation develops, use Siftsy to spot emotional spikes, coordinated criticism, and language patterns before they escalate.

Steps:

  1. Create a dedicated campaign for the issue or incident

  2. Upload all relevant posts – brand responses, news coverage, creator reactions, and any viral threads

  3. Check sentiment and tone in the analysis – look for rapid shifts from neutral or positive to negative, angry, or mocking

  4. Use keyword filters to track specific concerns, complaints, or language patterns that keep appearing

  5. Watch the Breakdown for themes like "customer service complaints," "product issues," or "brand authenticity" that signal the conversation is moving beyond the initial incident

What to look for:

Spikes in negative sentiment, recurring complaint themes, and the specific language people are using to express frustration. This gives you time to respond before a story leaves the platform, and gives you verbatim examples to take to stakeholders.


After the launch – report with evidence

Back up your post-campaign reporting with real comment data – the specific reactions, recurring themes, and audience language that tell the story behind the metrics.

  1. Use groups within your campaign to organize posts by channel type, message, or spokesperson

  2. Compare Sifty Scores across groups to see which execution drove the strongest response

  3. Explore the comments to find recurring themes and standout quotes

  4. Export the full analysis as a PDF or Word document for stakeholder decks

  5. Copy specific comments or insight summaries to paste into reports and presentations

What to look for:

Exact audience language you can quote directly – not just sentiment scores, but the themes and verbatim reactions that show how your message actually landed. This is what turns reporting from "overall positive" into something a stakeholder can understand and act on.

Was this helpful?