Skip to content
Tensor GardenTensor Garden

AI and automation

Useful AI is a bounded job with a person on the exception.

Routine work handled inside a written boundary, with a person on anything outside it.

Who calls us about this

The situations that usually bring people here.

  1. 01

    The same questions arrive several times a week and need the same document each time.

  2. 02

    Intake, routing and follow-up depend on somebody remembering.

  3. 03

    You want AI in the business but not answering things it should not.

  4. 04

    Staff already use AI tools and nobody has written down what they may read.

One request, bounded, drafted and checked

Step 1 of 5: A question arrives

  1. 01A question arrives

    An ordinary request from a customer, of the kind that arrives several times a week and needs the same document each time.

  2. 02It answers from sources you approved

    The scope is named and written down: these documents and this list, and nothing outside them.

  3. 03You get a draft you can read

    The draft carries the source it used, so a reviewer can check it against that source instead of retracing the whole request.

  4. 04A person checks it before it goes

    Review is part of the path, not an optional extra. The person sending it is accountable for it.

  5. 05Out of scope is labeled and handed over

    A commercial question is not answered by the automation. It goes to a person with the original request attached.

Illustration drawn for this page. The question, the draft and the documents are invented, and no customer data is shown.

We do not publish accuracy or speed figures for this. Those depend on your documents and your process, and we have not measured yours.

What changes

  • A defined scope, written down

    What it answers, what it will not answer, and which documents and systems it is allowed to read.

  • A draft a person can check

    The draft includes the source it used, so a reviewer can check it without retracing the whole request.

  • An exception path with a name on it

    Anything outside scope is labeled and routed to a person with the original request attached.

  • Less routine effort on frontline questions

    Handling many routine questions in the flow of work reduces effort that would otherwise become billable time or consume the support capacity in your agreement.

What it covers

  • Lead and client intake automation
  • Follow-up and communication workflows
  • Document and report generation
  • Help desk and ticket triage automation
  • Knowledge-base and SOP automation

How the work begins, and continues

  1. Name the work and the sources

    The work it would take, the sources it may read and the questions it must hand to a person, in writing, before anything is switched on.

  2. Run it with review in the path

    Drafts carry their source. A person checks before anything goes out, and the exception path has a name on it.

  3. Keep it bounded as things change

    When documents, systems or permissions change, the written scope is revisited rather than assumed.

Scope boundaries

  • It does not replace your staff. Judgment, exceptions and the conversations that need a person stay with people.
  • No accuracy, speed or performance figures are published, because we have not measured your documents and process.
  • Nothing runs on data outside the approved list, and nothing chargeable starts without approval.

How the work is controlled

Your priorities set the work. You approve additional charges before extra work starts.

Priorities are agreed with your leadership first, so a new request has something to be measured against. Nothing chargeable starts before your authorized decision-maker says so.

How we work, in full

Questions on this service

Does this replace our staff?

No. It removes sorting, copying, routing, reminders and documentation work. Judgment, exceptions and the conversations that need a person stay with people.

Why would an IT and software company build our AI?

Because the useful part depends on permissions, integrations, data and the systems underneath. The same team that maintains those can bound the AI to them honestly.

How do we know what it is allowed to see?

The approved sources are listed as part of the work, and the exception behavior is agreed before anything is switched on. We do not publish performance benchmarks for it, because we have not measured yours.

Related services

Links marked ↗ open the live site.

Local pages for this service

Start with a free assessment

A conversation about priorities, a high-level review, and a clear next step. We will tell you whether this service is actually the starting point.