n-ndMail Files Your Email Into NetDocuments. We Connect What Happens After.
ndMail is NetDocuments' own add-in for filing email: it saves a message straight from Outlook into the right client and matter workspace, tagged with the same metadata as any other document in NetDocuments. We don't set up or administer ndMail. We build the automation that uses what happens after an email gets filed, triggering tasks, surfacing activity, and connecting it to the systems ndMail itself doesn't talk to.
What ndMail actually does
ndMail sits inside Outlook and lets someone file an email, with or without attachments, into a NetDocuments workspace without downloading anything first or opening a separate browser tab. The email picks up matter and client metadata the same way any other filed document does, so it's searchable alongside everything else in the workspace.
That solves the filing problem. A message that used to live only in someone's inbox now lives in the matter record where the rest of the team can actually find it.
What ndMail doesn't do once the email is filed
Filing is the end of ndMail's job, not the start of anything else. Once a message lands in a workspace, nothing tells the practice management system, the billing software, or a case manager that it happened. Someone still has to open NetDocuments to see whether a client replied or a document came back signed.
Firms that rely on filed email as a trigger, a reply means follow up, a signed attachment means bill, end up checking NetDocuments on a schedule instead of being told the moment it matters.
Where this shows up in practice
A filed email becomes a task somewhere else
A client reply landing in NetDocuments through ndMail creates a follow-up task in your practice management system automatically, instead of waiting for someone to notice it.
Filing activity visible without a NetDocuments login
Staff see that a document or email got filed, and by whom, inside the system they're already working in, so checking doesn't mean switching tabs.
What's still manual around your ndMail filing?
A reply nobody follows up on, a signed document nobody bills against: tell us what it is and we'll look at what's actually possible to automate.
Filing email with ndMail but still checking NetDocuments by hand to see what happened?
Tell us what's not connected, a reply that should trigger a task, a signed document that should trigger a bill, a report someone pulls manually once a week. We'll look at what's realistic to build on top of ndMail's filing activity. And if email filing isn't actually where the friction lives in your firm, that's fine too; the same question applies to whatever else still runs on someone remembering to check.
Let's talk