You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

System administration best practices for large, complex customers

edited Mar 19, 2013 2:22PM in Taleo Enterprise

Content

New Taleo client moving from multiple, legacy solutions and support teams to centralized Taleo platform is interested in speaking with large (25k+ employee - can veer lower if complex), multi-divisional companies who are live with multiple Taleo modules, preferably Recruiting, Onboarding, and Learn.

  1. How did you design your support model across the organization?
  2. How do you split support roles/responsibilities between corporate and divsions?
  3. How do you split support roles/responsibilities between HRIS and IT?
  4. Have you implemented SLAs with your divisions?  What's working / needs improvement with SLAs?
  5. Other lessons learned along the way?

Feel free to reach out directly if you'd prefer not post to the forum.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!