Skip to content Abbie, AIE agent by Abbiamo.ai
EN

Idioma · Language · Lingua

Service E · Custom microapps

When your tools fall short, a custom microapp.

Abbie · speaking
A microapp is a targeted application, connected to your systems.
Let's talk about your process How we work
01What it solves

A step that must come out the same every time and your tools can't achieve it.

Some flows don't close consistently: there is no system that provides it, or the system exists but doesn't allow connections. That is where a microapp comes in.

  • Starting point

    Starting situation

    A step in your flow must come out the same every time, and the tools you already have fall short.

  • Who it's for

    Companies that are held accountable

    Corporations in regulated industries, BPOs and service providers, always through a partner.

  • Action or microapp

    They complement each other

    An action is a catalog operation. A microapp is a custom application for when your tools fall short; an action can be delivered with a microapp.

    Explore the actions →
02What is delivered

A microapp, with the same contract sheet as an action.

We explain which problem each microapp solves and which systems it connects to. Its contract sheet declares the same things as any catalog action.

Problem it solves
The step in the flow that needs consistency and why current tools fall short.
Connected systems
The systems you declare as authorized sources for each data type.
Name
Verb + object, unique; for example, «record promise to pay» (illustrative example).
Inputs and outputs
The data it needs and what it returns: a link, a status or a reference number.
Acceptance test
The expected, verifiable outcome: what is recorded matches what is expected.
On error
What happens when the input is invalid or the operation fails.
Permission and autonomy
Who can use it and the maximum degree of autonomy you accept for it.
Configurable limits
Amount, term and executions per contact.
Log
The evidence of each execution in the audit log.

Acceptance criteria are set in each project.

03How we work

From the problem to a verifiable microapp.

Abbiamo.ai develops the microapp, because every microapp ends up published as an Abbi Action.

  1. Step

    Define the problem

    Which step needs consistency and why your tools fall short. Before building, we check whether the Abbi Actions catalog or your system already solves it.

  2. Step

    Define the contract sheet

    Inputs, outputs, acceptance test, behavior on error, permission, limits, maximum autonomy and log.

  3. Step

    Build

    On the same action layer and with the same data and compliance rules as the AIE agents (Cognitive Autonomous Intelligent Entities).

  4. Step

    Connect

    With your connected systems. The operation is carried out in your system, in the microapp or in a mixed way.

  5. Step

    Close and decide

    At closing, an explicit decision is made on whether the microapp stays exclusive to your company or goes into the catalog.

04What it ends in

Working in your environment, not in a document.

  • Outcome

    A microapp in operation

    Connected to your systems and with its complete contract sheet.

  • Outcome

    A test passed

    What the microapp records matches what is expected, and evidence remains.

  • Outcome

    An explicit decision

    Exclusive to your company or part of the catalog, agreed at the close of the project.

05Rules that don't change

Tailor-made, with the same rules.

  • Rule

    Same data rules

    A microapp that handles payments or personal data follows the same data and compliance rules as the AIE agents: PCI DSS requirements for payments and each country's data protection regulations.

  • Rule

    Minimal data

    Only the data the process needs. Never passwords, PINs, CVVs or tokens.

  • Rule

    Protected credentials

    The credentials for each connected system are stored encrypted and are never displayed.

  • Rule

    Graduated autonomy

    Abbie uses it within her degree of autonomy; Caddie prepares it and the human agent authorizes it.

  • Rule

    Only what is confirmed

    No microapp is presented as available until it is implemented. Examples are marked as illustrative.

  • Rule

    No generic timelines or rates

    Scope, timeline and cost are defined per project. The quote comes through your partner.

06Keep exploring

Seven offers, one shared approach.

Which step in your flow must come out the same every time?

Tell us about your process and we will connect you with the right partner.

Let's talk about your operations

or write to us at hola@abbiamo.ai