Give accounts@ the same order as your support queue.

Operations and accounts teams live in shared inboxes: accounts@, billing@, invoices@, ops@, suppliers@. Solves turns each of those addresses into owned tickets, so every query has a single owner, a status and a clear history, instead of sitting unread because everyone assumed someone else had it.

The work is different from frontline support, but the failure mode is identical. A customer asks where their invoice is, a supplier chases a payment, a colleague forwards a query about a refund, and all of it lands in one mailbox that three or four people half-watch. Things get answered twice, or not at all, and at month end nobody can say who dealt with what.

Solves fixes that by making ownership explicit. A ticket is assigned, worked and closed by one named person, with private notes for the back and forth that should never reach the customer, and a metadata-only history of every change. The shared address stays exactly as your customers and suppliers know it; what changes is that it is now accountable.

The core change is ownership. When a message arrives at accounts@, Solves creates a ticket and you assign it to one person. From that point it has a state, open, pending, closed, a priority you can raise for an overdue payment or a dispute, and tags such as invoice query, refund, supplier or month end, so you can find and filter the work that matters.

Saved queue views for the finance cycle

Finance work runs on a cycle, and your queue should reflect it. Save the views you return to: everything open and assigned to you, everything tagged month end, everything pending a customer reply, or everything breaching its SLA. Each saved view is a filter you name once and reuse, so the morning routine is one click rather than a fresh search.

No more double-answered or dropped queries

Because a ticket has one owner, two people do not reply to the same supplier with different answers, and a query does not sit untouched because each person assumed a colleague had it. If someone is off, you reassign their open tickets in seconds and the history travels with the ticket, so the new owner has the full picture.

Most businesses do not have a single inbox. They have support@ for customers, accounts@ for billing, and often ops@ or a supplier address as well, and a group of brands may multiply that several times over. Solves handles all of them in one organisation. Each address is a brand mailbox with its own sender name and signature, so an accounts reply looks like accounts and a support reply looks like support.

Separate where it matters, shared where it helps

You decide who sees what. Finance can have its own view of accounts@ while the support team works the customer queue, and a manager can see across both. Lightweight collaborators can be limited to private notes only, so a colleague can weigh in on a disputed charge without ever being able to send a customer reply. Per-brand access keeps the boundaries clear without an enterprise role builder.

Contact history across the relationship

When a customer who has both bought from you and queried an invoice writes in, their history is grouped by brand, so the accounts team sees the billing thread and the support team sees the support thread, and nobody sees history they are not permitted to. One organisation, many brands, the right context in front of the right person.

Accounts inboxes are repetitive in a way that suits saved replies perfectly. The same handful of questions recur: a customer cannot find an invoice, a supplier wants your remittance details, someone needs to update a card, a buyer asks for a VAT receipt. Writing each answer from scratch wastes time and invites small errors in the details that matter most in finance.

Scoped to the accounts brand or shared

A saved reply in Solves can belong to a single brand or be shared across the organisation. That means your accounts team keeps its own library, with the correct bank details, the right tone and your standard wording, separate from the support team's saved replies, while genuinely common answers can still be shared. There are no placeholder fields pretending to be live; what you save is what goes out, edited as needed before sending.

Faster answers without losing accuracy

Saved replies speed up the queue without flattening it. You pull in the right answer, adjust the specifics for that customer, and send. The customer gets a prompt, accurate reply, the agent avoids retyping, and the wording stays consistent across whoever happens to be covering accounts@ that week.

Finance and operations need to be able to answer the question, who dealt with this and when. Solves keeps a metadata-only history on every ticket: assignment changes, status and priority changes, when a public reply was sent, and when a private note was added. That is enough to reconstruct how a query was handled without ever putting the message content into the log.

Metadata, not message bodies

The distinction is deliberate. The audit history records the action and the actor, not the words. Message bodies, subjects, contact details and any sensitive figures are encrypted at rest and reached only through authorised access, while the logs that show activity carry metadata only. You get accountability and privacy at the same time, rather than trading one for the other.

Helpful at month end and beyond

When a manager asks why a refund took two days, or whether a disputed invoice was ever replied to, the ticket history answers it plainly. The same record makes handovers and cover straightforward, because the next person can see exactly where a query was left, without trawling a shared inbox or asking around.