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

Idioma · Language · Lingua

Enterprise AI solutions

Complete processes, from start to finish.

Abbie · speaking
Sales, customer onboarding, products, scheduling, support, disputes and collections, 24 hours a day.
01Strategy, security and compliance

AI that is accountable is designed, protected and demonstrated.

Before the process, what supports it: why we exist, how we protect every operation, which standards we follow and where your data lives.

  • AI strategy

    The why comes first

    The belief, the six hows with their proof, what we sell and how to start with a first flow.

    See the strategy →
  • Security

    Bounded, traceable mandate

    «Actions» with limits no one expands, conversation locks, data isolated per client and change control.

    See security →
  • Regulation and compliance

    Built for those who are held accountable

    The standards we follow from the design stage, those of each industry and the decisions that always belong to your institution.

    See the standards →
  • Data sovereignty

    Your data, where your case requires

    Four deployment levels, from the cloud to your premises, and five questions to choose.

    See the levels →
02How the work is divided

People, AIE agents and systems, each doing their part.

Every solution divides the work the same way: an AIE agent is left with what requires judgment; what must come out the same every time lives in a system; and the last word is human.

  1. Person

    Decides what matters

    Keeps the decisions that require judgment, empathy and responsibility, and receives the full context when a case escalates.

  2. AIE agent

    Converses, decides the next step and acts

    Abbie executes within her mandate; Caddie guides and prepares so the human agent can authorize.

  3. System

    Keeps what must come out the same

    Amounts, deadlines, policies and records live in the company's systems and in Abbi Actions.

03Eight solutions

Each solution starts from a typical process. We adapt it to yours.

Eight processes we know well. Each one is designed on a base process and adapted to your rules, your sources and your operations.

  • Who: Abbie + Caddie

    Sales

    A typical five-step process and what is adapted in each implementation.

    See the process →
  • Who: Abbie

    Customer onboarding

    A typical five-step process and what is adapted in each implementation.

    See the process →
  • Who: Abbie + Caddie

    Product specialist

    A typical five-step process and what is adapted in each implementation.

    See the process →
  • Who: Abbie

    Scheduling

    A typical five-step process and what is adapted in each implementation.

    See the process →
  • Who: Abbie + Caddie

    Support and customer service

    A typical five-step process and what is adapted in each implementation.

    See the process →
  • Who: Abbie + Caddie

    Disputes and complaints

    A typical five-step process and what is adapted in each implementation.

    See the process →
  • Who: Abbie + Caddie

    Collections

    A typical five-step process and what is adapted in each implementation.

    See the process →
  • Who: Caddie + Abbi PitWall

    Quality, supervision and training

    A typical five-step process and what is adapted in each implementation.

    See the process →

Illustrative example; adjusted in each implementation.

—Who: Abbie + Caddie

Sales: a typical process.

Adapted with: suitability rules per product · authorized cross-selling · connection to your CRM. The closing, and whatever the law reserves for a licensed professional, is handled by your advisor.

  1. Step 1

    Receives the prospect's interest

  2. Step 2

    Qualifies: need, profile and budget

  3. Step 3

    Explains and quotes with approved prices

  4. Step 4

    Gathers the documents

  5. Step 5

    Schedules the closing with a licensed advisor

Illustrative example; adjusted in each implementation.

—Who: Abbie

Customer onboarding: a typical process.

Adapted with: your compliance team's checklists · electronic signature · requirements by account or policy type.

  1. Step 1

    Verifies identity

  2. Step 2

    Reviews the requirements

  3. Step 3

    Receives documents through a secure channel

  4. Step 4

    Validates the information

  5. Step 5

    Records the onboarding and notifies the customer

Illustrative example; adjusted in each implementation.

—Who: Abbie + Caddie

Product specialist: a typical process.

Adapted with: catalog by customer segment · your own comparison tools · what must never be said.

  1. Step 1

    Identifies the product of interest

  2. Step 2

    Answers with the current product sheet

  3. Step 3

    Compares options

  4. Step 4

    Answers questions

  5. Step 5

    If it goes beyond what is approved, follows the configured route

Illustrative example; adjusted in each implementation.

—Who: Abbie

Scheduling: a typical process.

Adapted with: prerequisites for the appointment · multiple locations or specialists · waiting list.

  1. Step 1

    Identifies the customer

  2. Step 2

    Checks the real schedule

  3. Step 3

    Schedules, changes or cancels

  4. Step 4

    Confirms the appointment

  5. Step 5

    Sends the reminder

Illustrative example; adjusted in each implementation.

—Who: Abbie + Caddie

Support and customer service: a typical process.

Adapted with: diagnostics per product · service levels by customer type · closing survey.

  1. Step 1

    Receives the request

  2. Step 2

    Classifies it

  3. Step 3

    Runs a guided diagnosis

  4. Step 4

    Resolves it or opens a ticket

  5. Step 5

    Follows up until closure

Illustrative example; adjusted in each implementation.

—Who: Abbie + Caddie

Disputes and complaints: a typical process.

