Why we built an audio guestbook into Poolr
Six months after launching Poolr, a bride named Sarah sent us a message. Her wedding photos were all there, every single one, but what she kept replaying wasn't an image. It was a 40-second voice message from her grandmother, recorded on her phone during the reception, saying things she'd never thought to ask on camera. That message arrived buried in her photo gallery. We realised we'd missed something obvious.
The gap between photos and memory
Photos capture moments. They're essential, irreplaceable. But a photo doesn't hold your uncle's laugh or your best mate's improvised speech or the way your mum's voice shook when she toasted the couple. Those things live in audio. They're hard to capture on purpose, and even harder to find later when they're scattered across different phones and voice memo apps.
When we started building Poolr, we focused entirely on photos because that's what events generate most of. But the customers who came back repeatedly, who said Poolr had changed how they relived their weddings or milestone birthdays, mentioned the same thing: "I wish I'd recorded my dad saying something." Not professionally. Not as a formal video. Just his voice, in the moment, with everyone there.
How it works in practice (and why simplicity matters)
The audio guestbook lives inside Poolr on the Occasion tier and above. Guests scan the same QR code they use to upload photos. Instead of reaching for a camera, they tap the microphone icon and record. No login, no app, no friction. A message might be ten seconds. It might be two minutes. We don't enforce limits because some guests have more to say.
What surprised us during testing was how differently people behaved when they could record audio instead of writing a caption or staging a selfie. One grandmother whispered a blessing in her native language. A best man rambled through three different stories before landing on the one that mattered. A child sang. People were less self-conscious about the audio than they were about appearing in photos. There's something about not being seen that lets people speak more truthfully.
The host's view: curation without gatekeeping
We knew from the start that hosts need control. Not every recording is suitable, and that's fair. So we built a live moderation queue, the same one we use for photos. A message comes in, the host can hear it in real time, and decide whether it goes into the shared album. They're not censoring; they're curating.
This matters because one host told us she had a guest record a message that was clearly meant to be private, an apology or confession meant only for the couple. She held it back, then called that guest to let them know they'd be welcome to share it if they wanted to. That's the relationship we're trying to enable. Not a public broadcast platform. A way to collect something intimate and decide together what to keep.
What happens after the event
Here's where most platforms fail. An event ends. Two weeks later, no one thinks about the temporary upload link or the limited-time album. But Poolr sits on the Occasion tier. The album never expires. Neither do the audio messages.
We've watched people download their album years later, and the first thing they do is replay the audio. A mother listened to a message from her late father-in-law six months after his death. A couple played their wedding audio guestbook to their newborn daughter. These aren't edge cases. They're the whole reason we built this.
If you move up to the Forever tier, face recognition and highlight reels help you relive events too. But the audio sits quietly in the background, available whenever you need to hear a voice again.
Why we don't call it a feature
Most software companies launch features and move on. Audio guestbook is listed on our pricing page, but internally, we think of it differently. It's a permission structure. We're giving guests permission to contribute something other than a photo. We're giving hosts permission to keep something vulnerable and personal inside their own event album, not broadcast it to the internet.
That's why we buried no ads in the player, no share-to-social buttons, no analytics tracking who listened when. It's not a content platform. It's a memory container.
If you've used Poolr to host an event, or if you've ever wished someone had recorded their voice at a moment that mattered to you, you might understand why we built this. The question we keep asking ourselves is: what other things do your guests want to say that aren't photos?