Primitive Computing

Here is a use case for an enrollment process:

Scenario X - Error: No Response to enrollment request

1. The customer clicks the enroll button.
2. System X sends the enrollment request to System Y, but there is no response.
3. The customer sees a message directing them to contact customer service.

Is this still acceptable in today's robust programming world? How much value is this system adding? From a user's perspective I get real upset when I see "Please contact customer service". The entire point of me taking my time to complete this automated transaction is so I do not have to speak to a service rep. I can understand bailing on the transaction if this is a complicated matter that requires human intervention. If so, please provide the user with detailed information explaining the situation.

Here is how I would implement this system. Who needs System Y when I can just have System X do this up front.
Bedrock Systems, Inc enrollment app.

Published 26-06-2006 09:39 by gmckinley

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

Jack said:: Hopefully, it is a rare case where the other system fails to respond. If there were a "backup" system, such as an email with Tx details is sent instead in the background, then the transaction can complete - and the user would never know there was a problem. Of course, this is an issue if you require real-time feedback.
September 5, 2006 6:10 AM