For any business on Xero

Live Xero on the call.

The ledger knows who owes you. This rings them. Overdue invoices chased by a real phone call against your live Xero balance. The customer hears what they owe, gets Xero's own payment link while they are still on the phone, and leaves the call with a date. Disputes go to you. It stops the moment the money lands.

Get Paid: hear the call

Flat monthly, no call caps, 30-day free trial.

One call, one record

INV-1042

OutstandingRead from Xero at 10:40
Payment linkSent by SMS during the call
PromiseBank transfer by 30 Sep
Next follow-up1 Oct, not tomorrow
GateDNCR washed · AI disclosed

Kept against the invoice. A dispute logged in April stays on the record and stops the chase.

The problems this is for

If four of these are true of your debtor book, the rest of the page is worth reading.

  • The reminder emails went out on schedule and nothing happened next.
  • A customer got chased for an invoice they paid on Friday.
  • Somebody said they would pay by the 30th, and nobody wrote down which invoice or which 30th.
  • A dispute was raised in April and the chase has no idea.
  • Ringing debtors is the job that falls off the desk first, every single week.
  • You want to try this and you do not want anything writing into your ledger.

Read live

The balance on the call is the balance in Xero

Read at the moment of the call, never from a copy. An invoice paid this morning is not chased this afternoon. The payment link is Xero's own online invoice, so the money lands where it always did.

Read-only by default

It cannot write to your ledger unless you switch that on

The connection asks for read access to contacts, invoices and your item list, and nothing else. The writes it can do, a draft quote or invoice priced by Xero and the promise date as a note on the invoice, are one separate consent you grant deliberately.

The part you do not want to own

Compliance sits under the call

Do Not Call Register wash with evidence kept, calling hours in the debtor's state, public holidays, AI disclosure every time, and a record of every exception.

What it reads, what it writes

Connected by OAuth to your own Xero organisation. A practice connects once and narrows the key to the client organisations that opt in.

In XeroAccessWhat that means
ContactsReadsWho the debtor is, and the number to ring. Matched to the caller on an inbound call.
Invoices and balancesReadsOutstanding amount, days past due, and the oldest invoice, read at call time.
Online invoice linkReadsXero's own payment page for the invoice, sent by SMS while the call is still going.
Your item price listReadsOnly so a quote can be priced from your own book. Never written to.
Promise to payWrites, opt-inThe date the customer gave, written back to the invoice as a note in its History and Notes. Never the amount, status or due date. The same write scope as the drafts; it moves the next call either way.
Dispute, follow-up dateKept with usRecorded against the invoice in Office Voice, where it moves the next call.
Draft quoteWrites, opt-inA DRAFT Xero Quote built from your item codes and priced by Xero. We never send a rate, so we can never invent one. Needs the write scope you grant on purpose.
Draft invoiceWrites, opt-inA DRAFT invoice for a job marked complete, built from your item codes and priced by Xero, referenced to the job. One per job. Never authorised or sent by us; you release it in Xero. The same write scope.

Checked against the connector as at 26 September 2026. The connection is direct to your organisation and is not a Xero App Store listing, which is why it can stay read-only: there is no marketplace scope we have to ask for that we do not use.

The rules under every call

How we build, not legal advice. The long version is the compliance paper.

  • Says it is an AI, first

    Every call opens with the AI identification and the recording notice before anything else is said.

  • Do Not Call Register

    Every outbound number is washed against the register before a call. If the register cannot be checked, the call is not made.

  • Calling hours, by state

    Outbound calls land inside the permitted hours in the customer's own state, public holidays included.

  • Consent to the strictest state

    Victoria, Tasmania and the ACT need every party to consent to recording. We cannot know where a caller is, so that is the standard on every call.

  • A record on every call

    Recording, transcript and what was written into your system, kept under a proof id you can pull up when a customer disputes it.

What stays with you

  • Disputes, the moment one is named. The call finds it and stops.
  • Payment plans, write-offs, hardship, and anything a lawyer would call a demand.
  • Credit policy and who gets chased at all. You set it; the call obeys it.
  • Relationship-sized balances, which are pulled out and left to you.

Build it, or point the chase at us

The whole workflow is published as an open standard with a Xero stub to build against. You only pay us for the live calls behind it.

Free

Build it yourself

The Debtor Chasing standard: the ranking, the six conditions that must stop a chase, the promise as a date, and a pass test. The Quote Out standard covers the draft-quote side, priced only from your own book.

Open the standard →

Monthly

Get Paid, on Office Voice

Connect Xero, choose who may be chased, and the calls run inside the rules above. Flat monthly, no call caps, no per-minute overage, 30-day free trial, and read-only until you say otherwise.

See Get Paid →

Xero stays the ledger. The phone call is the part that was not happening.

See Get Paid
Already asking Claude about your Xero file? What the free connector does, and what it leaves to you.
Running client books for other businesses? The practice version, one key across every book.
Want a quote drafted from the enquiry, priced only from your own book? The Quote Out standard.