Kudzu-Ops Mailing List: Re: Process change for Lanter service issues

Re: Process change for Lanter service issues	<– Date –> <– Thread –>
From: John Burger (jburgeraserl.org)
Date: Thu, 30 Oct 2014 07:38:47 -0700 (PDT)

Emailing the “Lanter PickUp Record” to cgreen [at] lanterdeliverysystems.com & khenry [at] lanterdeliverysystems.com to Lanter is acceptable as well. My apologies for my mis-statement in the previous email.

As for when to report: Items generally should be delivered within 2-3 days. Anything that goes to five days without delivery should be reported to Lanter’s central customer service number.

Thanks.

--jeb

John Burger, Executive Director

Association of Southeastern Research Libraries

ASERL

c/o Georgia State University Library - Administration Suite LS7

100 Decatur Street SE

Atlanta, GA 30303-3202

Telephone: 404-413-2896

Follow ASERL on Facebook: http://on.fb.me/Ziuz2a

Find me on Twitter: https://twitter.com/ASERLJEB

From: Kudzu-Ops [mailto:kudzu-ops-bounces+jburger=aserl.org [at] aserl-lists.org] On Behalf Of John Burger
Sent: Thursday, October 30, 2014 10:15 AM
To: John Burger
Cc: kudzu-ops [at] aserl-lists.org
Subject: [kudzu-ops] Process change for Lanter service issues

Kudzu-Lanter Friends:

Lanter is trying to rectify its service issues, and has centralized their customer service into a single office. Starting immediately, please report all problems with missing items, lost items, damages, etc to Lanter’s centralized Customer Service Department (800-830-6126). I would appreciate receiving a quick email about your problems to me as well, for my own information purposes.

ALSO: Speed is of the essence in reporting / rectifying problems. It is much easier for Lanter to trace a package that has been missing for a few days rather than a few weeks. The “wait and see if it shows up” approach is generally not fruitful – please report items that are more than a day late to Lanter ASAP.

THIS PART HAS NOT CHANGED: Please continue to fax daily manifests to Carol Green in Atlanta (678-593-7041).

I will update our documentation to reflect this. Here’s hoping this proves to be a useful change. Thanks for your support of this program.