The problem with renewal inboxes

A typical renewal inbox on a Monday morning is a mess of unrelated messages — expiration notices, subscription reminders, compliance alerts — arriving at random times, from random senders, in random formats. Someone has to read each one, figure out what it actually needs, look up the account it belongs to, and write a response. That is the work AVA was built to own.

AVA does not just skim the inbox. Every incoming email runs through a defined pipeline — the same stages, every time, with a full record of what happened at each one.

Stage 1: Read

When a new message arrives in the connected Gmail inbox, AVA reads it and produces a structured summary: what it is about, what action it needs, when it is due, and how urgent it is. This turns an unstructured email into data every later stage can use.

Stage 2: Classify

Next, AVA decides what kind of email this actually is — a renewal, a new request, a status check, or something unrelated that does not need a response at all. Anything that is not renewal-related gets set aside here; AVA does not force every message into its pipeline.

Stage 3: Memory lookup

For anything that is a renewal, AVA checks your stored client, contact, and asset records for a match. This is what lets it recognize this is the same account that renewed last year instead of treating every email as a first contact.

Stage 4: Select a template

AVA picks the response template that fits — based on the type of renewal and whatever tone or format you have configured for your account.

Stage 5: Log the transaction

Before any draft gets written, the transaction is logged. This is the audit trail — every renewal AVA touches has a record, regardless of what happens to it next.

Stage 6: Draft

This is where the actual writing happens. AVA combines what it read, how it classified the email, what it found in memory, and the selected template into a complete draft response.

Stage 7: Push to your review queue

The finished draft goes into your UNIT dashboard and into Gmail Drafts — not your Sent folder. It is ready to read, edit if needed, and approve.

The human gate

AVA never sends an email. That is not a limitation — it is the design. Every draft waits for you to review it. Approve it and it is ready in Gmail for you to send yourself; reject it and it is removed. The pipeline handles the repetitive work; the decision to send stays with a person.