Operations

Supplier mail is the queue nobody owns

Every organisation has an address that suppliers write to, and in most it is the same address customers use. The mail has no owner, no service level and no visibility, and the two things in it that matter - a payment query and a delivery problem - look exactly like the cold approaches surrounding them.

Three kinds of mail, one inbox, very different costs

A payment or invoice query has a deadline and a relationship behind it. A delivery or stock problem is operational and usually urgent to someone downstream. A cold approach has no cost at all if it waits a month. Treating all three as one queue means the third sets the tone and the first two inherit its response time.

What can be published, and it removes most of the volume

Where invoices should be sent and in what format. Which reference must appear on them. The payment terms and the payment run schedule. Who to contact about a delivery discrepancy. Where new supplier approaches should go instead of the general address. Five facts, and the payment-run one answers the single most common chase before it is sent.

What must never be confirmed automatically

Whether an invoice is approved, when it will be paid, what was agreed, or anything about a contract. Those are commitments, and a confident answer creates an expectation the organisation may not meet - which is a commercial dispute rather than a support ticket. Pointing at the published terms is honest; confirming a payment date is not.

Separating the queue is the whole win

Classifying an incoming message as payment, operational, or new approach, and recording it with the sender and the reference, turns one undifferentiated inbox into three with different urgencies. Nothing needs to be answered automatically for that to pay for itself - the sorting is the value, and today it is done by whoever happens to open the mail.

Frequently asked questions

What should an organisation publish for suppliers?
Where to send invoices and in what format, the reference required, the payment terms and payment run schedule, who handles delivery discrepancies, and where new approaches should go. The payment-run schedule alone removes most of the chasing mail.
Can an assistant confirm when an invoice will be paid?
No, and the design should forbid it. A payment date is a commitment, and a confident answer creates an expectation that becomes a commercial dispute if missed. Pointing at the published terms is honest; naming a date is not.
Why separate supplier mail from customer mail at all?
Because a cold approach that can wait a month shares a queue with an invoice query that cannot, and with a delivery problem someone downstream is already blocked on. Undifferentiated, the cheapest mail sets the response time for the expensive mail.
What is the measurable benefit?
Not messages answered - messages correctly routed, and the share of chasing mail that stops arriving once the payment-run schedule is published. We will not quote a figure; count your own invoice chases for a month either side.
Which languages can suppliers write in?
Hebrew with full right-to-left layout, English and Russian, detected from what is written. It matters for sorting: a payment query written in a second language is described approximately, and an approximate description is what gets filed as a cold approach.

Get in touch

Leave your details and we will reply. You do not need a sales call to get an answer.