Skip to main content
Audact
See the offer

Integration · RA-MICRO

Intake and time capture, without the retyping.

Planned · no date set

Inbound client triage, conflict-check intake and time capture, written back into the matter rather than typed twice. The part that makes this a legal product rather than a phone product is the professional boundary: an agent may take the facts, and it may not give the advice.

What the agent produces per call

{
  "event": "call.completed",
  "outcome": "intake_requested",
  "outcome_source": "conversation",
  "confirmed_by": null,
  "receipt_id": "rcpt_01HX7K9M3P4Q5R6S7T8U9V",
  "article_50": { "disclosed": true, "clause": "1", "at_turn": 1 },
  "scope": { "pack": "legal_de", "locale": "de-DE", "escalated_to_human": true, "at_turn": 9 },
  "write_back": {
    "system": "ra_micro",
    "matter_ref": "2026/0841",
    "time_entry_minutes": 12,
    "note": "Erstkontakt, Sachverhalt aufgenommen, Rückruf RA vereinbart"
  }
}

Worked example. Acme GmbH and Nova Industries are fictional; no customer data appears here.

escalated_to_human with the turn number is the field that matters here. It records the moment the conversation left the agent's competence.

What applies to the call

The caller must be told they are speaking to an AI system, at the latest at the first interaction.
Regulation (EU) 2024/1689, Art. 50(1) and 50(5)
Where the caller's data reveals a special category, the narrow grounds apply.
Regulation (EU) 2016/679 (GDPR), Art. 9

What Audact governs in the call

Article 50 disclosure at the top of the call, recorded.
In controlled testing
Professional scope under the Berufsordnung: the agent takes facts, it does not advise.
In controlled testing
Privileged turns kept in their own compartment, out of general retention.
In development
Write-back of matters, time entries and document references into RA-MICRO.
Planned

Sector

The first call is the one that never gets billed.

A first contact takes fifteen minutes, produces facts that need writing down, and is almost never captured as time. Taking it properly (the parties, the dates, the conflict check) is administration, and administration is what an agent is for.

The Berufsordnung draws the line at advice, and so does the gate. Where the caller asks what they should do, the call goes to a lawyer and the receipt records the turn where that happened. That record is the difference between an agent that helps and one nobody in the firm will authorise.

Setup

Four steps, once the integration ships.

  1. Connect Audact to your RA-MICRO instance through the partner API.
  2. Map agent personas to matter types, fee structures and practice areas.
  3. Configure the professional scope rules and the disclosure wording.
  4. Run in shadow mode (matter notes mirror without committing), then switch to active.

Questions

Can the agent run the conflict check?
It collects what a conflict check needs (parties, opposing parties, subject matter) and hands it over. Whether a conflict exists is a judgement, and it stays with the firm.
What happens to privileged content?
It goes into its own compartment with its own key and is excluded from general retention. Its chain entry stays, so the sequence remains checkable after the content is gone.

Do not wait for the integration

Every integration will be built on the same six endpoints. They run inside the managed platform; no public API is served on api.audact.ai yet, apart from the published Merkle roots. Where a sector system exposes an API, the shorter route is to call it from your side and let Audact govern the conversation.

See the API

Related