gethuman standard v1.0
The gethuman standards have been designed with simplicity and directness as to eliminate ambiguity and enable testing and certification. There may be more than one way to accomplish each, but the result must be as follows:
- The caller must always be able to dial 0 or to say "operator" to queue for a human.
- An accurate estimated wait-time, based on call traffic statistics at the time of the call, should always be given when the caller arrives in the queue. A revised update should be provided periodically during hold time.
- Callers should never be asked to repeat any information (name, full account number, description of issue, etc.) provided to a human or an automated system during a call.
- When a human is not available, callers should be offered the option to be called back. If 24 hour service is not available, the caller should be able to leave a message, including a request for a call back the following business day. Gold Standard: Call back the caller at a time that they have specified.
- Speech applications should provide touch-tone (DTMF) fall-back.
- Callers should not be forced to listen to long/verbose prompts.
- Callers should be able to interrupt prompts (via dial-through for DTMF applications and/or via barge-in for speech applications) whenever doing so will enable the user to complete his task more efficiently.
- Do not disconnect for user errors, including when there are no perceived key presses (as the caller might be on a rotary phone); instead queue for a human operator and/or offer the choice for call-back.
- Default language should be based on consumer demographics for each organization. Primary language should be assumed with the option for the caller to change language. (i.e. English should generally be assumed for the US, with a specified key for Spanish.) Gold Standard: Remember the caller's language preference for future calls. Gold Standard: Organizations should ideally support separate toll-free numbers for each individual language.
- All operators/representatives of the organization should be able to communicate clearly with the caller (i.e. accents should not hinder communication; representatives should have excellent diction and enunciation.)
gethuman standards testing for gethuman 500
The gethuman 500 will be tested for compliance with the gethuman standard regularly, and results will be published on gethuman.com. For each standard, organizations will receive a 0 (not compliant) or a 1 (compliant). Overall ratings will reflect an average of standard scores.
certification process
In order to be certified as gethuman-compliant, organizations must adhere to the gethuman standard. The gold-level standard items are also recommended, but are optional. Eventually, these gold-level items may be incorporated into a future version of the gethuman standard. The gethuman team will consider requests for exceptions when the organization feels a standard is not appropriate. This will be done on a case by case basis and is at the sole discretion of the gethuman team. Testing will be conducted to verify compliance, with periodic retesting to confirm continued compliance. For additional information please contact us.
gold standards
- While holding, allow callers to disable hold music; remember their selection for future calls.
- If ads or promotions are played, allow users to disable them.
- Allow callers, where appropriate, to identify themselves via caller ID and a securely defined PIN, instead of being required to enter long account numbers each call.
- Default to preferred language based on caller ID.
- Support and publicize individual toll-free numbers for individual languages.
- Allow callers to access audio transcriptions of their calls via the organization's website.
- Call back the caller at the time that he/she specified.
contact us
If you have questions regarding gethuman.com or the gethuman standard, please contact us.
The gethuman™ website is Copyright 2005-2008 by Paul M. English; Updated Tue 21-Nov-2006 8:22 PM