Arie (arie) wrote in xxcustomization,
Arie
arie
xxcustomization

A quick note on not logged in requests in Customization.

If a user isn't logged in when they are making a request in customization, they need to be told to log in before we can answer their request. Please review the Policy & Procedures post for Supporthelp Privs, Sections I & II for more information on this.

Basically, if a user isn't logged in, or is request help for a friend, the best way we can help them is if they are logged in or if their friend opens their own request. Not just because we need to see their journal ourselves, or speaking with the person directly causes less confusion, but because it will eliminate requests that are really for UJ or DJ. We don't do Customization support for UJ or DJ; they have their own Customization support.

Customization isn't like g/unk where a user might have a legitimate reason not to be logged in. In customization they are requesting help with customizing their LiveJournal. Non-users don't make requests for how to add a custom scrollbar or background, they don't have a journal to customize, after all. ;)

Most of the time the user probably forgot they weren't logged in. That's fine, a polite comment to please resubmit while logged in --along with a brief explanation of why we can best help them that way-- will be great. This way we can actually check back to see if they've applied the override or had trouble, and we can offer them specific advise, while still eliminating requests from users of other services. If someone has both an LJ and a UJ or DJ, that's fine, but its not our responsibility to offer support for 350,000+ other users when we have 720,000+ of our own to worry about. ;) Having the user logged in helps us help them. A good thing all around.

Thanks so much guys, you're the best!
Subscribe
  • Post a new comment

    Error

    default userpic

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 8 comments