AI Agents & Chatbots
Answers your customers get at 2am.
WhatsApp, website and social DM bots trained on your actual business - pricing, availability, policies and documentation - so they resolve enquiries rather than routing them to a queue.
Scoped against the work you already do
How we think about it
A chatbot is only as good as what it knows. We build on your real content - the price list, the service pages, the policy documents, the FAQ your team answers daily - and we make the boundaries explicit, so the bot says it will fetch a person instead of inventing an answer. That single rule is the difference between a bot that helps and one you switch off after a month.
The bot usually sits on a site we built and writes into a CRM we automated, which is why it can check live availability instead of promising a callback.
What this covers
The work, specifically.
- 01
WhatsApp AI bots
Lead replies, bookings and FAQs on the channel most customers already use.
- 02
Website chatbots
Trained on your own documentation, with a clean handoff to a human when it does not know.
- 03
Instagram and Facebook DM automation
First replies and qualification in the DMs, so enquiries do not go cold overnight.
- 04
Customer support agents
Tier-one resolution with escalation rules you set, and transcripts your team can review.
- 05
Appointment booking
Checks real availability and writes to the real calendar, rather than emailing a request.
- 06
Internal knowledge bots
HR policies, SOPs and document search for your own team.
Need AI Agents & Chatbots for something specific?
Tell us what you're trying to ship and we'll say plainly whether this is the right service for it — including when the answer is no.
How it runs
The same four steps, whatever we're building.
No account-manager relay. The lead on your project is someone who builds, and they stay on it from the first call to the last deploy.
Scope
A week of hard questions. We map what you actually need and say plainly which parts we'd cut.
Prototype
Something real in front of you early, not a document about it. Opinions get cheaper.
Build
Two-week cycles, a demo at the end of each. You see progress, not status reports.
Hand over
Documentation, a walkthrough, and the keys. Support if you want it — never as a hostage.
Questions
The things people ask before they enquire.
It depends on scope, but we will give you a number before you commit to anything. Most engagements start with a paid discovery — a fixed fee, a week or two — which ends in a written scope and a real budget. If the budget does not work, you leave with the scope document and no obligation to continue.
A typical first ship is around six weeks. Larger builds run in two-week cycles after that, each ending in a demo of something that actually runs. You will know within the first cycle whether the timeline is holding, rather than finding out near the deadline.
The people you meet. The lead on your project is someone who builds, and they stay on it from the first call to the last deploy. There is no account manager relaying messages between you and an unseen team.
You own everything — code, assets, accounts, domains. We hand over with documentation and a walkthrough, and your team can run it without calling us. If you would rather we stayed on for maintenance or a next phase, that is a separate agreement, not something buried in the original contract.
Yes. Most of our work is remote, and we keep a few hours of overlap with your working day for calls. Timezone has not been the hard part; unclear scope has.
Where it meets the others