Skip to main content
SwiftCase
PlatformSwitchboardFeaturesSolutionsCase StudiesFree ToolsPricingAbout
Book a Demo
SwiftCase

Workflow automation for UK service businesses. Created in the UK.

A Livepoint Solution

Platform

  • Platform Overview
  • Workflow Engine
  • Case Management
  • CRM
  • Document Generation
  • Data Model
  • Integrations
  • Analytics

Switchboard

  • Switchboard Overview
  • Voice AI
  • Chat
  • Email
  • SMS
  • WhatsApp

Features

  • All Features
  • High-Volume Operations
  • Multi-Party Collaboration
  • Contract Renewals
  • Compliance & Audit
  • Pricing
  • Case Studies
  • Customers
  • Why SwiftCase

Company

  • About
  • Our Team
  • Adam Sykes
  • Nik Ellis
  • Implementation
  • 30-Day Pilot
  • Operations Pressure Map
  • For Your Role
  • Peer Clusters
  • Engineering
  • Careers
  • Partners
  • Press
  • Research
  • Tech Radar
  • Blog
  • Contact

Resources

  • Use Cases
  • Software
  • ROI Calculator
  • Pressure Diagnostic
  • Pilot Scope Estimator
  • Board Case Builder
  • Free Tools
  • Guides & Templates
  • FAQ
  • Compare
  • Glossary
  • Best Practices
  • Changelog
  • Help Centre

Legal

  • Privacy
  • Terms
  • Cookies
  • Accessibility

Stay in the loop

Cyber Essentials CertifiedGDPR CompliantUK Data Centres

© 2026 SwiftCase. All rights reserved.

Platform

Timeline · Audit & Evidence

Everydecision.Everyactor.
Everysecond.

Timeline is the SwiftCase audit logger. Every action — AI or human — recorded with actor, timestamp, resource, outcome, and severity. Per case. Per agent. Per second. Exportable as a regulator-ready evidence pack.

See an example timeline
Scope a 30-day pilot
Per case
Every action on the case file, in order. Routine field updates, tool calls, conversations, approvals, escalations, settlement events.
Per agent
Every action by a specific AI agent definition or human user. Filter by handler, by Switchboard agent version, by service account.
Per second
Sub-second timestamps mean event ordering is unambiguous. Critical for reconstructing the exact sequence of a TL conversation or escalation.

The Data Model

Six fields. Every event.

Timeline records actions in a structured shape that handlers, managers, and regulators can all read.

actor

The named human or attributed AI agent that performed the action. Every entry has an owner — there is no anonymous activity in Timeline.

timestamp

Per-second precision, UTC. Both event-time and ingestion-time captured. Timezone-aware reporting available for multi-region operations.

resource

What was acted on — case ID, agent definition, workflow, field, document, conversation. Every action ties back to a structured object.

outcome

Success, failure, or partial. Includes the structured result data — what changed, what failed, what was returned. Not just “something happened.”

severity

Low, medium, high, critical. Routine field updates are low; tool failures and escalation triggers are high; PII access and policy-guard breaches are critical.

filterable

Every dimension is queryable — by date range, actor, resource type, outcome, severity, or any combination. Fast on the case timeline; fast across the platform.

Example Timeline

A total-loss case, six events.

An anonymised slice of a Timeline for one TL settlement. Every entry attributed. Every outcome captured. PII redacted for this example.

Engineer · Sarah J.Medium

Set total-loss valuation on case CL-184729 (£8,450) with comparable market evidence pack attached.

Switchboard · TL-Settlement-v3Low

Presented engineer-set value to customer on outbound voice call. Comparable evidence shared symmetrically (3 below, 4 above).

Customer · verified via 2-stepLow

Customer agreed to value. Structured response captured: agreement_confirmed=true, hesitation_level=none, vulnerable_flag=none.

Switchboard · TL-Settlement-v3Low

Drafted settlement-offer email. Status: pending_approval. Routed to handler queue for review.

Handler · James R.Low

Reviewed and approved settlement-offer email draft. Sent to customer at 14:37 UTC.

Switchboard · TL-Settlement-v3High

Escalation triggered: frustration detection on customer turn (call CL-184811). Routed to engineer Sarah J. with full conversation summary.

No anonymous AI actions. Every Switchboard entry references a specific agent definition (and version) and ties back to the named engineer or handler whose configuration it is executing. Personal accountability, mapped to actions, by design.

