Safe sender requests, handled from the ticket.
Neo finds the client's Proofpoint Essentials organization, adds the sender to the right safe list, and manages users and domains. It cannot release an email that is already in quarantine.
What Neo does with Proofpoint Essentials.
Safe and block lists
Adds a sender, domain or IP address to a safe or block list for a whole organization, one user or one group. Neo picks the narrowest entry that meets the request.
Starters, aliases and leavers
Looks up a user's filtering account, adds a new starter or an alias, and deactivates a leaver.
Domain health and DKIM
Checks a domain's mail routing health, verifies a new domain, and adds DKIM signing.
Concrete work Neo handles in Proofpoint Essentials.
Let this sender through
Neo adds the exact sender address to the user's safe list, so the next email is not held, and tells the user how to release the current one from their quarantine digest.
Block an unwanted sender
Adds the sender or domain to the organization's or the user's block list. Neo reads the list before and after, and restores any entry the change removed.
New starters and leavers
Adds a new user or an alias to the client's filtering, and deactivates a leaver's account, from the onboarding or offboarding ticket.
Mail flow figures for QBRs
Reads mail flow statistics and licence counts for a client, so the numbers are ready before the review.
Live in under an hour.
Connect, configure, go. No code, no long implementation.
Connect Proofpoint Essentials
Create a dedicated admin for Neo, then save its username, password and your stack in Neo. A Channel Partner Admin reaches every client organization. Neo checks the login before it saves.
Set access per agent
Pick Read Only, Helpdesk, IT Admin or Full Automation for each agent, or set each area by hand. Helpdesk fits safe sender tickets, and every sender list change waits on a technician.
Go live
Check the Organization Mapping tab and confirm any suggested matches. Your agents then work held email tickets from the PSA.
Questions about the Proofpoint Essentials integration.
Can Neo release a quarantined email?+
No. Proofpoint's published Essentials API has no quarantine endpoint. Neo can stop the sender's next email from being held. The agent tells the user to release the current one from their quarantine digest, or a technician to release it in the Proofpoint console.
Does Neo need approval to make changes?+
You decide per area. Helpdesk and IT Admin ask a technician before any sender list change. Deleting a client organization or a domain, granting impersonation rights, and creating a console login token as another user always ask a technician.
What credentials does Neo need?+
An admin username and password, plus your stack (for example us2). The Essentials API has no API key. Use a dedicated admin, which you can mark as the non-billable service account. If SSO or MFA blocks Neo's sign-in, use a local admin account. Neo stores the login in Azure Key Vault.
How are Proofpoint organizations matched to PSA companies?+
Neo matches by name first, then by the organization's mail domains against the website on each PSA company, then with AI. Name matches go straight to your agents. Domain and AI matches wait on the Organization Mapping tab for you to confirm, and you can set any mapping by hand.
Ready to wire up Proofpoint Essentials?
14-day free trial. No credit card. Live in under an hour, right inside your stack.