Designing a WhatsApp-first appointment system for Mexican clinics
A clinic does not need another chatbot. It needs a complete appointment workflow that handles language, calendars, exceptions, privacy, and human escalation.
Field notes
Practical thinking on broken workflows, useful automation, reliable software, and the work required after launch.
Built by LOJIK
We built these for ourselves first. What we build for you is shaped around your business.
Things we build


Intertitle development preview · demo profile

LOJIK One development preview · sample client data

Temper development preview · synthetic dataAI can compress implementation time. The real advantage is giving experienced builders more time for workflow design, testing, and accountable delivery.
Read entryA practical delivery loop for turning one broken workflow into reliable software, clear ownership, and a supported launch.
Read entryIf sending the email is all your form does, a missing API key deletes the submission. Separate capture from notification and you lose an alert, not a lead.
Read entryIf the limiter runs before validation, a visitor's typos spend their allowance and the next correct submission is dropped. Check order decides who pays.
Read entryA camelCase column breaks every insert with PGRST204, and Supabase's new API keys are not JWTs. Neither mistake has to surface as an error in your app.
Read entryMotion and visual polish can earn attention, but conversion depends on clarity, useful hierarchy, fast performance, and an obvious next step.
Read entry