1. Search Customer Data Hub to manage connectors by object or connector type.
2. Review your ideal account structure prior to importing accounts.
3. Import data from files, or set up integrations with other data sources on a one-time or recurring schedule.

1. Use Data Modeler to define how your customer data must be represented and stored for account, user, and collection objects.
2. Data types vary for account attributes (including custom metrics, hierarchy roll-ups, and collections) and user attributes.
3. You can add new attributes from Data Modeler or during integration configuration (Customer Data Hub).
4. Use dimensions to categorize account and user attributes into logical groups.

• Manual: Set attribute on account profile, in segment, or in bulk.
• Data Integration: Update stage from another system.
• SuccessPlay: Automate updates to these stages based on criteria. Examples:
  • Onboarding = Contract Start date in the last 90 days
  • Adoption = Customer Journey stage is not Onboarding or Nurture
  • Nurture = Contract Start Date over 365 days

1. Models: Totango allows you to design health profiles using two different models (Account Health or Multidimensional Health). You can enable multiple profiles under any model, but you can only have one model activated at a time.
2. Status: Accounts in “cancelled” status do not calculate health.
3. Order of Precedence: Position the profile(s) with the most restrictive criteria first (e.g., overrides). If an account doesn't apply to the first profile's segmentation, Totango continues to move down the profile order. Accounts that don’t match to any profile will not have health.
4. History: Recalculate going forward when making changes and optionally calculate past health for accurate look-back.
5. Hierarchy: If you have parent/child accounts, optionally roll up health calculations to parent levels.

1. Account profiles: Customize an account profile to show relevant data for each account type and team. (Switch to the team that you want the settings to apply to before you begin.)
2. SuccessBLOCs: Use SuccessBLOCs to group customers and set program goals around focused activities. Add collaborators to configure BLOCs as you work, and publish to team when ready to share scorecards, reports, and segments. (You don't need to activate SuccessPlays and campaigns.)

1. Configure teams to set core scope of accounts and available SuccessBLOCs. Optionally use employee hierarchy to dynamically define account set rules. 
2. Set system roles & permissions to determine other Totango features.
3. Assign dedicated users to each account team.
4. Control attribute visibility within account and user objects.
5. Each user of Totango must have a named license assigned (Practitioner, Contributor, or Viewer). Optionally elevate any Practitioner user to “Global Admin” (access to everything).

✨Your teams can begin using Catalyst for daily use! Continue enhancing automations that help your teams more efficiently protect and grow their customer accounts.

Ensure your team understands the value of Totango. Many Totango customers formalize this process by setting up a formal training plan, including an orientation session to prepare for launch.

1. SuccessPlays can live within any SuccessBLOC, typically one that supports a specific program initiative (e.g., Expansion, Renewal, Risk, Onboarding, VOC, etc.)
2. SuccessPlays can be event-based (trigger on condition) or manually run by your team whenever they decide.
3. SuccessPlays can have one or more action that execute in the order they are added.
4. Tasks created from a SuccessPlay allow additional options that are not available for ad hoc tasks, such as mandatory/automated post task completion actions, dynamic data, and dynamic task assignment.

1. Create emails from pre-built templates and customize the design. As an admin, be sure to set global campaign settings and authenticate your domain.
2. Use NPS or CSAT attribute types in campaigns to invoke customer sentiment surveys and track responses.
3. Send campaigns from a named user or account assignment role. Target recipients from pre-built segments or custom criteria.
4. Send campaigns on a one-off or scheduled basis. Choose timing for start and end dates, and optionally implement business hours rules to ensure timely delivery.
5. Build campaign workflows based on user engagement.