Founder, Zellbox

Nacho Coll

I build software for the front desks of clinics, salons, vets, and other appointment-driven small businesses — where a missed reminder is the difference between a profitable month and a red one.

LinkedIn Read the blog Email me

Role: Founder
Years building: 15+

Motivation

Why I built this

The product, the blog, and the company exist to fix one specific problem: visit-driven small businesses run customer communication across three disconnected surfaces.

Every appointment-driven business I'd seen up close ran customer communication across three uncoordinated surfaces: a WhatsApp Business app on the receptionist's personal phone, a Gmail inbox the practice manager half-tended, and a Google Calendar that nobody synced back to either of them. The next no-show, the next missed follow-up, the next "didn't get the reminder" — every one of those incidents had a footprint in at least two of those three places.

Existing CRMs didn't fit. The big horizontal ones (HubSpot, Salesforce) bill per seat and assume a sales pipeline. The vertical ones (Doctolib, Calendly, scheduling SaaS) own the booking layer but leave WhatsApp, email, and signed consent outside the platform. The WhatsApp-specific ones (Callbell, Wati) own messaging but don't know what an appointment is. There wasn't a CRM built for a clinic's front-desk reality where all three of those streams collide on the same customer record.

Zellbox is my answer — built for clinics, salons, vets, fisio, aesthetics, and any other appointment-driven small business where the same person at the front desk handles WhatsApp, email, and scheduling in parallel.

I write as many of the Zellbox blog articles as I can fit alongside the product work — the rest are written by the team and edited by me before shipping. Every post starts from a specific operational problem — no-shows on Mondays, last-minute cancellations the week of a treatment package, vaccination recall campaigns, signed consent for an aesthetic procedure, multi-staff ownership of one WhatsApp number — and proposes a concrete workflow we've already shipped in the product. We draft with AI assistance for structure, then rewrite, verify the sources, and ship. Nothing on the blog is an unreviewed AI dump.

Before Zellbox, I built and ran cloud infrastructure for Blockchain Web Services — the parent company that operates Zellbox. I've worked across product, engineering, and enterprise cloud delivery for ~15 years, including cloud-adoption work at Fortune-Global-500-scale businesses in the Nordics. The full work history is on LinkedIn.

What I'm working on

The three threads that keep me at the keyboard most days. Each one shows up in the product and on the blog.

Three messaging surfaces, one history

WhatsApp on the receptionist's phone. Gmail in the practice manager's tab. Google Calendar wherever the team scheduled it. The same customer is buried in three places. Zellbox keeps the WhatsApp Business number active where it already is (Meta Coexistence) and stitches Gmail + Calendar threads into one record per customer.

Built for visit-driven businesses

Clinics, salons, vets, fisio, aesthetics, dental, optometry, mental-health practices, tutoring centres, fitness studios, driving schools — anywhere the calendar drives the revenue and a 15-25% no-show rate quietly decides whether the month closes profitable. Meta-approved reminder templates ship on day one, plus a shared inbox so the whole team works from one record per customer.

Calm software for busy front desks

Zellbox is opinionated about what NOT to do. No automation traps. No marketing-spam upsells. No per-seat pricing that punishes you for adding a second receptionist. One predictable plan, predictable Meta charges, free Starter forever. The same product the team would want to use ourselves.

Get in touch

If a specific clinic / salon / vet workflow isn't on the blog, or if you'd like to talk about your current stack and where Zellbox fits, the fastest channels are below.

Looking for something specific? Try the full blog or the About Zellbox page for the company-level background.