About Zellbox
Zellbox turns your appointment book into a WhatsApp-native command center — automating reminders, confirmations, deposits, and recall cycles for appointment-driven small businesses.
What we make
Zellbox is a WhatsApp-first calendar and customer record system for small businesses that run on appointments — dental and private clinics, physio and mental-health practices, aesthetic clinics, beauty salons, barber shops, spas, veterinary clinics, and fitness studios. Every reminder, confirmation, deposit request, and recall nudge lives on the same WhatsApp thread the customer already messages you on.
We also handle send-and-sign consent flows (send a consent PDF, patient signs on WhatsApp, signed file lands on the patient record with an auditable trail — GDPR / LOPDGDD ready), deposit collection against Stripe to reduce no-shows on high-value appointments, and species-aware recall cycles for veterinary clinics running vaccination + antiparasitic protocols.
Why it exists
Appointment-driven small businesses lose 15–25% of revenue to no-shows and unrecovered recalls. Existing tools force a four-tool stack — one booking app, one CRM, one WhatsApp Business inbox, one payments gateway — with the operator wiring the connections manually. The customer ends up with a fragmented conversation across SMS, email, and WhatsApp, and the operator ends up with data trapped in four silos.
Zellbox unifies the four into a single workspace where WhatsApp is the primary channel, not an SMS afterthought. One calendar, one customer record, one WhatsApp thread per customer, one payments flow.
Who runs it
Zellbox is built and operated by the team at Blockchain Web Services (BWS), with Nacho Coll as principal. BWS is an AI-native solutions factory that ships production-ready software across a portfolio of products — Zellbox is one of them, alongside IPFS.NINJA, OpenAgile.AI, WallaWhats, Badges.ninja, Blockchain Database, NFT.zK, and Telegram XBot. The operating principle is Demand Becomes Product: engineered by people, accelerated by AI, accountable end-to-end — every line of code owned by a named engineer.
The founding team has been building on AWS since 2007 (Enterprise Architect work for LEGO, Nordea, Vueling and others) and building WhatsApp Business platforms since 2020. Zellbox launched in 2026 to give appointment-driven SMBs a WhatsApp-first calendar and customer record system that treats WhatsApp as the primary channel rather than an SMS afterthought — because every existing tool we evaluated for prior client projects treated WhatsApp as an add-on to an SMS-first stack.
The blog you’re reading is part operations documentation, part operator’s notebook. Some articles are drafted by an AI assistant (using the content-generation workflow described in editorial process) and reviewed by the team before publication; others are written end-to-end by hand. Every WhatsApp template body cited in an article is verified against the approved templates in production before it ships.
How we use AI in our content
Some blog posts on this site are drafted by Claude (Anthropic’s AI assistant) using a prompt that ranks topics by underserved-search-intent for the SMB verticals we serve, drafts the article body with required practical structure, and emits FAQPage JSON-LD. The BWS team then reviews the draft, verifies every WhatsApp template body against the approved production templates, fixes any factual errors, and approves publication. Articles that pass this review carry the byline “Nacho Coll” and include a disclosure paragraph.
This is disclosed per Google’s helpful-content guidance, which asks that “appropriate use of automation/AI-generation is self-evident to visitors through disclosures”. We agree.
Reach us
- Email — hello@support.zellbox.com
- Source code — github.com/blockchain-web-services
- Status — coming soon
Editorial standards
We don’t accept paid placements, sponsored posts, or affiliate links. Comparison articles (e.g., “Callbell vs Zellbox for clinics”) are written with explicit prices and feature counts from the competitor’s public documentation, and we link to their site so readers can verify the facts themselves. If you spot an inaccuracy in any post, please open an issue at our GitHub or email hello@support.zellbox.com — we’ll correct it and add an editorial note.
