Was invoice 1042 paid? Celeste can answer your vendors

Somewhere in your accounting inbox right now is an email that says “checking on invoice 1042.” Next to it is one asking for a W-9, and one asking whether you pay net 30 or net 45. Whoever answers these is probably also the person who closes the books, and every one of these emails is a context switch away from that.

This is a use case we built Celeste for, even though most people meet it as a customer service product. A vendor inquiry desk is customer service. The customers just happen to be your suppliers.

What it looks like

You forward your AP inbox (or a dedicated vendors@ address) to Celeste. The agent reads each inquiry, answers what it can, and holds what it should.

Payment status questions get a real answer, not an acknowledgment. Connect your ERP or accounting system as a tool and the agent looks up the invoice and replies with where it stands: received, approved, scheduled, paid on this date, check number if you have one. The part that matters is the scope. A vendor who writes in gets answers about that vendor’s invoices and nothing else. Identity comes first, and every lookup the agent makes is constrained to the requester’s own records by code that runs outside the AI. A supplier can never fish another supplier’s payment terms out of your agent, because the tool call physically cannot return them.

W-9 requests are a fetch-and-send. Payment terms, remittance addresses, PO requirements, invoice submission rules: that is document knowledge. Load your AP policy once and those answers come back consistent, at any hour, with no one retyping them.

What it refuses to wing

Some vendor emails should never get an automated answer, and this is where the product earns its keep.

“Can you pay this early for a discount” is a negotiation. “We’re changing our bank account” is a fraud pattern with a name. You can put phrases like these on an escalation list, and a message containing one is barred from an autonomous reply. It lands in a queue for your team with the trigger flagged. Anything that would change data rather than read it, releasing a payment, updating vendor details, is governed the same way as every write in the product: the agent can draft the action, and it executes only when a person approves, until you have deliberately decided otherwise for that specific tool.

And before the agent answers anything on its own, it practices. Point it at the inbox in shadow mode and it drafts replies silently against your real vendor traffic while you read what it would have said. You graduate topics one at a time: payment status this week, W-9s next, terms questions when you are satisfied. Nothing goes live by default.

Why AP is a good fit

Vendor inquiries are repetitive, well documented, and record-backed, which is the exact profile where an AI desk performs. They are also the queue nobody staffs. Support teams get headcount; the AP inbox gets whoever is closest. Moving the routine half of it to an agent gives your accounting staff back the afternoons currently spent confirming that yes, the check went out Tuesday.

The vendor gets something too: an answer in minutes instead of a reply three days later when someone surfaces from month-end close.

If you want to see the machinery, how it works walks through practice mode, per-topic graduation, and how held actions reach a human. Or look at the product and picture your AP inbox in the queue. The trial runs in shadow mode against real traffic, so you can watch it answer invoice questions before it ever sends one.