Community Ideas

1 Votes
Votes

(Voting Open) Email or cc

Return to previous page

You have votes remaining
  • 7/20/2016
  • 108 Views
  • Comment
  • Last Activity: 1 month ago

Company Response

Dave Kornegay
Dave Kornegay 2 months ago

Thank you, Monica.

To be sure this is not an existing request, and to clarify the scenario, is this a case in which you wish for other requesters to know that an issue has been already submitted to prevent duplicate submissions for the same issue?

Here are a couple of items to consider in the meantime if I am interpreting your idea correctly:

MY REQUESTS tab: this tab shows a Requester's previous requests. If they are allowed to see the "Assigned To" column with the person's name currently assigned to the work order or incident, that can send an email to someone and track it in the history of the request. The form is defaulted to email the Assigned To person, but that can be overwritten (so can the body of the email).

"Super Requesters": I made up this name, but you can allow a specific Requester the ability to see all work at a Location in their My Requests tab vs. just their specific individual requests. It's for those organizations that want expanded visibility for a Requester to see what is happening at a Location, but not have the power of the Site Admin role.

SITE ADMIN Role: Site Administrators see what is happening in their assigned location(s). They may decide to get an email of a new request that comes in and can forward that email to personnel, or reference the WO or Incident ID that was submitted.

TWITTER: Some departments will use a Twitter feed that includes updates on issues and resolutions to cut down on emails.

Comments

Vote Locked
You have votes remaining
Votes -  Voting Open

Email or cc

Monica Hixson
Monica Hixson 2 months ago

Company Response

Dave Kornegay
Dave Kornegay 2 months ago

Thank you, Monica.

To be sure this is not an existing request, and to clarify the scenario, is this a case in which you wish for other requesters to know that an issue has been already submitted to prevent duplicate submissions for the same issue?

Here are a couple of items to consider in the meantime if I am interpreting your idea correctly:

MY REQUESTS tab: this tab shows a Requester's previous requests. If they are allowed to see the "Assigned To" column with the person's name currently assigned to the work order or incident, that can send an email to someone and track it in the history of the request. The form is defaulted to email the Assigned To person, but that can be overwritten (so can the body of the email).

"Super Requesters": I made up this name, but you can allow a specific Requester the ability to see all work at a Location in their My Requests tab vs. just their specific individual requests. It's for those organizations that want expanded visibility for a Requester to see what is happening at a Location, but not have the power of the Site Admin role.

SITE ADMIN Role: Site Administrators see what is happening in their assigned location(s). They may decide to get an email of a new request that comes in and can forward that email to personnel, or reference the WO or Incident ID that was submitted.

TWITTER: Some departments will use a Twitter feed that includes updates on issues and resolutions to cut down on emails.

Comments