Use case · Customer support

Support agents that remember the last time

A senior rep carries three years of an account in their head. An agent fleet starts every conversation at zero, unless what happened last time was written somewhere it can read.

The mixture

01 · Persistent memory
Uses
02 · Current context
Uses
03 · Traceable decisions
Leads
04 · Shared context
Uses
05 · Scoped retrieval
Light
01 · What breaks

Every ticket is the first ticket

Current support systems struggle with coordination, prioritization and context retention. Six specific failure modes, each of which leaves a trace in your own helpdesk.

  1. 01

    Escalation ping-pong

    Issues bounce between departments without anyone owning the resolution. Each team sees its own slice of the case, never the whole of it.

  2. 02

    Priority paralysis

    Critical issues sit buried in the queue, because nothing detects urgency from what the customer has already been through.

  3. 03

    Case history blackouts

    Previous interactions are invisible to the next agent, so customers are forced to restart their explanation every time.

  4. 04

    The fix is in the transcript, not in context

    The same customer hit this six weeks ago and it was solved. The thread can be searched, but the resolution was never stored as something an agent can retrieve. Diagnosis starts again from the top.

  5. 05

    Two agents, two truths

    The customer tells the chat agent they moved to the legacy plan. An hour later the email agent answers from a billing record that has not synced. Nothing holds the reconciliation, so the contradiction reaches the customer.

  6. 06

    Nobody can say why it answered that

    A customer escalates a wrong refund answer. The logs show the prompt and the reply, but not which article, ticket or policy the agent was reading when it decided.

02 · What it does

Smart support features

Enhance customer experience with AI agents that remember context, learn from interactions and deliver personalized support at scale.

01

Retain customer history

Agents remember past conversations and customer context, without having to ask for it again.

02

Tailored solutions

Every reply feels personalized to the customer it is written for.

03

Pattern recognition

Agents detect patterns across customer interactions, so they are prepared for the unexpected.

04

Feels human

Past context lets agents remember things about the customer, so the customer feels connected to the agent.

03 · What it's made of

Mostly traceable decisions. Then three others.

Every application on Alchemyst is a different mixture of the same five jobs. That mixture is what makes this a different piece of software from the one next to it, even though the API underneath is identical.

Leads · Traceable decisions

Every answer keeps its receipts

Every search an agent runs is recorded as a Context Trace: the sources it was served, their scores and the rules applied. When an answer is wrong, you open the trace, see exactly which document caused it, and fix that document once.

  • Wrong answers trace back to one source.
  • Fixes land in the context, not the prompt.
  • Escalations arrive with evidence attached.

Uses · Persistent memory

The last time, remembered

Resolutions are written back against the customer, so the next ticket starts from what worked.

Uses · Shared context

Chat and email agree

Every channel reads the same customer context, scoped to the same account.

Uses · Current context

The refund policy in force

Superseded macros and old policies are subtracted before the agent answers.

That is four of the five. The fifth, scoped retrieval (intersection, subtraction and ranking decide what enters the window, not similarity alone), is what leads in Research agents, Coding agents and Voice AI instead. Same API, different mixture.

04 · What feeds it

The sources you already have

Bring sources in through the data-source integrations (PostgreSQL, MongoDB, Google Docs, Google Sheets, Amazon S3), an n8n workflow, or a direct context.add call. Each one lands scoped, so retrieval can intersect it with everything else.

ZendeskIntercomHelp center articlesSlackJiraBilling (PostgreSQL)
  1. 01 · Ingest

    Scope what you ingest

    Every document lands with a groupName: the sets it belongs to. Those sets are what retrieval intersects later, so the structure you choose here is the precision you get there.

    context.add
    import AlchemystAI from "@alchemystai/sdk";const client = new AlchemystAI(); // reads ALCHEMYST_AI_API_KEYawait client.v1.context.add({  context_type: "resource",  scope: "internal",  source: "help-center",  documents: [{    content: "Annual plans are refundable pro rata within 30 days of renewal. After 30 days, credit is issued instead.",  }],  metadata: {    fileName: "refunds-annual-plans.md",    groupName: ["support", "billing", "refunds"],   // the sets this belongs to  },});
  2. 02 · Write

    Write the resolution, not the transcript

    The transcript is already in the helpdesk. What is missing is the outcome, stored against the customer so the next agent retrieves it as experience.

    context.memory.add
    await client.v1.context.memory.add({  sessionId: "acme:ticket-44812",  contents: [    { role: "user", content: "Renewal card keeps getting declined." },    {      role: "assistant",      content: "Resolved: 3DS step timing out on their gateway. Retry window raised to 40s.",    },  ],  metadata: { groupName: ["support", "acme", "resolved"] },});
  3. 03 · Search

    Search before replying

    Search intersects the scopes, subtracts superseded and duplicate content, and ranks what survives. Only that reaches the model, and the whole decision is recorded as a Context Trace.

    context.search
    const { contexts } = await client.v1.context.search({  query: "Customer says their renewal payment failed again",  scope: "internal",  similarity_threshold: 0.8,  minimum_similarity_threshold: 0.5,  metadata: { groupName: ["support", "acme"] },   // ∩ narrow scope});// − superseded, deduplicated → ranked → into the window// Every search is recorded as a Context Trace.const reply = await llm.respond(message, { context: contexts });

npm install @alchemystai/sdk or pip install alchemystai, both ship the same client. Full reference in the docs.

05 · What it costs

Efficient support at scale

Handle more support tickets with fewer resources, while maintaining quality.

  • Automated context management reduces agent cognitive load.
  • Smart token usage cuts operational costs by up to 40%.
  • Handles complex, multi-turn conversations effortlessly.
Tokens used, average per taskMemory connected

Standard agent

3M tokens

High token usage, short context window

Alchemyst-enhanced agent

1.8M tokens

Shorter prompt optimized with Alchemyst

06 · Where it runs

Support transcripts are the customer's data

A support history is often the highest-PII corpus a company owns: names, orders, card failures and whatever the customer typed in frustration at 2am. Scope it per account, encrypt it, and keep it deletable on request.

Security & compliance
Deployment
  • Managed cloud

    Encrypted in transit and at rest, isolated per organization, and scoped at write time.

  • Dedicated infrastructure

    Enterprise

    Single-tenant, with VPC peering when your data cannot share a network boundary.

  • Self-hosted

    On-premise

    Run the context layer on your own infrastructure, with OpenTelemetry for observability.

Talk to us

Bring the ticket it gets wrong.

Not the demo. The one where it asked a question the customer had already answered.