Search
Topics
  Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
Modules
· Home
· Content
· FAQ
· Feedback
· Forums
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account

Current Membership

Latest: ZCardillo
New Today: 14
New Yesterday: 67
Overall: 148315

People Online:
Visitors: 64
Members: 1
Total: 65 .

Languages
Select Interface Language:


Major ITIL Portals
For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone

Related Resources
Service related resources
Service Level Agreement
Outsourcing

Note: ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.


The Itil Community Forum: Forums

ITIL :: View topic - Keeping users informed of during major incidents
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Keeping users informed of during major incidents

 
Post new topic   Reply to topic    ITIL Forum Index -> The ITIL Service Desk
View previous topic :: View next topic  
Author Message
Redrocker
Newbie
Newbie


Joined: Apr 16, 2012
Posts: 2
Location: Leyland, England

PostPosted: Thu Apr 19, 2012 1:01 am    Post subject: Keeping users informed of during major incidents Reply with quote

Hi all, just found this forum, so this is my first post. I work in Incident managment and we are looking for new ways to keep our users updated on the progress of major incidents.

We currently text to stake holders at the start and end of an incident, have messages we can put on the service desk number, email and have recently started messaging through citrix to users.

Does anyone have any other suggestions we could incorporate to reach a wider audience? We are a central service desk that supports a wide number of small remote sites.

cheers

Rob
Back to top
View user's profile
UKVIKING
Senior Itiler


Joined: Sep 16, 2006
Posts: 3318
Location: London, UK

PostPosted: Thu Apr 19, 2012 4:00 am    Post subject: Reply with quote

Rob,

The issue is TLI or TMI to the users
If you tell them about every outage - even out of hours that happen as a matter of course,.... will they think the service is unreliable

If you have the ability to post to a website / social web... but then.. what if that service is the one that is down

There is no easy answer

Ask the stakeholders is my next suggestion
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
Redrocker
Newbie
Newbie


Joined: Apr 16, 2012
Posts: 2
Location: Leyland, England

PostPosted: Thu Apr 19, 2012 9:50 pm    Post subject: Reply with quote

Thanks John.

I think it is a matter of striking the balance between keeping the users informed and information overload to the point they think as you say the service is unreliable.
Back to top
View user's profile
Nuno
Newbie
Newbie


Joined: Jan 09, 2008
Posts: 6
Location: Lisbon

PostPosted: Thu Apr 19, 2012 11:08 pm    Post subject: Reply with quote

Hi,

I agreed with John:
"Ask the stakeholders is my next suggestion"

In our case we use Remedy workflow to notify the users when there is incident status changes.

Regards
Back to top
View user's profile Send e-mail MSN Messenger
Hensome
Newbie
Newbie


Joined: May 31, 2012
Posts: 1

PostPosted: Thu May 31, 2012 8:15 pm    Post subject: Reply with quote

Hi Rob,

Just want to share with you the practices which we are running for major incident management.

1. Service Desk sends out the email notification to all the affected parties upon the detection of major incident.
2. The major incident manager sends out another email notification/update with more details (e.g. potential cause, which party is working on the issue, the resolution progress, any workaround identified, potential emergency change, etc.) to the stakeholders.
3. The other support team (e.g. application team, infrastructure team) who owns the incident ticket keeps updating the stakeholders by replying incident manager's email.
4. Upon resolution, the supporting team notifies the stakeholders with the actions taken to resolve the issue, workarounds applied, potential root cause, any improvement plan if applicable.
5. The incident ticket is resolved and Service Desk sends notification to all the affected parties.

Hope this helps. And please feel free to comment.

Cheers,
Henry Chang
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> The ITIL Service Desk All times are GMT + 10 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003 http://www.nukecops.com

Forums ©

 

Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.