1

I'm designing an application to handle requests from users. Requests will be assigned to all kinds of people. For instance, a "Request for vacations" would be handled by someone in HR. But a request to repair a door lock would be handled by someone in facilities management. In some complex cases, multiple people could work on a single request.

I'm looking for a noun to describe someone who works on requests.

A general term that means "someone who does something in a process" would be fine too.

Sly
  • 273
  • This is related to my other question: http://english.stackexchange.com/questions/35596/what-do-you-call-someone-who-makes-a-request – Sly Aug 01 '11 at 13:33
  • Also, processor. – Mitch Aug 01 '11 at 13:57
  • @Mitch: I thought about processor too, but 1. it's been canibalized by its meaning of CPU; 2. dictionaries seem to say it applies to machines exclusively. – F'x Aug 01 '11 at 14:53
  • Expeditor, maybe. – mkennedy Aug 01 '11 at 15:28
  • I need a word that is user friendly and that I can use in email messages sent to the requesters. For instance: "Dear Jenny, Your request number is 1788726. The <> assigned to your request is Mike Brown." – Sly Aug 01 '11 at 15:34
  • Oh...then the most natural thing is to say person. – Mitch Aug 01 '11 at 15:48
  • I need something more specific that I can use everywhere in the application. For instance, you can open the list of all operators to see their workload. Or you can print a report of requests per operator. Or you can display a list of open request and see the operator column. – Sly Aug 01 '11 at 16:11

3 Answers3

4

In the abstract, I would go with operator. If you wish to put this together with the type of requests that the person has to answer to, you could probably say handler.

F'x
  • 38,736
  • +1 for "handler", which is often used in a programming context to identify "service routines" that [asynchronously?] deal with specific events/requests arising elsewhere within a system. – FumbleFingers Aug 01 '11 at 14:24
  • I would say handler, too, though I'm not a native speaker. – kovalad Aug 01 '11 at 20:34
2

We had a similar situation in an IT department where I once worked. Requests for help would be placed in a queue, and any of several people with various job descriptions might handle a specific request. The person who actually did handle a given request was the responder (similar to handler, as proposed by F'x).

In some cases, multiple responders were needed, or the first responder might clarify the problem and then pass it on to a second responder, possibly a specialist (who only worked on a certain type of problem) or a domain expert (who might handle several types of problem but had special expertise in a certain subject).

Nicholas
  • 5,613
  • We had people who used "Responder" as the person that the Handler talked back to, following the idea of Stimulus and Response. Then that code met someone like you who thought of it the other direction. Since then, we eschew Responder in this type of naming. – SRM Aug 26 '21 at 16:43
0

In use case analysis a general term for "someone who does something in a process" is the actor.

Unreason
  • 12,446