Is it safe to automate financial email?

The routine half, yes — telling someone your payment terms is not a financial decision. Keep the other half manual. Disputes, refunds and anything with a contested amount should escalate untouched, which is exactly what the escalation branch is for.

Can it push invoice details into our accounting tool?

Not by itself; there is no accounting integration. The API and MCP server let your own tooling read the classified thread and write into your ledger with server-side permissions, which is the honest version of the same outcome.

Does it chase people for payment?

The agent does not send reminders. It answers billing mail that arrives — where the invoice is, what the terms are, why a card failed — and leaves the dunning to whatever already does it.

Does it handle supplier invoices as well as customer questions?

Both, on separate branches. They arrive at the same address and have nothing else in common, so the first classification step is what makes the mailbox workable.

Can disputes always reach one specific person?

Yes. Routing is a condition you draw, so a dispute can go to a named person every time rather than into a shared queue.

← All use cases

billing@invoices@

Billing and invoice email automation

Billing mail is the most repetitive thing a business receives and the most expensive to get wrong. An agent on billing@ answers the routine half from what you wrote down, and puts anything touching money in front of a person.

What it looks like today

'Where is my invoice' answered by hand, several times a day, with the same three sentences.
A disputed charge sitting unread behind a fortnight of supplier invoices.
Payment questions answered slightly differently depending on who happened to reply.

How the billing@ workflow runs

1
Mail arrives at billing@
Supplier invoices, customer questions, payment confirmations, the occasional dispute. The workflow runs on all of it.
2
It gets sorted by what it is
An invoice arriving is not the same event as a customer asking about one, and a dispute is neither. Each gets its own path, and the paths look nothing alike.
3
Routine questions get the written answer
Payment terms, where to find a receipt, what happens when a card fails — these are already documented somewhere. The agent answers from that document, and stays quiet where the document stops.
4
Anything contested goes straight to a person
Disputes, chargebacks, anything where the amount is wrong. No draft, no attempt. Tag it, notify someone, stop.

What changes

Customers stop waiting two days to be told something your terms page already says.
The same question gets the same answer no matter who is on shift.
Disputes surface immediately instead of ageing behind supplier mail.

Where you stay in charge

Nothing that moves money moves without a person.

The agent answers questions about your billing. It does not make billing decisions, issue credits, or agree to anything.
Disputes and chargebacks leave the automation entirely and arrive with a human, tagged and summarised.
Automatic sending here is worth earning slowly. Answering 'when will I be charged' from your terms is safe; anything that sounds like a commitment is not.

One morning, concretely

A customer asks on Saturday where their receipt went. They have the answer from your own billing page within the minute. The chargeback notice that arrived an hour later is already flagged, unanswered, and waiting for Monday.

Questions people ask

Is it safe to automate financial email?: The routine half, yes — telling someone your payment terms is not a financial decision. Keep the other half manual. Disputes, refunds and anything with a contested amount should escalate untouched, which is exactly what the escalation branch is for.
Can it push invoice details into our accounting tool?: Not by itself; there is no accounting integration. The API and MCP server let your own tooling read the classified thread and write into your ledger with server-side permissions, which is the honest version of the same outcome.
Does it chase people for payment?: The agent does not send reminders. It answers billing mail that arrives — where the invoice is, what the terms are, why a card failed — and leaves the dunning to whatever already does it.
Does it handle supplier invoices as well as customer questions?: Both, on separate branches. They arrive at the same address and have nothing else in common, so the first classification step is what makes the mailbox workable.
Can disputes always reach one specific person?: Yes. Routing is a condition you draw, so a dispute can go to a named person every time rather than into a shared queue.