EN
Idioma · Language · Lingua
Actions with verifiable outcomes.
Conversing is not the same as executing an operation.
Abbi Actions is the Abbiamo.ai catalog of predefined operations: repeatable, with permissions and with an outcome that can be verified. What must come out the same every time lives in an action, not in the conversation. Abbi Actions are defined once in the «Actions» console of Abbi Studio, which only Abbiamo.ai operates. The other consoles can restrict them, never expand them.
-
Abbie
Abbie executes them
Within her degree of autonomy, action by action.
Meet Abbie → -
Caddie
Caddie prepares them
He gets the operation ready for the human agent to authorize.
Meet Caddie → -
Microapps
Action or microapp
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.
See services → -
Abbi Studio
They live in Abbi Studio
Each Abbi Action is defined once in the «Actions» console of Abbi Studio, the main platform.
See the «Actions» console →
Every action, from start to outcome.
Illustrative examples. The names of real actions are published once their status is confirmed.
Five parts, all traceable.
-
Part
Trigger
What starts it: a conversation, an event or a human agent who authorizes it.
-
Part
Permissions
Who can execute it and with what degree of autonomy.
-
Part
Input data
What information it needs and which authorized source it comes from.
-
Part
Verifiable output
What outcome it produces and how it is checked.
-
Part
Record
What is written in the system, with its rule and its source.
Autonomy is earned, action by action.
Each action has its own level. Each higher level limits the one below, and autonomy grows as the results build confidence.
-
Level
Suggests
Abbie proposes the action and a human agent executes it.
-
Level
Executes with confirmation
Abbie executes after a confirmation.
-
Level
Executes on its own
Abbie executes within her mandate and leaves a record.
Consistency, packaged.
The AIE agent decides when to invoke an action; the action defines what happens.
-
Benefit
The same outcome every time
Given the same inputs, an action produces the same outcome and leaves a record.
-
Benefit
Verifiable outcome
What is said to the customer matches what is saved in the system.
-
Benefit
Permissions and limits
Who can execute it, with what degree of autonomy and with what limits on amount, term or executions.
-
Benefit
One catalog for Abbie and Caddie
Abbie executes them; Caddie prepares them for the human agent to authorize.
-
Benefit
On top of what you already have
They are carried out in your system, in a catalog microapp or in a mixed way.
-
Benefit
Evidence for auditing
Every execution leaves its entry in the audit log.
Seven actions to get started.
Collections and support operations with an outcome that can be verified. Abbie executes them within her degree of autonomy; Caddie prepares them for the human agent to authorize. Each one is carried out in your system, in a microapp or in a mixed way.
-
Payments
Generate payment link
Generates a payment link with the amount and reference from the authorized source, and sends it on the customer's channel. Limit: configured maximum amount; never asks for passwords, PINs, CVVs or tokens.
-
Collections
Record promise to pay
Records in the system the date and amount the customer commits to pay, within the approved options. Limit: configured maximum term, no pressure and within permitted hours.
-
Collections
Generate agreement
Generates the agreement with the approved conditions that apply to the case. Limit: it is not closed if a mandatory requirement is missing; an exception requires explicit, traceable authorization.
-
Scheduling
Schedule appointment
Checks availability, schedules, confirms or reschedules the appointment and sends the confirmation. Limit: only time slots available in the system; the confirmed appointment is the one that gets recorded.
-
Support
Create ticket
Creates the ticket with the context of the conversation and provides the tracking number. Limit: the status is reported from the system, not from memory.
-
Documents
Send document
Sends the customer a document, such as a confirmation or an agreement, on the enabled channel. Limit: only current documents approved by the company.
-
Identity
Verify identity
Checks the customer's identity against the authorized source before an operation that requires it. Limit: only the data the process needs; never passwords, PINs, CVVs or tokens.
-
Development
Custom action
For what the catalog doesn't cover and your flow needs in order to close. It is quoted as development and can move into the catalog.
See custom microapps →
Proposed initial catalog. Each implementation confirms which actions are enabled; meanwhile, names and examples are illustrative.
An action from the inside: record promise to pay.
This is what an action's contract looks like before it is enabled. Illustrative example: the real values are defined in each implementation.
- Name
- Record promise to pay (verb + object, unique in the catalog).
- Trigger
- A conversation in which the customer commits to pay, or a human agent who authorizes what Caddie prepared.
- Valid inputs
- Account reference, amount and committed date, taken from the authorized source and from the conversation.
- Outputs
- Status of the promise and record reference number.
- Resolution
- In the client's collections system, in a microapp or in a mixed way.
- Acceptance test
- The promise recorded in the system is the same one the customer heard.
- On error
- If an input is missing or invalid, the action is not executed and the behavior declared in the contract sheet applies.
- Permission
- Abbie executes it within her degree of autonomy; Caddie prepares it and the human agent authorizes it.
- Configurable limits
- Maximum term, amount and executions per contact. Anything that exceeds them is blocked and recorded.
- Autonomy
- It starts at «suggests» and never exceeds the maximum Abbiamo.ai allows for that action.
- Log
- Every execution, authorization, failure or block is recorded in the audit log with its evidence.
Illustrative example. Available actions are confirmed in each implementation.
Several actions, one business outcome.
Abbi Tasks are ordered combinations of Abbi Actions that deliver a complete outcome.
-
Illustrative example
A complete outcome
Receive a patient's test results → record them in their file → notify the physician.
-
Inside Abbi Studio
Abbi Tasks
Its own page: what it is and how it relates to Abbi Actions and Abbi Studio.
Meet Abbi Tasks →
Fact sheet, the contract sheet of each action.
Every catalog action declares its contract before it is enabled.
- Name
- Verb + object, unique in the catalog; for example, «record promise to pay».
- Valid inputs
- The data it needs: amount, reference, email.
- Outputs
- What it returns: link, status, reference number.
- Resolutions
- Client system, catalog microapp or mixed, configured per action.
- Acceptance test
- The expected, verifiable outcome.
- On error
- What happens when the action fails or the input is invalid.
- Permission
- Who can execute it and at what degree of autonomy.
- Configurable limits
- Amount, term and executions per contact.
- Maximum autonomy
- The highest degree Abbiamo.ai allows for that action.
- Log
- The evidence that remains in the audit log.
- Proposed initial catalog
- Generate payment link · record promise to pay · generate agreement · schedule appointment · create ticket · send document · verify identity.
Available actions are confirmed in each implementation.
Pricing, in one place.
The price, a calculator to estimate your month and what is quoted separately are on the pricing page.
-
Pricing
How much it costs
The price of the agent and of usage, on a single page.
See pricing → -
Calculator
Estimate your month
Move the controls to match your operation's volume.
Calculate → -
Contact
Request your quote
Tell us about your process and we will connect you with the right partner.
Let's talk about your operations →
Abbi Actions in your industry, step by step.
Detailed cases with the situation, how it is resolved, the actions, the controls and the verifiable outcome. Illustrative examples.
-
Industry
Banking and financial services
Collections, payment agreements and disputes.
See cases → -
Industry
Insurance and healthcare
Policies, claims, appointments and sensitive data.
See cases → -
Industry
Telecommunications, energy and mining
Support, collections, activations, outage reports and field safety.
See cases → -
Industry
Government and BPO
Procedures, case numbers, quality and after-hours capacity.
See cases →
Abbi Studio, the main platform.
Abbi Studio is the main platform of Abbiamo.ai. Abbi Actions, Abbi Tasks and Abbi Flow live inside it; Abbie and Caddie, the AIE agents, are governed from it.
-
Platform
Abbi Studio
Design the agent: prompt, context and rules. For Abbie, for your platform or for your human team.
Meet Abbi Studio → -
Inside Abbi Studio
Abbi Tasks
Ordered combinations of Abbi Actions that deliver a complete outcome.
Meet Abbi Tasks → -
Inside Abbi Studio
Abbi Flow
Chains «Tasks» into a complete process, with conditions, detours and the point where a person steps in.
Meet Abbi Flow →
Products and services, one shared approach.
-
AIE agent
Abbie
Talks with your customers. Acts in your systems.
Meet Abbie → -
AIE agent
Caddie
Caddie guides you. You decide, within the rules.
Meet Caddie → -
Platform
Abbi Studio
Design the agent: prompt, context and rules. For Abbie, for your platform or for your human team.
Meet Abbi Studio → -
Inside Abbi Studio
Abbi Tasks
Ordered combinations of Abbi Actions that deliver a complete outcome.
Meet Abbi Tasks → -
Inside Abbi Studio
Abbi Flow
Chains «Tasks» into a complete process, with conditions, detours and the point where a person steps in.
Meet Abbi Flow → -
Verifier
Abbi PitWall
Verifies, diagnoses and improves your agents in live operation.
Meet Abbi PitWall → -
Services
Microapps, consulting and implementation
Design and rollout based on a diagnosis.
See services →
Tell us which operation must come out the same every time.
Tell us which process you want to improve.
Let's talk about your operations →or write to us at hola@abbiamo.ai