DocsRequest early access
Product
Refunds in chatVerify the customer, find the payment, resolve it.Disputes & fraud warningsPrevent chargebacks, respond to disputes on time.Refund policy & simulatorClear rules, tested before you publish.Safety & auditWhy the AI can never move money.Payment analyticsApprovals, declines and alerts at a glance.TicketsYour team’s queue after the automation.CasesEvery request with its decision, step by step.
Solutions
Subscription softwareCancellations and forgotten renewals.Online storesDouble charges, deliveries, chargebacks.Digital goods & gamesFraud warnings and refund abuse.Online educationGuarantee refunds, by chat or email.Travel & bookingsLarge amounts, decided by people.Several countriesSeveral accounts, several currencies.Payment providersStripe, PayPal, Paddle, Adyen and more.Your own payment systemOne open contract over REST or MCP.Helpdesk teamsZendesk, webhook intake and email.
Developers
The Chargeless APIWebhooksAPI referenceYour own billing systemEvidence serviceprovidercheck
Resources
How it worksFrom customer request to resolution.IntegrationsProviders, channels and helpdesks.SecurityHow money and data are protected.FAQAnswers to the common questions.
DocsPricing
Request early accessSign in
Tickets

Response targets that keep the team on time.

Set reply and resolution targets per priority. Chargeless tells the right people when one is missed, and never touches the ticket.

Request early accessTickets: Overview

Three targets per priority

First response, next response and resolution, in minutes, per priority. The clock runs only while your team has the ticket.

  • First, next, resolution
  • Minutes per priority
  • Only while the team has it
Ticket settings in the merchant panel: response targets per priority and the limits on automatic replies.
Illustrative example, not real data

Breaches notify, never act

A missed target notifies the assignee, or owners and admins, in the panel and by email. It never reassigns, closes or replies.

  • Due and overdue in the queue
  • Panel and email notices
  • No automatic changes
Ticket queue in the merchant panel with a handed-off chat open, the reason it reached the team and the customer’s payment.
Illustrative example, not real data

Targets met, over time

Ticket analytics shows targets met per priority, breaches over time, and what is due or overdue right now.

  • Met rates per priority
  • Due soon and overdue
  • Breaches by day or week
Ticket analytics, SLA targets: first reply and resolution targets met, next reply breaches, targets by priority and tickets due soon or overdue.
Illustrative example, not real data

More in Tickets

Start with low limits. Raise them when the record shows it works.

Start in test mode, run your policy against your own history, and go live when the results meet your standards.

Request early accessHow it works
  1. 1A test workspace on your provider’s test mode
  2. 2Your past requests replayed against your policy
  3. 3Live with low limits, raised as the record allows