Automated PO Follow-Up Without Losing Buyer Control
TL;DR
PO-Relay automates the prep work in PO follow-up: reading the thread, pulling the PO context, and drafting the message. The act of sending stays with you. Read-only Gmail and ERP, drafts only, never an agent.
What automated PO follow-up means for a production buyer
On a normal week you write the same handful of follow-up emails over and over: the acknowledgment nudge, the second nudge with a little more weight, the expedite request, the partial-shipment question, the "still on track for the original date?" check. Each one needs the prior thread, the PO numbers, the dates the supplier last committed to, and what is at risk if the line slips. The writing is fast. The research is what eats the morning.
Most of what calls itself "automated PO follow-up" in the SERP is an agent: a tool that emails suppliers on a fixed cadence with a templated message. A production buyer cannot accept that risk. A misfired automated chase to the wrong supplier on the wrong day, on a thread where there is a quality hold or a commercial dispute open, costs more than it saves. The right automation is on the prep side, not the send side.
What is broken about typical "automated follow-up" today
Cadence-based agents send the wrong message at the wrong time
Automated outreach on a fixed schedule does not know that the supplier replied yesterday on a different thread, that there is a quality hold open, or that the contact is on vacation. It sends anyway, and what shows up in the supplier inbox is a robotic nudge that ignores the context. Production buyers spend the next week unwinding the relationship damage. The time saved on writing is more than spent on apologizing.
Templated chases hide what is actually at risk
Generic "checking in on PO 12345" emails carry no information. The supplier still has to look up the PO, figure out what you are asking, and decide what to escalate internally. The reply takes longer because the question was vague. A real follow-up names the line, the date the supplier last confirmed, and what is at risk if it slips. Templates without context cost both sides time.
Hand-writing every follow-up burns the buyer's morning
The other extreme, no automation at all, means rebuilding context for every chase. You scroll the thread, pull the PO, check what the supplier last said, and write the email. Five minutes per follow-up, ten follow-ups a day, an hour gone before you have moved a single line forward. Buyers reach for cadence agents because the alternative feels worse. Both ends are wrong.
How PO-Relay solves it
PO-Relay automates the prep, not the send. Email Intelligence reads every supplier reply as it lands in your Gmail and matches it back to the right PO line. When a thread should have a reply by now and does not, when a supplier confirmed a date that has now passed without a shipment notice, or when a PO has gone unacknowledged past the window your SOPs define, an open loop appears on the dashboard with the work already pulled together.
Auto Follow-Ups drafts the chase the moment the loop opens. Each draft includes the prior thread, the PO numbers and quantities pulled from the ERP, the date the supplier last committed to, and the current risk against your build schedule. First-time follow-ups read like a polite check-in. Re-follow-ups carry the right escalation language, "this is the second follow-up regarding PO 12345, originally sent on March 14," so the supplier sees the pattern without you rewriting it. The draft sits next to the loop, never in the sent folder. You open it, edit anything that needs your voice, and send from your own Gmail in your own name.
Open Loop Tracking keeps the state. Each chase lives on the board until the supplier closes it. When the reply lands, Email Intelligence matches it back, updates the line on the parts dashboard, and either closes the loop or queues the next nudge. The buyer is in the seat for every send, every time. The assistant does the watching, the matching, and the writing. You make the call.
What you get
A draft for every silent thread, with full context attached
The prior thread, the PO line, and the risk are loaded so review takes seconds.
Re-follow-ups that escalate without you rewriting them
Second and third chases carry the right urgency built in.
No emails sent on autopilot
Every message goes through your hands and out from your own Gmail.
Triggers based on real signals, not a fixed cadence
Loops open when the supplier actually owes a reply, not when a calendar timer says so.
Inbound replies matched back automatically
When the supplier responds, the right line on the dashboard updates without your help.
A boundary that protects the supplier relationship
The assistant cannot send a misfired chase, because the assistant does not send.
What PO-Relay does not do
PO-Relay is not an agent. It does not send email autonomously, does not run on a fixed cadence, and does not contact suppliers through portals, calendar invites, or any channel other than the drafts you copy into your Gmail. It does not write back to your ERP. It does not learn your tone as a personalization model; it follows the SOPs you supply.
The boundary is the entire positioning. If the assistant could send on its own, it would also be able to misfire on its own, and the relationship cost of one bad chase outweighs a year of saved time. You stay in the seat for every send.
How it fits with your existing tools
PO-Relay connects to Gmail through OAuth with read-only scope and reads your ERP read-only. Nothing in either system changes. The drafts live in the assistant, not in your inbox, until you copy them in to send. Setup runs about 5 minutes once your Gmail and ERP credentials are connected, and there is no migration, no supplier onboarding, and no IT project to schedule. Each buyer connects their own Gmail and gets their own dashboard, so a team of buyers runs as separate per-buyer instances and nothing about your inbox is shared with another buyer.