Process automation

Connecting existing systems, preparing work for review and handling exceptions.

AI content quality at volume: expertise in, drafts out

A cheap draft can be expensive to approve. Put the expertise in before the machine writes, let deterministic checks and a critic reject what fails, and measure cost per approved article.

Read the guide
Expertise in, drafts outA brief with facts, sources and positions feeds a draft. The draft passes through a gate of deterministic checks and a critic pass. Failures loop back for at most two revision rounds. What passes goes to a named person for approval, and only approved articles publish. Conceptual illustration.BriefFactsSourcesPositionsReaderDraftChecksphrases, shapesCriticanother modelApproveRevise, at most two roundsRejected, with a reasonExpert work happens before the draft existsMeasure: cost per approved article, rejected drafts included
Expertise in, drafts out

The expert's work is finished before the machine writes. The checks and the critic run before any person reads, and the person's decision comes last and is recorded.

Technical SEO and AI search optimization: turn visibility into qualified demand

Fix the crawl and index faults first, write pages that people and AI assistants can read, cover the searches your main site was never built for, and judge the work by qualified enquiries.

Read the guide
From a search to a qualified enquiryThree stages in a row: a search result page with an AI answer, your page with the answer at the top, and an enquiry form. Below them, three bars shrink from 2,000 visits to 20 enquiries to 8 qualified enquiries. This is a conceptual illustration using the article's worked example, not customer data.AI answerAnswer firstSend enquirySearchYour pageEnquiry2,000 visits20 enquiries8 qualifiedEach step gets its own numberIllustrative figures
From a search to a qualified enquiry

The count shrinks at each step, so each step needs its own number and its own owner. The figures are the article's worked example, not a result.

Native AI assistants for business software: guide first, then act

An assistant inside the software people already use can show where a setting lives, prepare the change and apply it after confirmation. Measure the work finished, not the messages exchanged.

Read the guide
An assistant panel inside the application, next to the record it will changeA business application window with a navigation column, a page editor showing a welcome page with an SEO title field, and an assistant panel on the right. The panel proposes a new SEO title, shows before and after, and offers apply and cancel. A badge on the editor says the role was checked by the application. Conceptual illustration.PagesMediaSettingsUsersWelcome pageHeadlineSEO titleWelcome to our storeBodyAssistantChange the SEO title?BeforeAfterOur store, open 24 hoursApplyCancelRole checked by the app
The assistant works beside the record

It sees the page the person has open, proposes a change with before and after, and the application checks the role and writes only after apply.

Multi-brand service desk automation: one desk for several customers

Service desk tools assume one company. When one team serves several brands, the gaps show up as leaked context, missed SLAs and duplicate work. Here is how to close them, and what AI makes routine.

Read the guide
Separate customer views over one shared queueThree customer portals, for brand A, brand B and brand C, sit side by side at the top with dashed walls between them. Each connects down to one shared staff queue in the middle, which connects down to a delivery teams panel at the bottom. The walls end at the queue: records and notifications stay separate per brand, while people and process are shared, and delivery teams see the work without the customer. Conceptual illustration.Separate per brand: requests, files, notifications, identityBrand ABrand BBrand COne staff queueShared people, triage rules and reviewDelivery teamsSee the work, without the customer
Where the walls stop

The walls between brands run through the portal, search and notifications. They stop at the queue, because the saving of a shared desk comes from sharing the people and the process.

Automated resolution rate: measuring support AI by outcomes

A bot can answer more conversations while your agents get harder work. Measure verified resolution, safe escalation, repeat contact and the cost per resolved case before you trust the headline rate.

Read the guide
From all contacts to billed resolutionsA ledger of four bars. All contacts, 10,000. The bot took part in 6,000. 3,000 were contained, meaning the customer stopped asking. 1,500 were verified as resolved. A bracket shows that the blended rate counts contained and verified together, 50 percent of the bot's conversations, while billing counts verified only, 25 percent. Conceptual illustration with assumed figures.One month, assumed figuresAll contacts10,000Bot took part6,000Contained3,000Verified1,500Blended rate50%Billed25%Both rates divide by the 6,000 conversations the bot handled
Two rates from the same month

The blended rate counts contained conversations, where the customer stopped asking, together with verified ones. The invoice counts verified only, so the dashboard can show double the billed rate.

Assess Aigentcy with your assistant.

Copy our summary prompt or open it in your preferred service. Check the response against the sources.

Read the prompt

Links open an external AI service with this public prompt. Sign-in and prefill behaviour vary. If needed, paste the copied text.