Playbook

Freshdesk holds the ticket queue, the knowledge base, and the customer history an agent needs, which makes it a good platform for support automation and an easy one to do badly. This guide covers API integration, triage and response drafting, grounding answers in knowledge articles, escalation design, and measuring resolution rather than deflection.

monday.com runs operational processes across sales, marketing, HR, and delivery in boards that each team shapes for itself. This guide covers the GraphQL API and column model, permission scoping, the intake and reporting workflows worth automating, and how to build an agent that survives the board changes teams make constantly.

Notion holds the documentation, project trackers, and operational databases that internal AI agents need, in a structure that is flexible enough to be inconsistent. This guide covers API integration, working with Notion's block and database model, permission scoping through integration access, and the internal workflows that pay back.

Airtable holds the operational databases that fall between spreadsheets and real systems, which is exactly where manual work accumulates. This guide covers API integration and schema handling, rate limit design, the record maintenance and intake workflows worth automating, and how to keep an agent working when the base schema changes underneath it.

Asana holds the work itself, which makes agents there useful for intake, status, and reporting and dangerous if they start reassigning people's tasks. This guide covers API and webhook integration, working with Asana's project and task model, the intake and reporting workflows that pay back, and where an agent should stop and ask.

Intercom sits in the product where customers are already stuck, which makes its agents higher-leverage and higher-risk than a ticket queue. This guide covers API and webhook integration, conversation state, grounding answers in help content and product data, handover to teammates, and measuring resolution rather than containment.

Dynamics 365 sits on Dataverse, which gives agents a clean data surface and a security model expressive enough to scope them properly. This guide covers integration through Dataverse and the Web API, security role design, the sales, service, and finance workflows worth automating first, and how to build without creating upgrade debt.

Sage runs the finance function for a large share of mid-market companies, where teams are small and exception work eats the month. This guide covers integration across Sage Intacct and Sage 200, permission scoping, the workflows that pay first in a lean finance team, and the audit controls that keep the ledger defensible.

Xero's API is one of the cleanest in accounting software, which makes agent work straightforward and shifts the difficulty to workflow design and controls. This guide covers OAuth and rate-limit handling, the bookkeeping and advisory workflows worth automating, how practices serve many clients from one build, and the controls that keep the ledger defensible.

Zoho runs sales, support, finance, and operations for a large number of small and mid-sized businesses from one suite, which makes cross-application agents unusually valuable. This guide covers OAuth scoping across the suite, the CRM, Desk, and Books APIs, the cross-app workflows that pay first, and the controls a lean business needs without an enterprise programme.

Oracle ERP Cloud exposes good integration surfaces, which makes agent work more straightforward than in older estates and no less consequential. This guide covers REST and BI Publisher integration, role and data access security, the exception workflows worth automating first, and the audit controls a financial system demands.

SAP holds the transactions that matter, which makes it the highest-value and most carefully governed place to put an AI agent. This guide covers integration options across S/4HANA and ECC, authorisation and segregation of duties, the workflows that pay first, and the controls an SAP estate demands.