Opening a file — the gesture nobody bills

A process serving firm never complains about intake. It is so routine that nobody sees it as work anymore. You open the request, you type, you move on. You have to look at it closely to see what it really weighs. This article describes a use case.

What intake really involves

Every service request that reaches a process serving firm is typed in by hand before anyone goes out: the case, the court, the person to serve, the addresses, the deadline. Nobody bills for it. Data entry automation can take over that copying, as long as a person still makes every call that matters and signs every affidavit.

In practice, a law firm sends the papers, most often by email. Someone reads the case caption and finds the person to serve. They check that this person is not already in the system under another spelling. They copy the addresses, the court, the case number and the deadline. Then come the notes: a gate code, work hours, a photo. Then the next request.

This happens across a whole profession. The National Association of Professional Process Servers says it has well over 2,000 members representing all 50 states. Every job those servers take starts from a request that someone read and typed in.

Each part of process server intake is simple. None of it is hard. It is just constant, and it lands on the same few people every day.

Three costs, only one of which is measured

Time is the cost you can see. It is not the biggest one.

The second cost is the duplicate. The same person entered twice, under two spellings, causes no trouble on the day it is typed. It causes trouble the day two people each work on their own version.

The third cost is the heaviest and the rarest: an error carried from the request into the proof of service. The rules are plain about where that proof ends up. Rule 4 of the Federal Rules of Civil Procedure says it outright:

“Unless service is waived, proof of service must be made to the court. Except for service by a United States marshal or deputy marshal, proof must be by the server's affidavit.” — Federal Rules of Civil Procedure, Rule 4, Legal Information Institute

In plain words, a sworn statement goes to the court. A typo there is no longer a typo. It can mean a service that gets challenged, and a job that has to be done again.

What changes when an agent holds the intake

An agent built for the firm replaces neither the software nor the person. It takes the part that is pure copying: reading what came in, preparing the job, and flagging anything unclear.

That last part is the one that counts. An address that looks wrong, a name spelled two ways, a deadline that does not match the papers: the agent stops and says so. It does not guess.

The rule is simple. Anything that is a decision goes up. Anything that is copying stays down.

Service itself is never in play. Serving papers, signing the affidavit and swearing to it stay with your servers and your staff, under the rules of each state you work in. No agent goes near them.

Why this is not a software problem

People often ask if their software will one day do this on its own. Some tools can import a file. But requests come from many law firms, each with its own format, and someone still has to read them. That reading is the work.

So the fix is not a new setting. It is an agent that works the way the person works, in the tools you already use. We build it to measure, for one firm, and install it at the firm’s office. The files stay on the firm’s own machines. Only the text a task needs is sent to the AI model.

---

You can read what an agent does for a process serving firm and check what a custom agent costs. Other use cases, industry by industry are gathered on a separate page. The day-to-day detail is best covered in a conversation.