Practical notes from the engineers who build agents, copilots and AI products.
Copilots that act, retrieval over the customer's data and natural-language reporting are the features users pay more for. A chat box over your help centre is not one of them. The tier holds when the feature removes recurring work inside the customer's own records and is priced with its running cost known.
Australian clients overlap with IST mornings, get fixed-price programs and ownership terms designed for distant teams. Sydney's afternoon is Bengaluru's morning: three to four shared hours a day; Perth shares most of it. The rest runs on written hand-offs, demos in your hours and a contract handing over everything.
AI collections combine reminder calls and WhatsApp with payment links, within RBI conduct rules and consented communication. The agent handles early-bucket reminders, promises to pay and payment links; hard cases and disputes go to people, every contact is logged, and calling hours and frequency are enforced in code.
Chatbots are cheap because they do little; agents cost more because they integrate, act and are evaluated; compare on resolution, not price. A chatbot answers from a knowledge base. An agent reads the account, takes gated actions and is measured per intent, which is where budget and value both sit.
Log inputs, outputs, model version, user and reviewer for every automated decision in an append-only store auditors can query. Add the prompt version, retrieved sources, policy checks and the action taken, keep it for the retention period your regulator sets, and make sure a non-engineer can reconstruct any decision.
Agents replace brittle screen-scraping RPA where judgement is needed; keep RPA for fixed, structured steps with no API and no ambiguity. Most estates end up with both: agents deciding and coordinating, RPA bots executing the last mechanical step into a system that has no other door.
Chatbots answer; agents act. Choose an agent when the job has steps, tools and decisions, and a chatbot when it is pure Q&A. The test is simple: if the person who does this work today opens other systems and makes choices, you need an agent. If they only look things up and reply, a chatbot is enough.
Lead routing, claims triage, invoice exceptions, onboarding, support, collections, scheduling, reporting, reconciliation and research are agent-ready today. Each has a clear goal, systems with APIs, decisions that mostly follow written rules, and a human who can approve exceptions while the agent proves itself.
Buy the sprint when you need an outside benchmark, speed and someone accountable for the answer. Run it in-house when you already have an AI engineer with evaluation experience, unrestricted data access and ten uninterrupted days to give them. First-timers should buy; experienced teams should build.