How it works

One agent per customer. Asleep until something matters.

An agent is not a program running all day for every customer. It is that customer's memory, goals and rules, kept on file and woken when something about them changes.

The cycle

Remember. Notice. Decide. Learn.

Remember

Every order, visit, ticket, call and message from your systems joins one history for that customer.

Notice

A new event arrives: a complaint, a missed payment, a slowdown, a renewal date. Only the agents it concerns wake up.

Decide

The agent reads its customer's history and chooses one of three things: reach out, brief your team, or wait. It writes down why.

Learn

It records what happened next, and the next decision for that customer starts from there.

Inside one decision

Watch one agent decide.

Dana's internet failed for the third time in three weeks. Step through what her agent did next.

DW
Dana WhitfieldFiber 1 Gig + TV · $129/month · customer for 6 years
SAMPLE DATA

What woke it

Something changed for this one customer.

Event
Third outage in 21 days on her street's node2 h 10 m, 3 h 05 m, 2 h 40 m. All during her working hours.
Call
She phoned support asking about a creditOct 26, 4:02 pm

What it read

14 records from her own history. Nothing from any other customer.

Network outages ×3Support ticketCall transcriptContract: renews in 41 daysUsage: works from homeLast order2023 note: prefers straight answers

What it weighed

Four options. One survived.

Not allowed
Send an apology with a bill creditCredit is a price decision. Your rule keeps it with a person.
Rejected
Send a retention offerA discount before the fix treats a reliability problem as a price problem.
Rejected
WaitRenewal opens in 41 days. Waiting risks the decision being made without us.
Chosen
Brief Jordan with the network ticket and a call planA person calls, confirms the fix date and decides on any credit.

What it checked

Seven checks before anything leaves.

✓Every fact traces to a record
✓Nothing from another customer
✓Nothing stale
✓No false familiarity
✓Contact limits respected
✓No harm to sensitive matters
✓Your rules: price and credit left to a person

What it did

A brief for the person who owns Dana. No message to her yet.

Brief
Call Dana. Confirm the fix date first. Don't lead with an offer.Sent to Jordan Ellis, retention lead, with the network ticket attached.
0.6 cents
AI cost of this decision
Why it can afford every customer

Cheap checks first. Expensive thinking only where it counts.

The design uses simple checks first and reserves deeper analysis for the events that need it.

All customersHistory stored. Storage is the only cost.
0
Something happenedAt least one event arrived
0
Simple checks flaggedFast rules, no AI
0
Agent wokeA low-cost model kept it; the agent reads everything
0
Reach out0messages drafted or sent
Brief the team0handed to a person
Wait0chose to do nothing yet
Illustrative monthly AI cost, model calls only$0about 1.3 cents per customer

Illustrative figures for one month at a company with 48,212 customers, from the Keepara demo workspace.

Integrations

Keepara reads every system that knows your customer.

CRM, customer data platform, billing, support, orders, bookings and more. Keepara joins them into one history for each customer, and writes back only to the few tools that act.

Direct connectors

Keepara reads from each system through its own API, with the fields and permissions you approve.

Warehouse or CDP

One connection to Snowflake, Databricks or your customer data platform covers many systems at once.

Files

Scheduled CSV or Excel exports over secure file transfer, for systems without an open API.

Keepara API

Send events straight to Keepara and receive its decisions through webhooks.

Core customer systems

CRM

Accounts, contacts, owners and open deals.

  • Sales Cloud
  • Dynamics 365

Customer data platforms

Unified profiles, events and segments.

  • Data Cloud
  • Real-Time CDP

Billing and subscriptions

Renewal dates, failed payments and plan changes.

  • Billing

Payments

Charges, refunds and disputes.

  • PayPal

Customer support

Open tickets, escalations and satisfaction scores.

  • Customer Service

Customer success

Health scores, success plans and business reviews.

  • Gainsight
  • Totango

ERP

Orders, shipments, returns and invoices.

  • S/4HANA
  • NetSuite
  • Dynamics 365 Business Central

Industry systems

