Telecommunications

Orders, fault tickets and billing disputes, from the first email to the closed case.

Agents take the steps between your order, ticketing, field and billing systems. A named person approves each credit and each change to a customer account. Network control stays outside every permission.

A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.

The gap between the order, the ticket and the bill

We build AI agents for telecom operations in the work between your business systems. A business order arrives by email and is typed into the order system. A fault ticket needs the service record, a field visit and a note back to the customer. A billing dispute needs the invoice, the contract and a credit that someone must approve. Each step sits in a different system, and a person carries it across.

The agent carries it. It reads the request, checks it against the account and the contract, drafts the order, the work order or the credit, and routes it. Your order desk, your dispatcher and your billing lead approve the steps that carry their names.

  • Each agent signs in as itself and reaches only the accounts in the permission for that job.
  • Content is checked before it leaves for a contractor or a partner, and the customer details you list are removed.
  • We do not connect agents to network elements or network management. See the five guarantees.
Follow one workflow

One billing dispute, four systems, one credit a person approves.

The task: settle one billing dispute from a business customer. This workflow is designed and has not run yet. To watch an approval and a refusal in a live run, open the requisition run in the sandbox.

  1. 01Ticketing

    Take the dispute and receive a credential for this account only. It expires when the dispute closes.

    Who approves
    No approval on this step
    On the record
    credential issued · this account only
  2. 02Email

    Read the customer's complaint and the invoice it disputes.

    Who approves
    No approval on this step
    On the record
    read-complaint · allowed
  3. 03Documents

    Compare the charged lines with the contract terms in the document store.

    Who approves
    No approval on this step
    On the record
    compare-contract · allowed
  4. 04Accounting

    Try to open the billing history of a second account under the same name. It is outside the permission for this job, so the step is refused.

    Who approves
    No approval on this step
    On the record
    read-other-account · refused · outside permission
  5. 05Accounting

    Post the credit for the overcharged line. The step waits until the billing lead approves it.

    Who approves
    Billing lead
    On the record
    post-credit · approved by billing lead
  6. 06Email

    Draft the reply to the customer with the corrected amount.

    Who approves
    No approval on this step
    On the record
    draft-reply · allowed

In short

  • Can an agent change a customer's plan or apply a credit by itself?Only within what your access policy allows for that job. A credit or a plan change you mark as sensitive waits for the person you name.
  • Does it touch the network?No. It works in order, ticketing, field, billing and document systems. Network elements and network management stay outside its permission.
  • What does a field contractor receive?The work order for that visit and the details it needs. Other customer details are removed before the pack leaves, and the record lists what was removed.
  • Can we show an auditor how a dispute was settled?Yes. The record holds each step, the approval and any refusal. An outside party checks it with the open verifier, without us.

Telecom workflows, and the state of each.

Built items run in the sandbox today. Designed items have their steps written. On-request items are scoped in the assessment.

Built
We have run it.
Designed
The steps and approvals are designed. It has not run yet.
On request
We scope it with you before we design it.
  • Designed

    Customer case intake

    A complaint or a request read, sorted and routed to the right queue. A person approves the reply that commits a credit or a date.

    See the workflow
  • Designed

    Billing dispute to credit

    The steps above: the invoice and the contract compared, a second account refused, and the credit held for the billing lead.

  • Designed

    Business order entry

    An order from an email or a form checked against the quote and entered. The order desk approves any line that differs from the quote.

    See the workflow
  • Designed

    Fault ticket to field work order

    The agent reads the fault ticket, pulls the service record and drafts the work order. The dispatcher books the visit.

  • Built

    Field packs with customer details removed

    The sandbox run sends a contract summary out with client identifiers removed. The same outbound check covers a pack for a field contractor.

    See the redaction
  • Built

    Equipment and spares orders

    The agents draft the order and check stock. An order above your threshold waits for a person. The sandbox run orders laptops.

    Run it in the sandbox
  • Built

    Late equipment from a supplier

    The agent follows up a late delivery across four systems, and the buyer approves the new date.

    Run it in the sandbox
  • On request

    Cancellation and transfer requests

    Requests checked against the account and the contract, for a person to confirm.

  • On request

    Partner and wholesale orders

    Orders that cross to a partner, with the same rules and a record on both sides.

Keep the assistant you already run

If a chat assistant already answers your customers, keep it. Its answer still has to reach the order, ticketing and billing systems, and today someone copies it across. That gap is the workflow we build.

If the assistant can connect over A2A or MCP, it enrols on Ares without a rewrite. It signs in as itself, it can do only what it was allowed to do for that job, and its steps go on the same record. The assessment confirms whether yours can.

The five guarantees

Every workflow on this page carries them. Each one has a limit, and we state it.

  1. 01

    Each agent can do only what it was allowed to do, for that job.

    The limit

    Permissions are only as good as the rules you approve.

  2. 02

    Sensitive steps go to a person.

    The limit

    You decide which steps are sensitive.

  3. 03

    Documents are inspected before an agent sees them, and answers are checked before they leave.

    The limit

    Filters cover stated patterns and languages.

  4. 04

    Every decision is recorded, including refusals, in a record an outside party can check.

    The limit

    It shows what agents did, not whether a business rule was wise.

  5. 05

    It can run in your building, on one small machine.

    The limit

    Local models differ from the largest cloud models.

What it does not do

  • It does not connect to network elements or network management. It works in your business systems only.
  • It does not set credit limits or decide which changes need a person. Your billing and service leads do, and Ares enforces the list.
  • In the workflows on this page, no reply that commits a credit, a date or a change reaches a customer before a person approves it.
  • The record shows what the agents did, not whether the tariff or the contract term behind a decision was right.
First step

Assessment, pilot, production.

Each step has a fixed scope and ends with something you keep.

  1. 01

    Workflow assessment

    A look at one process: where an agent can act, which steps go to a person, what a wrong action would cost, and what the data allows.

    What you get
    A short, paid look at one process, with your process owner.
    What you keep
    A written scope and a price for a pilot.

    Fixed price, quoted after one call.

  2. 02

    Pilot workflow

    One workflow on your systems, supervised, with the record on from the first run.

    What you get
    One workflow at a fixed scope, with your people approving the sensitive steps.
    What you keep
    A working workflow and a measured result.

    Fixed price, quoted after one call.

  3. 03

    Production and run

    The workflow in production on Ares, on your hardware or hosted in your country.

    What you get
    Support, and the next workflows.
    What you keep
    The workflow, and the record of every decision it made.

    Recurring fee for operation and support.

Questions and answers

Tell us about one workflow.

Name one queue where your staff copy a case from one system to the next. We will say whether an agent should carry it, and what the first step costs. The first step is a workflow assessment. Fixed price, quoted after one call.

A senior member of the team replies within two business days.