[ Agent manifesto ]

We believe support should not slow down teams building product

Modern support should combine AI, account context, documentation, and human judgment to resolve repetitive tickets without adding operational noise.

We created the agent because support inside many SaaS companies was becoming a difficult mix of repeated conversations, scattered documentation, and context lost between tools.

Teams do not fail because they do not want to help. They fail because each question arrives without enough context, each answer depends too much on someone’s memory, and each customer blocker takes too long to become product learning.

We believe modern support has to work differently. AI should answer when real knowledge exists. Documentation should be connected to daily work. Customer context should be present before the first reply is written. And a person should step in when their judgment truly improves the experience.

The agent exists to bring those pieces into a clearer system: inbox, knowledge, AI, human handoff, and product insights working together.

We do not want to hide the team behind automation. We want to give them time back for the conversations where a person truly matters.

Adrià CastanyFounder of Intake

The team

We build the agent from Barcelona, close to SaaS teams that want to answer better without turning support into a heavy layer of process.

What we stand for

  • Less noise, more answers

    Fewer inboxes, fewer tool jumps, and fewer repeated answers by default.

  • AI should work with real knowledge

    An agent that improvises is not support. AI should use documentation, history, and clear rules.

  • Context is part of the answer

    A good answer depends on who is asking, what happened before, and what they need now.

  • Support should also improve product

    Every repeated question is a signal to improve onboarding, documentation, or product.

  • People when it matters

    Automation should create time for the cases where a person adds judgment.

We are at the beginning. But the direction is clear: less noise, better answers, and more context for teams building product.