Get Started with TeamDynamix

Tags tdx

OVERVIEW

The TeamDynamix (TDX) Admin team assists groups interested in establishing their services and processes in TDX. Information collected in the form will help the team understand your team's needs. Please provide as much detail as possible. The TDX Admin team will review your submitted request and may schedule a follow-up discussion and determine next steps.

You can also book time with us to discuss your use case:  TeamDynamix Usage Discussion

Considerations Before Getting Started

Team/Group Information

  1. Team/Group Name: Provide the official name of the department, office, or team.
  2. Team/Group Description: Please provide a concise overview of what the group is responsible for. This description is visible to other ticketing technicians to help them decide where to reroute a support request they receive in error or which team they can reach out to for additional help in resolving an issue.
  3. Team/Group Membership: List group member's full name, user ID (e.g., abc123), and membership (member or manager)
  4. Who is the owner of the content created in TeamDynamix? Owners are responsible for ongoing service and content ownership after go-live.

Implementation Scope

  1. Targeted Go-Live Date
  2. Team/Group Transition Scope at Go-Live: With your preferred go-live date, determine whether your Team/Group plans to transition processes to TeamDynamix all at once or begin with smaller implementations.
  3. What TeamDynamix capabilities is your Team/Group interested in?
    • Knowledge Base Management: Create and maintain articles, documentation, and resources that provide users and team members with helpful information and support self-service.
    • Services and Service Offerings: Present the services your team provides, allowing users to understand what is available and submit requests for assistance.
    • Ticketing: Track, manage, and resolve service requests, incidents, and other work submitted to your team.
    • Workflows and Automation: Automating routine tasks, notifications, approvals, and more.
    • Reporting:  Create reports and dashboards to provide insight for tickets, issues, trends, and more.
  4. How does your Team/Group currently track support issues?
  5. Identify existing content that should be added to TeamDynamix
  6. Are there any constraints or important dates we should consider?