The report is finished. Now get it to them.
Automation projects are scoped as if delivery were the easy part. It is routinely the part that kills them. You have the numbers, the summary, the schedule — and twenty counterparties who all read one messenger, on their phones, in a market where that messenger is the business. Everything upstream is engineering. The last mile is somebody else's product decision. State what you cannot give up, and watch the options rule themselves out.
Honest-AI note. No model, and deliberately no vendor names — products change, and the point is the shape of the constraint, which doesn't. Each channel below is a real attempt with a real outcome: one abandoned after a deterministic crash behind a closed layer, one built and verified and then parked for a reason no code fixes, one shipping in production, one priced and declined, one that always works and nobody reads. The verdict strip is solved live from the matrix at the bottom, so the page cannot claim a trade-off the table doesn't support.
What you cannot give up
Plain-language key (last mile, unattended, robot endpoint, verification, protocol bridge)
- Last mile
- The step between "the output exists" and "the person read it". Usually assumed, rarely scoped.
- Unattended
- A scheduled job sends with nobody present. The difference between unattended and one-tap-per-message is the difference between a system and a chore.
- Robot endpoint
- An official address a platform gives you to post into a group you control. Sanctioned, reliable, and limited to people who have joined that group.
- Verification
- Paying a platform to confirm your organisation is real. It buys reach and trust — not necessarily the right to send automatically.
- Protocol bridge
- Software that re-implements a messenger's own protocol so a server can act as a client. Powerful, unsanctioned, and opaque exactly where you need to debug it.