Adapted with: deadlines by country and regulator · reports for the regulator · escalation to an internal committee.

  1. Step 1

    Receives the complaint

  2. Step 2

    Identifies the customer and classifies it

  3. Step 3

    Opens the case number with the regulator's deadline

  4. Step 4

    Follows up

  5. Step 5

    Notifies the resolution

Illustrative example; adjusted in each implementation.

—Who: Abbie + Caddie

Collections: a typical process.

Adapted with: contact hours permitted by law · strategy by delinquency bracket · restructuring agreements.

  1. Step 1

    Identifies the debt

  2. Step 2

    Notifies the customer

  3. Step 3

    Offers the authorized plan

  4. Step 4

    Records the promise to pay

  5. Step 5

    Reminds and follows up

Illustrative example; adjusted in each implementation.

—Who: Caddie + Abbi PitWall

Quality, supervision and training: a typical process.

Adapted with: your quality criteria · training plans per human agent · connection to your quality tools. Development, not surveillance.

  1. Step 1

    Listens to the interaction

  2. Step 2

    Measures against your criteria

  3. Step 3

    Diagnoses what failed or what is missing

  4. Step 4

    Proposes the adjustment or the training

  5. Step 5

    Checks that it worked

Illustrative example; adjusted in each implementation.

04Solutions by function

Choose a process and see how it is resolved.

The actions come from the proposed initial Abbi Actions catalog; each implementation confirms which ones are enabled.

Collections

Reminders, promises, payment agreements and payments with firm, respectful treatment, during the hours regulations permit.

Marco Each market's collections rules; for example, those of CONDUSEF in Mexico and the FDCPA / Regulation F in the United States.

Abbie

Reminder and promise to pay

Situation

A customer has a payment about to fall due or already past due.

How it is resolved

  1. Abbie introduces herself as the company's artificial intelligence assistant and verifies identity.
  2. She checks the balance in the collections system, which is the authorized source.
  3. She offers only the approved options and records the promise or generates the payment link.
Abbi Actions
Verify identity · Record promise to pay · Generate payment link
Controls
Permitted hours · No pressure or threats · Does not make up amounts, deadlines or rates
Verifiable outcome
The promise the customer heard is the one recorded in the system.
Abbie + Caddie

Payment agreement with mandatory requirements

Situation

The customer asks for a payment agreement that requires conditions before it is signed.

How it is resolved

  1. Abbie verifies which approved agreements apply to the case.
  2. If the case exceeds her mandate, she hands it to a person with the full context.
  3. Caddie prepares the agreement and blocks the closing if a requirement is missing; the human agent authorizes.
Abbi Actions
Generate agreement · Send document
Controls
Requirements verified before closing · Exceptions only with explicit, traceable permission
Verifiable outcome
Every agreement has its evidence: conditions, authorization and document sent.

Support

Initial diagnosis, tickets and follow-up with patience, approved procedures and the real status in the system.

Marco Approved procedures only; escalation to a person with the full context.

Abbie

Reporting a fault

Situation

A customer reports that a service is not working and wants to know what comes next.

How it is resolved

  1. Abbie checks the service status in the connected systems.
  2. She applies the approved procedure for the initial diagnosis.
  3. She creates the ticket or schedules the visit and provides the tracking number.
Abbi Actions
Create ticket · Schedule appointment
Controls
Approved procedures only · Escalates with the full context
Verifiable outcome
Every reported fault has a ticket, a tracking number and a record.
Abbie

Ticket follow-up

Situation

The customer asks again about an open case.

How it is resolved

  1. Abbie verifies the customer's identity.
  2. She reports the status from the system, not from her memory.
  3. If the committed deadline has already passed, she transfers to a person.
Abbi Actions
Verify identity · Create ticket
Controls
Distinguishes what is confirmed from what is pending confirmation
Verifiable outcome
What is reported matches what the system says.

Customer service

Inquiries, disputes and requests resolved with current information and a person available when needed.

Marco Minimal data; notice of AI assistance, recording and transcription according to each country's regulations.

Abbie

Inquiry about requirements or conditions

Situation

A customer asks what they need for a request or what a service includes.

How it is resolved

  1. Abbie answers from the current documents the company approved.
  2. She sends the information on the contact channel the customer chooses.
  3. If the question exceeds her mandate, she hands the conversation to a person on the team.
Abbi Actions
Send document · Create ticket
Controls
Sources with a validity period · Does not create new conditions or policies
Verifiable outcome
Every answer can be traced back to the document that produced it.
Caddie

Guided dispute

Situation

A customer doesn't recognize a charge; the human agent must follow the procedure.

How it is resolved

  1. Caddie gathers the context the human agent has access to and recommends the next step, with its source.
  2. He keeps the checklist of the current procedure.
  3. He prevents closing the interaction without the dispute reference number.
Abbi Actions
Create ticket · Verify identity
Controls
Closing blocked without a reference number · The human agent keeps the conversation and the decision
Verifiable outcome
No dispute is closed without its ticket and its reference number.

Scheduling

Appointments, confirmations and changes at any time, against the real availability of the schedule.

