Back To Core Concepts

How Cartos Operates: What to Expect as a Team

Cartos is your analytics follow-up agent inside Anamap. It helps keep analysis moving by asking for missing context, tracking responses, and escalating when needed.

This guide focuses on what users should expect and what to configure for a smooth experience.

What Cartos does for users

Cartos helps your team by:

  • Identifying questions that block analysis
  • Asking the right person for missing context
  • Following up if there is no response
  • Recording context so future runs are more informed
  • Prioritizing release-impact follow-ups when release signals are received

What your team needs to set up

To get reliable behavior, configure these three things:

  1. Connected analytics sources
  • Connect GA4 and/or Amplitude so Cartos can validate and prioritize findings.
  1. Recipient configuration
    • Add recipients for outreach (Slack and/or email), with priorities and topic owners.
    • Keep recipient records current when ownership changes.
  2. Schedule + outreach settings
    • Turn on Fulltime Agent mode and set cadence/timezone.
    • Confirm outreach policy (timeouts/retries) matches your operating rhythm.

Channel behavior (Slack and Email)

Cartos can deliver outreach through Slack or email depending on your configured recipients.

  • If a recipient is configured as slack, Cartos sends in Slack.
  • If a recipient is configured as email, Cartos sends via email proxy.
  • If one path is unavailable for a given recipient, Cartos records the failure and continues queue handling.

How Cartos knows Slack is enabled

Slack outreach is considered available only when:

  • Your company has a configured Slack installation, and
  • A valid Slack bot token exists for that installation.

If those are missing, Slack delivery is marked unavailable and Cartos uses the configured queue/fallback flow.

Response and follow-up behavior

After outreach, Cartos:

  • Marks questions as awaiting response
  • Tracks timeout windows and retry limits
  • Schedules retries or escalates to alternate contacts when needed
  • Learns from response channels and recipient patterns over time

Release-trigger behavior

If your CI/CD sends a release signal to Cartos:

  • Cartos creates a high-priority ownership/impact follow-up
  • Cartos sets urgency windows based on connected source availability
  • Cartos starts follow-up workflows so teams can validate impact quickly

For implementation details and payload/auth examples, see:

  • Cartos Release Trigger: Setup & Requirements

Best practices for teams

  • Keep at least one active owner/admin recipient configured.
  • Define topic experts for major domains (checkout, acquisition, activation, retention).
  • Use clear role tags and priorities to reduce routing delays.
  • Review unresolved questions regularly and close stale threads.
  • Revisit cadence settings quarterly as team processes evolve.

What Cartos does not replace

Cartos accelerates coordination and analytics follow-through; it does not replace product judgment or owner accountability. The best results come from clear ownership and fast responses from your team.