Playbook

Explanation of benefits documents arrive in dozens of payer formats and carry the information that determines whether a claim was paid correctly. This guide covers extracting line-level data reliably, matching to claims and remittances, classifying denials by reason, routing underpayments to follow-up, and why posting to the ledger stays under human control.

Quoting sits between a customer who wants a number and a rating engine that needs complete, accurate risk data. This guide covers capturing risk information conversationally, validating and enriching it, integrating with the rating engine rather than replacing it, handling eligibility and referral rules, and the regulatory boundary that keeps pricing inside filed rates.

KYC onboarding is where regulated firms lose customers to friction and lose examinations to weak evidence. This guide covers document capture and verification, extraction with confidence, screening integration, risk scoring that supports rather than replaces analyst judgement, the perpetual-KYC extension, and the audit evidence an examiner will ask for.

Resume screening is the most regulated AI use case most companies attempt, and the one most often built without knowing that. This guide covers the automated employment decision rules that apply, structuring screening around job-related criteria rather than resemblance to past hires, bias testing across protected groups, notice and human review requirements, and the audit evidence you will be asked for.

Returns are expensive, emotionally charged, and full of policy edge cases that customers experience as arbitrary. This guide covers encoding returns policy as testable rules, deciding eligibility with reasons customers accept, detecting abuse without penalising ordinary customers, automating labels and refunds within limits, and using the conversation to keep the sale where an exchange would serve better.

Transaction monitoring generates more alerts than any team can clear, and the genuine cases sit in the queue behind them. This guide covers using AI to triage and contextualise alerts rather than replace the detection layer, reducing false positives with governance regulators accept, supporting typology detection, building investigator workflow, and the model risk documentation an examination will require.

Booking looks simple and is full of rules: who can be seen by whom, for how long, with what preparation, and what happens when someone cancels at short notice. This guide covers integrating with calendars and scheduling systems, encoding availability and eligibility rules, handling the conversation across channels, confirmations and reminders that reduce no-shows, and rescheduling without creating gaps.

Where is my order is the highest-volume question in commerce support, and answering it well means more than reading a tracking number. This guide covers integrating order management and carrier data, detecting exceptions before the customer notices, communicating delays honestly, offering resolution actions within policy, and handling the cases where tracking data is wrong or missing.

Content moderation fails when policy is vague, automation is trusted too far, or reviewers are treated as a cost line. This guide covers turning policy into a testable specification, tiering decisions by confidence and severity, designing review queues that protect reviewer wellbeing, handling appeals, and measuring the errors in both directions that matter.

Forms are where organisations move information from one place to another by hand, thousands of times a day, and an agent that fills them from source documents and systems removes exactly that work. This guide covers field mapping from a form's schema, sourcing values from documents and records with per-field confidence, validating against rules, confirming with a person before submission, and keeping an audit trail of where every value came from.

Magento runs complex catalogues with attribute sets, configurable products, and multi-store scopes that make automation valuable and error-prone. This guide covers integration tokens and ACL scoping, catalogue enrichment within attribute sets and store views, order and customer service operations, cache and index behaviour that agents must respect, and the workflows worth building first.

A chatbot that works in English and is switched on for other languages usually fails quietly in all of them. This guide covers language detection and switching, whether to translate or generate natively per language, building retrieval and evaluation sets per language, handling mixed-language and code-switched input, and escalating to human agents who speak the customer's language.

Summarization is the most requested and least rigorously built AI capability in the enterprise, because a summary that reads well can still be wrong. This guide covers defining summary types by their use, structuring output for each, handling documents longer than a context window, evaluating faithfulness rather than fluency, and running summarization as a shared service at a cost that scales.

WooCommerce runs a vast number of small and mid-sized stores on WordPress, where the owner is also the merchandiser, the support team, and the operations manager. This guide covers REST API key scoping, product enrichment and inventory workflows, order and customer service support, the plugin and hosting realities of small stores, and keeping writes safe on a live shop.

Image generation is easy to demonstrate and hard to run as a production capability, because the outputs carry brand, legal, and reputational weight. This guide covers constraining generation to brand guidelines, templating prompts so marketers do not write them, review and approval workflows, rights and provenance labelling, safety filtering, and the caching and cost patterns that make generation at scale affordable.

Contentful separates content from presentation through a content model, which gives an agent structured fields to work with and a publishing workflow it must respect. This guide covers the Management and Delivery APIs, grounding in the content model, drafting entries and localisations into the editorial workflow, quality and SEO checks, and why the agent creates drafts rather than publishing.

Figma holds the design system, the product screens, and the handoff artifacts engineers build from, and an agent there can catch inconsistencies no reviewer has time to find. This guide covers REST API and plugin access, design system compliance auditing against components and tokens, accessibility checks, handoff documentation generation, and why the agent proposes rather than edits.

GitLab holds code, pipelines, issues, and deployment in one place, which lets an agent see a change from issue to production. This guide covers merge request review that reads the diff and the pipeline together, pipeline failure diagnosis from job logs, issue triage and linking, project and group access token scoping, and the protected branch and approval rules that keep the agent's contributions reviewable.

Linear is opinionated about how software teams should work, and an agent that fights those opinions gets removed. This guide covers the GraphQL API and webhooks, triaging and enriching inbound issues, linking issues to code and customer context, cycle and project reporting, and the boundary around priority, assignment, and estimates that belongs to the team.

Sentry captures every error but not whether anyone is looking at it, and most engineering teams have a backlog of issues nobody triaged. This guide covers building an agent that reads new issues with their stack traces, breadcrumbs, and release context, proposes root cause hypotheses, routes to the right owner, links related issues, and where appropriate drafts a fix as a pull request for review.

WordPress runs a large share of the web, from small business sites to enterprise publishing, with a REST API and a plugin ecosystem that make agents easy to connect and easy to connect badly. This guide covers application passwords and role scoping, drafting posts and pages into the editorial workflow, content maintenance across large sites, SEO checks, and the security posture a WordPress agent requires.

Datadog holds the telemetry an on-call engineer needs and far more of it than anyone can read during an incident. This guide covers querying metrics, logs, and traces through the API with scoped keys, triaging alerts with correlated context, assembling incident timelines, and keeping the agent's own query load from becoming a cost line or a performance problem.

dbt projects hold the transformation logic, lineage, tests, and documentation that an AI assistant needs to be useful to analytics engineers, in a structured form the assistant can read. This guide covers grounding in the manifest and catalogue, generating models and tests that follow project conventions, documentation generation, impact analysis from lineage, and keeping every generated change reviewable through the normal pull request flow.

PagerDuty is where incidents become people's problems, at three in the morning, with a page and no context. An agent that briefs the responder before they open a laptop is worth more than most dashboards. This guide covers incident enrichment through the API and events, responder briefing, stakeholder update drafting, postmortem timeline assembly, and the boundary around paging, escalation, and resolution that stays with people.