Skip to main content

Giving Dex context

Dex works better the more it knows about your organization and about you. There is no onboarding questionnaire to complete first: Dex answers cloud questions from day one, and learns your context from the conversations you have with it.

Organization context​

Shared context applies across every user in your organization. It is worth telling Dex:

  • How your company describes teams, business units, environments, and workloads.
  • Which cloud accounts, projects, or subscriptions matter most.
  • How ownership is usually determined.
  • Which communication and ticketing tools should be used for follow-up.
  • How your organization prefers to describe cost optimization work.

This gives Dex the common language your team already uses. For example, if your company calls a workload by an internal product name, Dex can use that language when explaining related assets or opportunities.

Ask Dex "what do you know about us?" at any time to see what it has on file, and correct it in conversation.

Personal context​

Dex also remembers what is specific to you:

  • Your name or preferred short name.
  • Your role, team, and areas of responsibility.
  • Which systems, services, or cost centers you care about.
  • How you prefer to receive summaries and follow-ups.
  • Whether you usually own decisions, review recommendations, or route work to someone else.

This lets Dex tailor responses. A FinOps lead may want portfolio-level savings and prioritization. An engineering manager may want owner-ready summaries and risk context. An individual engineer may want the specific resource, expected impact, and implementation notes.

Keeping it current​

Your organization changes: teams move, ownership shifts, services get renamed, and priorities change. Correct Dex in conversation.

Examples:

  • "That service is now owned by the platform team."
  • "Call this group Core Infrastructure going forward."
  • "For commitment recommendations, route the first review to FinOps."
  • "Use my short name in summaries."

When information is important for future work, make the correction explicit. Dex can then use that updated context in later conversations.

Being specific pays off​

Concrete answers beat general ones. "The payments team owns the checkout and billing accounts" is more useful than "engineering owns it." Specific ownership, names, and follow-up preferences help Dex route opportunities and summarize work more accurately.