Brendan Caulfield
Lead Chatbot Architect
"A chatbot is not a product you ship once. The maintenance schedule matters more than the launch date."
About Piscandolu
Chatbot work
Chatbot work
that keeps running
Piscandolu handles the ongoing maintenance and updates your chatbot actually needs — the kind of work that happens after the launch, when real usage starts uncovering gaps.
Based in Sarnia, Ontario, Piscandolu has been working with businesses that depend on conversational tools to handle real customer interactions, not just demos.
Who we are
Maintenance
Maintenance
is the job
Most chatbot problems don't show up at launch. They appear three weeks later, when an edge case breaks a flow, or a software update silently changes how an API responds. Piscandolu was built to catch those things early.
The work is specific — reviewing conversation logs, patching intent recognition failures, updating response content when business conditions change, and testing across connected platforms after every update cycle.
We document every change made and what triggered it. Over time that record becomes useful — patterns emerge, and recurring issues get addressed at the root rather than patched repeatedly.
Regular updates
Intent libraries and response content updated on a fixed schedule, not just when something breaks.
Platform monitoring
Active watching across connected services — Messenger, WhatsApp, website widgets, and custom API endpoints.
Change documentation
Every modification logged with context — what changed, why it changed, and what it replaced.
Issue root causes
Recurring failures get traced back rather than patched — fixing the pattern, not just the symptom.
Structured sessions available
For teams that want to understand their chatbot's maintenance requirements — or manage parts of it internally.