Referrals, invoices, payer correspondence. Reception, the biller and the practice manager all open mail from strangers as part of the job. Screening operates within the mailbox, not ahead of it, and adds short drills for the people doing the opening. Ironscales works at mailbox level over an API, and is not a gateway.
Anything positioned ahead of your mail reads each message once, in passing, and its work is then done. Whatever passed at that instant passes forever, the message whose linked page was innocent on delivery and hostile by lunchtime included. Ironscales runs off a connection into Microsoft 365 or Google Workspace, which means it reads mail that already landed and stays free to change its mind afterwards.
In practice that means a message judged hostile is withdrawn from all of the inboxes it reached, not merely the one that raised a hand. Nothing is rerouted, no MX record changes, and no window opens in which mail piles up somewhere while an engineer works out what broke.
Simulation and short lessons sit on their own line, partly because a practice sometimes wants them without the mailbox layer, and partly because what they produce is worth having on its own. Campaigns get paced to teach. A lesson goes to the person who clicked rather than to everybody at once, which is the difference between training and a staff meeting.
Afterwards you hold a dated record, name by name, of what was sent and what was completed. That is the document somebody eventually asks for when the question becomes how the workforce was prepared, and it cannot be assembled from memory the week it is wanted.
Rates come live from billing. Anything tagged waits on the chart while you carry on reading.
Cover operating within the mailbox rather than ahead of it, on the Microsoft side or the Google one, with brief drills for whoever opens referrals and invoices all day. An API connection is what lets it act on something delivered an hour ago.
| Fitted to | Microsoft 365 or Google Workspace mailboxes, joined by API |
|---|---|
| Watches | Mail once it has landed, and how people answer a rehearsed attempt |
| Kept for | A reporting history your workforce training file can quote |
| Escalates to | Withdrawal from the mailboxes first, then our desk |
| Reviewed by | An engineer, wherever the software is undecided |
Rehearsed attempts sent across the workforce, with a short lesson reaching whoever needs one. Priced by the person, so a clinic can run it without buying mailbox cover first. What comes out is the dated name-by-name record somebody eventually asks for.
| Fitted to | Named users in a Microsoft 365 or Google Workspace tenant |
|---|---|
| Watches | Opens, clicks, reports, and who got to the end of the lesson |
| Kept for | A dated record, name by name, for your training file |
| Escalates to | Your practice, as a summary fit to put before a committee |
| Reviewed by | Your privacy officer, with our engineers on the numbers |
Each station has an edge to it, and clinics get caught out by suppliers who pretend otherwise. Below is where this one stops, set down so a practice can work out what else it needs and who else has to supply it.
Heads up: card statements show FORTIFY 24X7 - MediDefense IT is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.