The problem
This county library network runs eight branches and somewhere around sixty programs a month. Toddler story time, senior tech help, resume workshops, maker nights for teens. Genuinely useful stuff, mostly free, mostly empty seats.
Announcements went out through whatever librarian had a spare minute. A Monday morning Facebook post here, an email blast there. One branch announced its tax prep workshop four days after it happened. Attendance hovered near ten percent of capacity network wide and kept dropping, which the budget committee interpreted as falling demand.
It was not demand falling. It was awareness.
What Zyren found
The network connected its social accounts and event calendar to Zyren, and the analysis flipped the assumption. Across all branches, local engagement peaked weekday evenings between six and nine, plus Sunday late afternoon. Most library posts historically went out weekday mornings, written and scheduled whenever staff wrapped opening tasks.
Worse, roughly forty percent of posts duplicated each other. Two branches announcing different events within the same hour buried both.
How Zyren helped
Every event announcement now goes into Zyren once. The tool schedules each post per branch for peak windows, staggers overlapping announcements, and repeats reminders leading up to the event automatically.
Week 1: All event posts moved to evening and Sunday windows. Week 2: Reminder sequences configured. Each event now gets an announce post, a reminder two days out, and a morning-of nudge. Week 4: Staff stopped manually posting entirely. Social media duty dropped to reviewing drafts. Week 8: Attendance figures started arriving and the network did the math twice to be sure.
The results after 2 months
- Event attendance doubled across the network
- Tax prep workshop filled all thirty seats with a waitlist
- Teen maker night grew from six attendees to consistent twenties
- Social media duty for staff fell from hours weekly to under thirty minutes
- The budget committee proposal to cut weekend hours was withdrawn
What didn't work
Fully automating tone was a mistake early on. One reminder for the grief support circle read like a flash sale announcement. Staff now tag sensitive events so Zyren sends a single gentle reminder or none at all.
What they'd do differently
"We assumed empty rooms meant nobody cared. Turns out everybody cares and nobody knows. It was a timing problem the whole time."
Next steps
The network wants Zyren to coordinate cross branch promotion, so each branch's strongest events get promoted through neighboring branches' channels on a rotating basis.