One inbox, not five
Customer and vendor mail tied to the record it belongs to, not to whoever’s mailbox it landed in.
Flowwiz / Finance InboxEvery reply.
[Email to action]
Every reply.
On the right record.
Customer and vendor email classified, tied to the invoice or bill it belongs to, and turned into the next step.
Both sides classified
Customer mail carries disputes, promises, and queries. Vendor mail carries invoices, confirmations, and remittances.
Forwards still work
Customers keep emailing the person they know. A forwarded thread is classified and logged exactly the same way.
Email to action
From a reply to the right next step.
Reading the message is the easy part. The value is in what happens next, and in what deliberately does not.
- 01Capture
The message arrives directly, on CC, or forwarded.
- 02Classify
Customer or vendor, then the finance intent inside it.
- 03Attach
The message is tied to the customer, vendor, invoice, or bill it concerns.
- 04Log
It lands on one timeline per customer and per vendor, not per mailbox.
- 05Act or route
Update the timeline, create a task, pause the reminder, or send an exception to an owner.
Timeline · Northstar Studio
- Finance Inbox
Reply received from billing@northstar.co
“We can pay $4,800 by Thursday.”
- Promise To Pay Agent
Promise-to-pay captured against INV-1048
- Promise To Pay Agent
Reminder sequence paused
- Account owner
Notified to review the commitment
Classification
What the inbox separates.
A reminder sequence should stop when a customer has already told you why they cannot pay yet. That only works if the reply was understood.
Customer email
- Dispute raised
- Promise to pay
- Billing question
- Query resolved
- Supporting documents requested
- Bounce notification
Vendor email
- Invoice or bill received
- Payment confirmation
- Remittance advice
- Statement or dunning notice
- Rate or term query
FAQ
Before you go further.
What happens to a dispute?
The workflow assembles the context (invoice, prior replies, open items) and routes it for review instead of continuing routine reminders.
What does the owner receive?
The message and the relevant invoice context, so the reason for the routing is visible before they open anything else.
Do we have to change our email addresses?
No. Direct mail, CC, and forwarded threads are all classified and logged the same way.
Does it replace our shared mailbox?
It works alongside it. The difference is that the thread is attached to the customer or vendor record rather than to a mailbox.
Can we see who replied to a vendor?
Yes. The timeline records the participant and the action, so the thread is not owned by one person’s inbox.
Start
See it with your team’s context.
Bring your workflow, your systems, and who approves what.