Skip to content
ARCHYTASAI

ENV-OPS-103 · Customer Support & Service Operations

CaseDesk. Resolve customer problems through the right actions, not just plausible answers.

B2B customer service: inquiries, subscription entitlements, billing complaints, service incidents and credits, handled in multi-turn conversations with a simulated customer.

Custom buildCustomer Support · Multi-turn Dialogue · Account Operations

Overview. What the environment trains, and the work it's built around.

Core competency

Resolve customer problems through the right actions, not just plausible answers.

  • Investigating accounts, usage and incidents before answering
  • Applying contract terms and entitlement tiers exactly
  • Issuing credits within authorization limits
  • Asking the clarifying questions a case needs
  • Escalating with complete handoffs and no unauthorized promises

Built around the work of

Customer Support Specialist · Customer Success Manager · Escalation Manager · Service Operations Analyst

Simulated systems

  • Support desk
  • CRM
  • Subscription billing
  • Product status
  • Knowledge base

Sample task

A customer says their team experienced a four-hour service outage and is demanding a full month's refund. The customer's contract specifies a limited service credit, and the customer also disputes an unrelated overage charge. Investigate both issues, clarify any missing information, apply the appropriate policy, and update the account and support records.

Specification. The environment, field by field.

spec · env/casedesk.yamlENV-OPS-103
product_type:
Executable RL training and evaluation environment
category:
Customer Support · Multi-turn Dialogue · Account Operations
commercial_model:
Environment development and validated task packages
environment_id:
ENV-OPS-103
target_roles:
Customer Support Specialist · Customer Success Manager · Escalation Manager · Service Operations Analyst
core_competencies:
  • Investigating accounts, usage and incidents before answering
  • Applying contract terms and entitlement tiers exactly
  • Issuing credits within authorization limits
  • Asking the clarifying questions a case needs
  • Escalating with complete handoffs and no unauthorized promises
simulated_systems:
Support desk · CRM · Subscription billing · Product status · Knowledge base
interfaces:
Structured support, CRM and billing tool API · Conversation channel with a simulated customer · Knowledge-base search
interaction:
Multi-turn conversation with a simulated customer whose private information state is fixed per scenario, alongside tool use on account systems.
state:
Customer accounts, subscriptions, invoices, usage, incidents, cases and credits. Each episode starts from an isolated, seeded snapshot.
disturbances:
Ambiguous requests, demands beyond contract terms, unrelated billing disputes in the same case, identity gaps and frustrated customers.
task_families:
  • TASK-OPS-103-01 · Billing dispute resolution
  • TASK-OPS-103-02 · SLA & entitlement handling
  • TASK-OPS-103-03 · Multi-turn issue resolution
  • TASK-OPS-103-04 · Escalation & customer recovery
evaluation:
Account identity, entitlement calculations, credits issued, case status and escalation, checked against seeded ground truth. Communication quality is scored separately.
reward:
State assertions on accounts, credits and cases, plus rubric-based scoring of the conversation that never replaces the transactional checks.
training_use:
RL training, held-out evaluation and SFT on reference conversations.
deployment:
Containerized, isolated execution, with a private deployment option.
licensing:
Commercial use rights. Exclusivity and ownership are agreed for each engagement.

Workflow coverage. What agents do, and what the verifier checks.

  • Workflow

    Billing disputes

    Example tasks

    Investigate a disputed charge against usage, incidents and the price plan.

    What is verified

    The adjustment equals the recomputed amount and is within the agent's authority.

  • Workflow

    SLA and entitlements

    Example tasks

    Work out what an outage entitles the customer to under its contract.

    What is verified

    The credit follows the contract's credit schedule, not the customer's demand.

  • Workflow

    Technical issue resolution

    Example tasks

    Clarify a vague report, find the cause and resolve it or route it.

    What is verified

    The right account and workspace, the right cause and a correct resolution.

  • Workflow

    Escalation

    Example tasks

    Hand an at-risk account to the account team with full context.

    What is verified

    Complete handoff, correct owner and no commitments beyond the agent's authority.

Task families. Each family has its own datasheet: prompt, verification criteria and failure modes.

Agent tools. What the agent can call.

The agent talks to a simulated customer while working through support, CRM, billing and incident tools. Credits are limited by role, and escalations go to named owners.

tools · env/casedeskJSON-schema tools
  • get_customer
  • get_subscription
  • get_service_incident
  • read_contract_terms
  • get_invoice
  • issue_credit
  • update_case
  • escalate_case

Verification methodology. Checked against state the verifier computes itself.

Customer and account identity, entitlement calculations, credits issued, case status and escalation.

The verifier checks

  1. 01Account changes were made only after the contact was verified as authorized.
  2. 02Changes were made to the right customer's account and nowhere else.
  3. 03Credits equal the amount recomputed from contract, usage and incident records.
  4. 04Every credit is within the agent's authority, or was approved.
  5. 05Case status and notes match what was actually done.
  6. 06Escalations went to the right owner with the required handoff fields.
  7. 07Replies contain no commitments outside the agent's authority and no other customer's data.

Reward

The simulated customer has a fixed private information state, so its answers stay consistent across episodes. Communication quality can be judged separately, but never replaces the transactional checks.

Scores zero on

  • Unauthorized monetary credits
  • Changes to the wrong customer's account
  • Exposing another customer's information
  • Claiming a resolution that wasn't performed

Included deliverables. What you receive, and what we agree before we build.

Delivered with the environment

  • Containerized environment with seeded accounts and customer profiles
  • Validated task instances with reference conversations
  • Verifier and conversation rubrics
  • Agent traces and failure-mode analysis across repeated runs
  • Technical datasheet and integration documentation

Agreed before development

  • Contract terms, SLA schedules and credit limits to model
  • Customer personas and how adversarial they are
  • The conversation rubric and its weight
  • Execution limits per episode
  • Acceptance criteria

Every environment is built to order. Tell us which workflow you need to train or evaluate, and where you are in the process.

Request sample tasksDiscuss custom developmentRequest technical integration detailsSee ways to buy