Hotels and travel

Stays, bookings, cancellations and guest preferences.

  • OPERA Cloud
  • Mews
  • Cloudbeds

Banking

Accounts, balances and the products a customer holds.

Insurance

Policies, claims and renewals.

  • Guidewire
  • Duck Creek

Telecom

Plans, usage, bills and network issues.

  • CSG

Industrial equipment and distribution

Service visits, contracts and installed machines.

  • Field Service
  • ServiceMax

Executive coaching

Sessions, notes and client goals.

  • Simply.Coach
  • CoachAccountable

Commerce

Orders, purchase rhythm and refunds.

  • Shopify
  • Commerce

Signals around the customer

Marketing and messaging

Campaigns, opens and unsubscribes. Keepara can hold a campaign for one customer.

  • Klaviyo
  • Marketing Cloud

Product usage

Logins, feature use and drop-off.

Feedback and reviews

Surveys, scores and public reviews.

  • Medallia

Contact center

Calls, call reasons and transcripts.

  • GenesysCloud CX
  • NICECXone
  • Five9

Email and chat

Threads between your team and the customer.

  • Gmail
  • Outlook

Meetings and calendars

Meeting dates and agreed summaries.

  • Calendar
  • Gong

Notes and documents

Account notes and contracts.

  • OneNote
  • Drive

Data and plumbing

Data warehouses

Customer tables, read where they already sit.

  • BigQuery

Integration platforms

Any system not listed here, through the tools you already use.

  • Workato

Sign-in

Your team signs in with the company login.

  • Entra ID

Files

Scheduled exports, picked up on a timetable you set.

  • CSV
  • Excel
  • SFTPSecure file transfer

Keepara API

Send events in. Get decisions out.

  • REST API
  • Webhooks

Reads Where the history lives

  • Sales and orders: point of sale, ecommerce, order management
  • Operations: ERP, billing, bookings, service and work orders
  • Customer records: CRM, customer data platforms and loyalty programmes
  • Conversations: support tickets, contact center, email
  • Product and usage data: app events, network data, machine telematics

Writes Where decisions land

  • A brief or a task in the CRM, for the person who owns the customer
  • A hold on the marketing tool's list, so a campaign skips this customer for now
  • A drafted message, sent through your own tools after approval
  • A ticket when something needs fixing first

Why it must write at all

Deciding to wait only works if the agent can stop the campaign that is already scheduled. A read-only agent can advise. It cannot hold anything back.

Warehouse first

Larger companies often gather their data in one warehouse or customer data platform already. One connection there covers many systems. Direct connections add the real-time events a warehouse delivers late.

The hard part: who is who

The same customer appears in different systems under different names, emails and numbers. Merge two people by mistake and the agent speaks to one using the other's history. Matching comes before everything else.

Your systems

Running something else? We build it with your team.

We are happy to work with your tech team and build the integrations you require, from a homegrown database to an industry system we have not listed.

Talk to us about your systems
Trust and control

It suggests first. You widen what it may do.

Autonomy is a setting for each kind of action, off by default. You grant it one action type at a time, and only you can widen it.

  • Every decision is logged with its reason and the records it rests on.
  • Every fact in a message must trace back to a record. If it can't, the message is blocked.
  • Nothing about one customer can appear in another customer's message.
  • Price, credit, complaints and anything regulated stay with a person.
  • One switch stops all agents at once.
Questions

Questions people ask.

Do customers talk to the agent?

No. The agent works for your team, behind the scenes. Customers hear from your company, in your voice, through the channels you already use.

Does it replace our CRM or marketing tools?

No. Keepara decides; your existing tools keep sending and recording. It sits on top of what you run.

Will it message customers without our approval?

Not unless you decide it can, for a specific kind of message. It starts by suggesting, and a person approves.

What happens to our customer data?

The design keeps each company’s customer records separate. Access, retention and data handling requirements are agreed for each deployment.

Get in touch

No one wants to be a number in your database.

In 30 minutes, I’ll walk you through a customer example from your industry. We’ll discuss where it could help your team.