Case study

Zapiens

AI assistant on WhatsApp: directly recognized commands use no tokens; AI responses use the configured key.

ZapiensPreview

Problem

Small file tasks on the phone, like turning a photo into a sticker, merging images into a PDF or converting a document, need a different app for each one. I wanted to handle all of it inside WhatsApp, without paying for AI on every request.

What was built

A personal WhatsApp assistant, integrated with the Evolution API, with a web panel for settings and logs.

  • Static and animated stickers, image conversion and documents to PDF
  • An action menu when a file arrives without a command, listing only the conversions that accept that file type
  • Natural language conversation, with an AI provider configurable in the panel

What sets it apart

Every message goes through a cascade from cheapest to most expensive: direct command, shortcut, menu reply and detection of obvious requests ("make it a pdf", "make a sticker"). AI only steps in for open conversation or ambiguous requests, so most actions spend no tokens at all. The webhook answers right away and processes in the background, so slow AI never blocks WhatsApp.

Outcome

Running on my VPS for personal use, with CI, images published to GHCR and rollback in seconds by version.