My favorite part of Claritysoft is how flexible the custom‑field setup is, and it fits our broadcast‑media workflows perfectly at Munich Broadcast Studio GmbH. As part of my daily job, I track lots of unique information for podcast guests and advertising partners, and standard CRM tools rarely let you adjust record structures the way you actually need. I can build dedicated custom fields to capture GDPR‑critical information, such as whether an interview guest has given permission to go on air, consent dates using our local DD.MM.YYYY format, interview progress and recording‑related notes. Operating in Germany, we must be ready to show proof of participant consent whenever required, so having this information sitting directly on each contact record saves me so much prep work before every recording. I no longer need dig through old emails and messy spreadsheet cells to hunt for consent confirmation. The tagging feature is another huge plus. I can sort contacts into clear groups including podcast guests, advertising prospects and freelance audio contractors. When we kick off a new podcast series, I filter contacts by tags and export targeted CSV lists to feed into our evasys survey tool for post‑interview feedback. I also appreciate its granular permission controls. Only three of us on the team hold active login accounts. I manage the admin configuration, while two other colleagues have limited access to update records. The rest of our staff never get into the CRM backend, which keeps sensitive personal guest data safe and aligns with our GDPR requirements. All of these are real‑world workflows working with actual interview guests and business partners from our Munich studio, not fake demo test data. Review collected by and hosted on G2.com.

Claritysoft handles our core contact‑tracking needs well for our small broadcast studio, but I keep running into real practical pain points in my day‑to‑day work. First, its built‑in reporting is pretty inflexible. Even though I have created many useful custom fields for guest consent, interview status and recording timestamps in DD.MM.YYYY format, combining data from these custom fields inside a single report is awkward. For instance, I cannot quickly pull one unified report showing all podcast guests who provided broadcast consent within a specific time range. My workaround is to pull a basic filtered contact view, export everything as CSV, then build the full report manually in Microsoft Excel. This extra sorting and arranging eats into my working hours, and there is always some risk of copy‑paste mistakes. Besides that, automated reminders cannot connect to my custom fields. Notification alerts only work with Claritysoft’s default system date fields. If I input a follow‑up date inside one of my media‑related custom fields, the tool will not send me any reminders at all. So I have to manually copy those important dates over to standard date fields or keep a separate external task list. When our recording schedule gets really packed, I might miss some follow‑up tasks for a couple of business days. These are not hypothetical issues. These are consistent frustrations I experience working with real guest and advertiser records for our Munich‑based podcast and radio productions. Review collected by and hosted on G2.com.