Why It Matters

Built for the regulator who hasn’t arrived yet.

FCA SMCR, Consumer Duty, FOS file requests, GDPR right-to-erasure — all of them ask for the same thing. Timeline answers it.

FCA SMCR — every action has a named owner

Senior Manager Conduct Rules expect personal accountability mapped to actions. Timeline provides exactly that mapping — the engineer who set a value, the handler who approved an email, the manager who signed off a threshold change. No “the AI did it.”

FCA Consumer Duty — fair-outcome evidence by default

Consumer Duty asks for documentation that customers were treated fairly. Timeline produces that documentation as a side-effect of normal operation — what was offered, what was disclosed, what the customer said, who escalated when, and what the named human did about it.

FOS files — complete and structured

When a case lands at the FOS, you hand over a structured evidence pack: full transcript, decisions with attributed humans, comparable evidence shown to the customer, escalation events, and the resolution path. Not a hunt through inboxes.

GDPR / DPA — per-resource audit

Every access to personal data is logged with actor, purpose, and outcome. Subject access requests can be served from Timeline. Right-to-erasure preserves audit hashes while removing PII. ICO inspection is a query, not a project.

Outputs

Four ways Timeline gets used.

Same data, four audiences. Handlers see case timelines. Managers run cross-platform queries. Regulators get evidence packs. Engineers get webhooks.

Per-case audit timeline

Every action on a single case rendered as a chronological timeline. Used by handlers, managers, and complaint-investigators alike. No more “hunt the email thread.”

PDF evidence pack export

One-click export of a case’s full Timeline as a regulator-ready PDF. Filterable by date range or event type. Cryptographically signed with case hash for chain-of-custody.

Cross-platform queries

Filter all activity across the tenant by actor, resource type, outcome, severity, or date. Find every escalation last quarter. Every failed tool call. Every PII access by a specific handler.

API and webhook access

Stream Timeline events to your SIEM, data lake, or compliance tooling in real-time. Pre-built schemas for Splunk, Datadog, and generic webhook consumers.

FAQ

The procurement and compliance questions.

How long is Timeline data retained?

Default retention is seven years to align with FCA record-keeping expectations and FOS referral windows. Per-tenant retention policies can override this — longer for litigation hold, shorter for specific event types where regulatory requirements differ. Right-to-erasure under GDPR preserves audit hashes while removing PII content.

Can we customise event types?

Yes. Timeline ships with structured event types for common actions (case create, field update, conversation, tool call, approval, escalation, etc.) and supports custom event types for tenant-specific workflows. Custom events get the same filtering, retention, and export treatment as built-in events.

Does Timeline log AI failures and tool errors?

Yes — explicitly. Every tool call records its outcome (success/failure/partial), every escalation records its trigger reason (low confidence, frustration, explicit request, error), and every provider-failover event during AI resilience routing is logged. Failures are not hidden; they are evidence.

How does Timeline integrate with our SIEM?

Timeline events stream to webhooks in real-time with structured JSON payloads. Pre-built schemas for Splunk, Datadog, and generic SIEM ingestion are available. For higher-volume tenants we offer batched export to S3 / Azure Blob / GCS with deduplication and replay support.

Can we export to our own data lake?

Yes. Two paths: real-time webhook delivery for ingestion-as-it-happens, or a batched daily export to your blob storage with full schema metadata. Both preserve the full event structure including actor attribution and severity classification.

What about GDPR right-to-erasure?

When a data subject erasure request is processed, Timeline preserves the audit record (action occurred, by whom, when, on what resource type) but removes PII content from the event payload. This satisfies GDPR Article 17 while preserving the regulatory audit trail. Cryptographic hashes ensure the audit log itself remains tamper-evident.

How is this different from generic application logging?

Application logs are for engineers debugging code. Timeline is structured business-action logging designed for regulators, handlers, and customers. Every entry has a named human or attributed AI actor, a structured resource reference, and a regulatory-relevant outcome. You can hand a Timeline export to the FOS; you cannot hand them a Splunk query.

Pilot it on your noisiest workflow.

Run a 30-day pilot. We’ll set up Timeline on the workflow you choose, and you’ll see the audit trail your existing tooling can’t produce. No platform migration. No long lock-in.

Scope a 30-day pilot
See the HITL design
Platform security
UK hosting, RBAC, encryption
TL settlement
Audit trail in production
AI resilience
Failover events, also logged