Skip to main content

Telryn

Telryn helps a complaints lead at a lender or payments company find closed support conversations that should have reached the complaints register. It brings human and AI support contacts, policy deadlines, register entries and owner actions into one local report. Reviewers get a separate, blinded grading packet.

In the synthetic rehearsal, Mira tells the Fin agent about a duplicate charge on 4 August. “Even with a refund I want to know how this happened.” Fin refunds her and closes the chat. Two weeks later she calls, and an agent records a query. In October the lead can trace both contacts to the same charge, read Mira’s original words and see what the case manager still owes her. Under the example firm’s policy, the eight-week final-response deadline was 29 September. Registration has its own clock. Open the worked report

Install

For an analyst on Linux or macOS, use pipx with CPython 3.12–3.15 and SQLite. The base CLI has no third-party runtime dependencies. Run the two-week rehearsal from any directory. Choose a new output directory each time.

pipx install telryn
telryn demo --complaints --out runs/complaints-pilot

Open runs/complaints-pilot/2026-10-05/report.html and expand C102. The customer asked Fin to open a complaint about a duplicate charge. The register was still empty for that case at 08:00 UTC on 12 October. The case manager accepted it at 11:00. The register entry and completion record both arrived at 12:00. C108, Mira’s case, shows what a referral still waiting for acceptance looks like.

The command prints both report paths, shows each method’s results and saves the two-week comparison in comparison.json under the output directory. It also prints the command to verify a report with the separate rehearsal trust store. PyPI package · Walk through both weeks and check the source records

For a managed deployment, IT can import the signed Linux image for amd64 or arm64. Windows users can run it through Docker Desktop with Linux containers. The weekly job runs with networking disabled. The security review pack includes the data flow, outbound connections, storage responsibilities and an SPDX software inventory for each architecture. Container instructions · Download the security review pack

Run a week with your team

Start the private browser desk with telryn desk --out runs/desk. For a scheduled job, use telryn weekly /path/to/week.toml --out /path/to/new-run. Keep the team signing key and revision registry in persistent private storage. Weekly operating guide and scheduler example

  1. Set the scope. Support operations supplies closed conversations. QA supplies completed human reviews. The contact centre and AI agent owner supply transcript references and handoff records. Complaints supplies the dated register and action history. Record missing channels and who owns each gap.
  2. Issue the sample. The policy owner approves the rubric, clock rules and calendar. Choose a versioned FCA DISP, US Regulation E or CFPB Company Portal starter, or use the firm’s own policy. Preview what the grading budget can detect. Telryn draws from both flagged and unflagged conversations that ordinary QA left unreviewed. Policy packs
  3. Grade and follow up. Reviewers decide whether a case qualifies before seeing the register finding. Record second reviews and settle disagreements. The lead can verify the signed report, follow a case to its source passages, and check the deadline, register coverage and owner action. Evidence formats · Report verification

What the evidence supports

A clean sample can miss rare failures. If exactly 25 of 5,000 unreviewed conversations qualify and reviewers recognize every one, a uniform random sample of 50 has a 22.3% chance of finding at least one. Reaching 95% takes 564 first grades. Sampling assumptions

The rehearsal compares Telryn with a saved SQL search using the same records and staff budget. Across its 1,350 possible two-week draws, the saved search finds at least as many owner-accepted episodes in 96% of draws. The cases and staff times are synthetic. The field protocol measures whether either method brings action forward or saves staff time on a real queue. Field protocol

AI agents and integrations

  • Before an agent release, send synthetic complaints through the test agent and check its test register independently. A missing, late or unverifiable entry keeps the release gate closed. Agent test and adapter contract
  • For transcript screening, use structured signals or select Ollama, Azure OpenAI or regional Amazon Bedrock. Each definite extracted fact needs a cited passage. Bedrock users can install the AWS SDK with pipx install 'telryn[bedrock]'. Model setup and data handling
  • For intake and handoff, use helpdesk connectors or approved exports. The integration guide lists the evidence each provider exposes, including when the team must supply a lifecycle ledger. Supported integrations

Run telryn qualify to exercise the bundled checks. Architecture · Public support dataset · Contributing · Apache-2.0

Metadata

Release files for telryn 0.9.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for telryn 0.9.4
File Size Uploaded Provenance Actions
telryn-0.9.4.tar.gz 282.4 kB With provenance Details for telryn-0.9.4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for telryn 0.9.4
File Interpreter ABI Platform Actions
telryn-0.9.4-py3-none-any.whl Python 3 none any Details for telryn-0.9.4-py3-none-any.whl

Total release size: 636.4 kB

Release files / telryn-0.9.4.tar.gz

Download URL telryn-0.9.4.tar.gz
Size 282.4 kB
Tags Source
SHA-256 checksum
How to use checksums
e92582667926ad405be942350ffb9dd9d9e8fa52e33b87da73bf21b268e4c083
BLAKE2b-256 checksum
How to use checksums
7fa20357337b374a67d68e6a47a4baf5848cb97336f30dc926ccb451e2d1601c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 21, 2026.

Transparency log

Release files / telryn-0.9.4-py3-none-any.whl

Download URL telryn-0.9.4-py3-none-any.whl
Size 353.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b1f30794935ca6c22d75bf72a24a104114c8dac9a7e356edf78bebc3bcf8d141
BLAKE2b-256 checksum
How to use checksums
dbd5cfa2b9c31cd9450d792bd0944d8909004b77a3cc969913690bc28ff56b88
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 21, 2026.

Transparency log

Security for telryn 0.9.4

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for telryn-0.9.4.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 21, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page