This walkthrough describes how AVA's pipeline handles a renewal in practice — it is illustrative of the process, not a specific named account, since we are still early and building our library of real customer stories.

Monday, 8:14 AM: a renewal notice lands

An email arrives in the connected inbox — a subscription or license renewal, due in three weeks. Under the old process, this sits until someone has time to read it, check the account history, and figure out what to send back. With AVA, the pipeline starts within seconds of the webhook firing.

The read and classify stages

AVA reads the message and produces a structured summary: what is expiring, the due date, and how urgent it is. It is then classified as a renewal (not a new request or an unrelated message) and queued for the next stage.

Memory lookup: recognizing the account

AVA checks stored client and contact records for a match. If this account renewed before, that history — prior terms, past contacts, any notes on file — comes back into the pipeline instead of getting rediscovered from scratch.

Drafting the response

Using the matched template and the account's history, AVA writes a complete draft — not a generic template with blanks, but a response that reflects what is actually on file for that account.

Landing in the review queue

By the time a coordinator opens their dashboard, the draft is already sitting in the queue and in Gmail Drafts. They read it, make any edits, and approve. Nothing goes out until they do.

What this replaces

Without this pipeline, the same renewal requires someone to notice the email, pull up the account separately, draft a response manually, and remember to follow up if there is no reply. AVA does not remove the review step — it removes everything before it.

Have a real renewal workflow you would like to see broken down, or want to share how AVA fits into yours? Tell us about it — we are building out real case studies as more teams come on board.