CX operations

Extract, track and deliver on every support promise.

Oathscript is the commitment-tracking layer for customer support teams who already know response-time SLAs miss the point. The reply is the easy part. The promise is the hard part — and the part that keeps the customer.

Request accessSee how it works

HubSpot, Gorgias or Zendesk — $99 / month to 2,000 tickets, then linear.

Customer-support commitment ledger — handwritten notes organized into a structured promise record.
§
Promise ledgerTicket #41792 · Gorgias
Open
Commitment

“Refund the $189 annual add-on by Tuesday, and add three months of credit for the outage.”

Customer
Marisol G.
Owning agent
Pavel R.
Due
Tue 2026-08-05
Value
$189 + 3 mo.
Awaiting agent confirmationLive
The position

A response is a reaction. A promise is a commitment.

Every support agent — and every AI assistant next to them — makes specific promises every day. A replacement by Friday. An escalation within forty-eight hours. Three months of credit. And most of those promises vanish into the transcript the moment the ticket auto-closes.

Dashboards that count replies do not see this. CX leaders do. Oathscript is built for the people who feel the gap between “we replied in eleven minutes” and “we are still two weeks late on the refund” — and want the second number to be visible, trackable, and owned.

How it works

Four steps from a transcript to a kept word.

No dashboard migrations. No retraining. Drop in an export and the first ledger is ready before your standup.

  1. 01
    Ingest

    Connect a ticket source

    Drop in your HubSpot or Gorgias ticket export. Daily, weekly, or on-demand — Oathscript reads transcripts and proprietary fields, never touches production.

  2. 02
    Structure

    Extract the promise

    Every natural-language commitment is lifted out with its customer, owning agent, due date, financial value, and ticket link — not a fuzzy embedding, a record.

  3. 03
    Prove

    Confirm with the agent

    Nothing is created or closed without an agent ’s sign-off. That single rule is why precision stays high and the noise of naive RAG pipelines stays out.

  4. 04
    Deliver

    Track to fulfillment

    Daily briefs list every open and overdue promise. The dashboard ranks who is holding and who is slipping — by agent, by team, by week.

What you get

The view your BI tool cannot give you.

Subject of the record

A promise, not a reply

Your dashboards count responses. Your customers remember commitments. Oathscript closes that gap — every "refund by tomorrow" and "we’ll replace this on Friday" becomes a record with a due date and an owner.

Confirmation gate

Agent-confirmed, never auto-closed

A promise is born only when the agent responsible confirms it. A promise is fulfilled only when the agent confirms that, too. The model proposes; the human disposes. False positives stop at the door.

Today, 9:14

Pavel has 3 candidate promises waiting on a confirm. Two will approve, one will reject — the AI was too generous with “we’ll look into it.”

Morning ritual

A daily brief, not a dashboard tour

Every morning, every agent and every manager gets a tight email: who owes what to which customer, what is overdue, what is disputed. Read in sixty seconds, act on in five.

The compounding asset

An outcomes dataset, eventually

Beyond the dashboard, Oathscript is building the dataset that does not yet exist anywhere: structured promise patterns linked to refunds, escalations, and cancellations. The view of CX that no BI tool gives you today.

Built for

The leaders who feel the reply–promise gap.

  • CX operations leaders

    You measure promise-to-fulfillment and refuse to ship a dashboard that is just a count of replies.

  • Support managers

    You need every agent’s commitments visible on Monday morning — not reconstructed from a Slack scrollback.

  • Trust & safety teams

    You already track escalations; you need the structured set of promises that preceded them.

  • HubSpot, Gorgias, Zendesk shops

    You have the transcripts. You have the volume. You are tired of looking at response-time dashboards.

Pricing

One price under 2,000 tickets. Linear above it.

Predictable math so growth does not buy a surprise invoice. No per-seat games, no enterprise-unlock-gates for things you actually use.

Starter

$99/ month

Up to 2,000 tickets processed monthly. Built for a single support team trying Oathscript on for size.

Scaling
Linear volume tiers above 2k.

  • HubSpot or Gorgias ingestion
  • Daily agent + manager brief
  • Open / Fulfilled / Overdue / Disputed states
  • Agent confirmation gate
Talk to us
Most teams

Team

Linearvolume

Beyond 2,000 tickets, pricing scales line-by-line so growth does not buy a surprise. Bring the whole CX org.

Scaling
Volume scales the same way.

  • Everything in Starter
  • Multi-team dashboards + rollups
  • Custom owning-agent taxonomies
  • Priority ingest + audit trail
Talk to us

Enterprise

Talkto us

For trust-and-safety, escalations, and regulated CX. SAML, custom retention, and the outcomes dataset add-on.

Scaling
Annual, with procurement-ready paperwork.

  • Everything in Team
  • SAML SSO + audit log export
  • Custom data residency
  • Outcomes-dataset access
Talk to us
FAQ

Questions we get in the first fifteen minutes.

If yours is not here, write to us and we will answer in plain language.

Ask anything

The next step

Keep the word your customer remembered you gave.

We are onboarding the first cohort of CX teams. Tell us what you promise, what slips, and what you would like to see next.

Request early accessWalk the four steps again

We read every message at oathscript@polsia.app.