Skip to main content
Audact
See the offer

Integration · Skribble

Spoken consent, then a qualified signature.

Planned · no date set

Skribble issues electronic signatures under eIDAS, including the qualified tier. The planned integration lets an agent trigger a signature request from inside the call and links the resulting certificate to the receipt for that conversation, so the consent that was spoken and the signature that followed sit in one bundle instead of two systems.

What the agent produces per call

{
  "event": "call.completed",
  "outcome": "signature_requested",
  "receipt_id": "rcpt_01HX7K9M3P4Q5R6S7T8U9V",
  "article_50": { "disclosed": true, "clause": "1", "at_turn": 1 },
  "consent": { "captured_at_turn": 14, "scope": "contract_execution" },
  "write_back": {
    "system": "skribble",
    "document_ref": "doc_2026_0841",
    "signature_tier": "QES",
    "linked_receipt": "rcpt_01HX7M2N3P..."
  }
}

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

linked_receipt is the point of the integration: the certificate is not a loose file, it hangs off the conversation that produced the consent.

What applies around the signature

A qualified electronic signature has the equivalent legal effect of a handwritten signature.
Regulation (EU) No 910/2014 (eIDAS), Art. 25(2)
The person must be told they are speaking to an AI system, before anything is agreed.
Regulation (EU) 2024/1689, Art. 50(1) and 50(5)
Consent must be demonstrable by the controller.
Regulation (EU) 2016/679 (GDPR), Art. 7(1)

What Audact governs in the call

Article 50 disclosure at the top of the call, recorded.
In controlled testing
The gate reads a recorded consent state with its scope and its position in the call.
In controlled testing
Receipts chained, so the consent and what followed it are one sequence.
In development
Triggering a Skribble signature request and linking the certificate back.
Planned

Sector

The gap between yes on the phone and a signature.

In insurance, legal and financial work, agreement on a call is the start of a process, not the end of one. What follows is a document, a signature and a wait. The two halves usually live in different systems, so nobody can show in one place that the person who spoke is the person who signed.

Linking the certificate to the receipt closes that gap. It does not make Audact a trust service: Skribble issues the signature and carries that status. What Audact carries is the record of the conversation it came from.

Setup

Four steps, once the integration ships.

  1. Connect Skribble with your own subscription.
  2. Map document templates to the flows that may request a signature.
  3. Configure the consent wording and which tier each flow requires.
  4. Run in shadow mode, read the linked receipts, then switch to active.

Questions

Is Audact a trust service provider?
No. Skribble issues the signature under eIDAS. Audact records the conversation, the consent and the link between them, and it does not present its own artefacts as qualified anything.
Is the Skribble subscription included?
No. Nothing to order. A connection is scoped inside an applicable paid agreement; integrations are not priced separately. The Skribble subscription stays between you and Skribble.

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