# Cookbooks Overview

> Practical Kommon Poll setup guides for common monitoring programs, team workflows, and reporting use cases.

> Practical Kommon Poll setup guides for common monitoring programs, team workflows, and reporting use cases.

Cookbooks are opinionated, step-by-step recipes. Use them when you know the business situation and want a working setup rather than a feature-by-feature explanation.

Each cookbook includes:

- What the setup is for.
- Which Kommon Poll areas to configure.
- Suggested query and tracking patterns.
- Recommended filters, alerts, reports, and review cadence.
- Best practices and mistakes to avoid.

---

## Choose A Cookbook

| Use case | Start here |
| --- | --- |
| Always-on reputation monitoring for one brand | [Brand Monitoring Cookbook](/cookbook-brand-monitoring) |
| Active incident, reputational risk, fraud, outage, or public backlash | [Crisis Monitoring Cookbook](/cookbook-crisis-monitoring) |
| Regional, city-level, language, or community discussion for a global brand | [Local Discussion Monitoring For Global Brands](/cookbook-local-discussion-global-brands) |
| Comparing your brand against competitors | [Competitor Monitoring Cookbook](/cookbook-competitor-monitoring) |
| Managing many clients, brands, or teams | [Agency Setup Cookbook](/cookbook-agency-setup) |
| Launching a campaign, product, event, or hashtag | [Campaign Launch Monitoring Cookbook](/cookbook-campaign-launch-monitoring) |
| Weekly or monthly leadership reporting | [Executive Reporting Cookbook](/cookbook-executive-reporting) |
| Finding product issues, support themes, and customer feedback | [Customer Experience And Product Feedback Cookbook](/cookbook-customer-experience-product-feedback) |

---

## Core Setup Pattern

Most cookbooks use the same foundation:

1. Confirm the active team.
2. Define the listening goal.
3. Connect or request sources.
4. Build the query with AI Boolean Builder or the manual query builder.
5. Run a Quick Search.
6. Inspect the Mentions tab.
7. Save the project with title, type, description, topics, team, and owner.
8. Add Social Tracking sources where needed.
9. Choose tracking start mode:
   - **Backfill 30 Days** for supported recent-history collection.
   - **From Now Only** for new data going forward.
10. Configure alerts in Notifications Center.
11. Create reusable PDF and Slide formats.
12. Review, tag, respond, export, and share based on the workflow.

---

## Shared Best Practices

- Always check the active team before saving searches or changing settings.
- Use queries for keywords, names, hashtags, and exclusions.
- Use filters for date range, sentiment, source, author, domain, geography, language, demographics, tags, subtopics, intents, reach, and priority.
- Read Mentions before trusting charts.
- Use tags consistently across teams.
- Use **Add to Report** for representative examples.
- Use Kommon Poll AI to summarize filtered context, then verify with charts and mention cards.
- Create saved report formats before recurring reporting starts.
- Keep alert rules narrow enough to be useful.

---

## Recommended Starting Stack

For most mature programs, configure:

- One saved project per major brand, campaign, competitor set, or client.
- Social Tracking for official pages, important hashtags, groups, listings, and review sources.
- Notifications Center rules for critical negative or priority mentions.
- WhatsApp or Slack for urgent operational notifications.
- Email for routine summaries.
- PDF Format for management summaries.
- Slide Format for presentations.
- Full Card Data CSV for analyst investigation.

Start with the cookbook closest to your situation, then adapt the steps to your plan, team structure, and data availability.