Marco Consent and contact notices according to each country's regulations.

Abbie

Scheduling or rescheduling an appointment

Situation

A customer wants to schedule, confirm or change an appointment outside office hours.

How it is resolved

  1. Abbie checks availability in the scheduling system.
  2. She schedules, confirms or reschedules and sends the confirmation with what to bring.
Abbi Actions
Schedule appointment · Send document
Controls
Only time slots available in the system · Identification as AI
Verifiable outcome
The confirmed appointment is the same one recorded in the schedule.
Abbie

Reminder and confirmation

Situation

An appointment is approaching and the company wants to reduce no-shows.

How it is resolved

  1. Abbie sends the reminder on the enabled channel.
  2. She records the confirmation or reschedules if the customer asks.
Abbi Actions
Schedule appointment
Controls
Permitted contact hours · Minimal data
Verifiable outcome
Every confirmation or change is recorded in the schedule.

Onboarding

Customer onboarding and first steps with identity, documents and conditions verified before activation.

Marco Identity verification and document retention according to each market's industry regulations.

Abbie

Onboarding assistance

Situation

A new customer needs to complete their onboarding and doesn't know what is missing.

How it is resolved

  1. Abbie explains the steps and the current list of documents.
  2. She verifies identity and sends the documents for signature.
  3. She reports progress from the system until the onboarding is complete.
Abbi Actions
Verify identity · Send document
Controls
Never asks for passwords, PINs, CVVs or tokens · Minimal data
Verifiable outcome
Every onboarding shows what was received, what was validated and when.
Caddie

Activation with requirements

Situation

An activation requires verifying identity, documents and conditions before it goes live.

How it is resolved

  1. Caddie keeps the activation checklist and prepares the operation.
  2. He alerts when a document or a verification is missing.
  3. The human agent authorizes the activation; Caddie does not execute it for them.
Abbi Actions
Verify identity · Send document
Controls
Incomplete activations blocked · Exceptions with explicit permission
Verifiable outcome
No activation goes live without its requirements verified.

Quality and supervision

Evaluation of interactions with evidence and a clear view of risks for supervisors.

Marco No sanction or final score without human review.

Caddie

Quality evaluation with evidence

Situation

The quality team needs to review more interactions without losing judgment.

How it is resolved

  1. Caddie evaluates eligible interactions with the company's quality rubric.
  2. Every evaluation carries its evidence and is checked against human review.
  3. Learnings are applied only when a person approves them.
Abbi Actions
Create ticket
Controls
Rubric defined by the company · Human review
Verifiable outcome
Every evaluation has its evidence and its review.
Caddie

Real-time supervision

Situation

A supervisor needs to know where to step in during operations.

How it is resolved

  1. Caddie shows them the interactions, their risks and when to step in.
  2. He alerts when an interaction drifts from the procedure.
Abbi Actions
Create ticket
Controls
Permission-based visibility · The decision belongs to the supervisor
Verifiable outcome
Every alert and every intervention is recorded.

On-the-job training

Specific feedback at the close of each interaction and an onboarding mode for new human agents.

Marco Training is based on the company's current procedures.

Caddie

Feedback at closing

Situation

A human agent finishes an interaction and wants to know what to improve.

How it is resolved

  1. Caddie delivers specific feedback with the source of the procedure.
  2. He points out what was done well and the next step for improvement.
Abbi Actions
No actions required: it is feedback
Controls
No final sanctions without human review
Verifiable outcome
Improvement rests on evidence, not impressions.
Caddie

Onboarding new human agents

Situation

A newly hired human agent handles their first cases.

How it is resolved

  1. Caddie activates onboarding mode: he guides each step and explains why.
  2. He blocks the critical steps they have not yet mastered.
Abbi Actions
The same Abbi Actions, prepared for the human agent to authorize
Controls
Mandatory steps blocked · Growing human agent autonomy
Verifiable outcome
The new human agent operates with the right procedure from day one.

Illustrative examples, not existing deployments. The actions, channels and systems in each case depend on the implementation.

05Limits that travel with every solution

What no process can relax.

Hiding that it is AI, stating things without a source, making up conditions, asking for credentials, applying pressure or learning on its own: six locks fixed in the entity that no client, deployment or configuration level can relax.

  • Security

    The locks, one by one

    Together with the bounded mandate of Abbi Actions, data isolated per client and change control.

    See the locks →
  • Compliance

    Each industry's standards

    Banking, insurance, healthcare, telecommunications, energy, mining, government and BPO.

    See the standards →
06Next step

From the process to operations.

  • Industries

    Cases by industry

    Banking, insurance, healthcare, telecommunications, energy, mining, government and BPO.

    See industries →
  • Services

    Design the process

    Process consulting ends in a design ready to implement.

    Process consulting →
  • Pricing

    Packages and billing

    Implementation, capacity and metered usage, through your partner.

    See pricing →

Tell us which process you want to solve.

Your request goes to the partner assigned to your company.

Let's talk about your operations

or write to us at hola@abbiamo.ai