Halfway through the call the agent offers to take the deposit, texts a Stripe Checkout link to the phone the caller is holding, and waits. They tap, they pay, they come back. Then the agent checks with Stripe and says the sentence every business wants said on a first call: "That has gone through, you are booked in."
In-call payments are in early access. The whole loop has been run end to end on a real phone call against a simulated gateway, and no business has taken a live payment on it yet. So this page is an invitation rather than a sales pitch: we are looking for a handful of businesses to be first, with us watching every call. We would rather tell you that here than let you find it out on a Friday.
Everything else an agent does ends with a note for somebody to action later. This ends with money in your account before the caller has put the kettle on.
You write the moment: when a job is booked, when an invoice comes up, when a deposit is due. The agent raises it in the wording you wrote, not in wording it invented, and only when the rule you set says it should.
A text goes to the number they are ringing from, on the same rails as every other text your agent sends. It carries your business name, the amount, and a link that opens a Stripe Checkout page belonging to your account.
On Stripe's own secure page, with the card in their pocket or the one their phone already has saved. Nothing is read out loud, nobody in your office types a card number, and the call keeps going the whole time.
Not the caller, and not itself. Our server asks Stripe about that exact checkout and answers the agent with the truth: paid and the amount, declined, or not finished yet.
"That has gone through, you are booked in." The one sentence that turns a maybe into a job, said while they are still on the phone rather than in an email they open on Tuesday.
The call, the transcript, the summary and the payment land together as one record. If the action was tied to a Xero invoice, the payment is noted against that invoice and your accounts inbox is emailed.
Payments are authored on the agent builder canvas, next to everything else your agent does. There is nothing to code and nothing the model gets to decide on its own.
Most actions are one figure: a $150 callout deposit, a $50 booking fee. Where the price genuinely depends on what the caller describes, you give the agent a floor and a ceiling instead and it works inside them. It cannot go a cent over your ceiling, and it cannot invent an amount. Off the rails, it takes the details and leaves the pricing to you.
You write the message that goes out and the agent drops the link into it. The model never composes the text, which is the same rule every other link your agent sends already follows. The Stripe page then shows your business name and the amount before anybody touches a card.
A condition you write in plain English: only once a job is booked, only for a first-time customer, only on the collections call. Silent otherwise.
The same loop on an outgoing call, so an agent chasing an overdue invoice can take the payment on the spot rather than promising an email.
An action is offered once per conversation and the link lasts half an hour. No caller gets pestered, and no link goes wandering off into a text inbox for a week.
This is the part worth being blunt about, because it is the part people quite reasonably worry about when a machine offers to take a payment.
You create a restricted API key in your own Stripe dashboard, ticked for Checkout Sessions and nothing else, and paste it in. It cannot refund, cannot move your payouts, cannot read your customers and cannot touch anything else. It is stored encrypted, never shown back in full, and you can revoke it inside Stripe at any moment without ringing anybody.
The checkout is created on your Stripe account, so the payment settles to your bank on your own payout schedule, on your own Stripe fees, with your name on the receipt. We are not the merchant, we do not hold funds in the middle, and we take no cut of a payment. Switch us off tomorrow and every payment you have taken is still sitting exactly where it was.
The card is typed on Stripe's own secure Checkout page, on the caller's handset, and that page belongs to Stripe rather than to us. No card number is spoken on the call, none is written into a transcript, and none reaches a Talkify server. What we keep is the amount, the currency, the outcome and Stripe's reference for the checkout.
A webhook is only ever a nudge to go and look. Whatever the outcome, we read it back from Stripe with our stored session id and that is what the agent is told, so the answer the caller hears is Stripe's answer rather than a guess made from what they said.
Where the action came off an overdue invoice, the payment is written back as a note on that invoice in your own Xero and your accounts address is emailed, so a person still sees it and reconciles it. We do not quietly write payment records into your ledger.
A payment is one thing the agent can do on a call, not the call. It still books the job, still answers the questions, still takes the message and still texts and emails you the lot within seconds, whether the payment happened or not.
Rules, not preferences. Each of these is enforced in the code rather than asked for politely in a prompt, because a payment is exactly where a well-meaning machine must not improvise.
The deposit line only works if the agent sounds like somebody you would hand your card details to. Ring ours, talk over it, change your mind halfway, ask it something awkward. Most people ring expecting a robot and hang up having had a conversation. No sign-up, no card, answering around the clock.
The loop is built and it has been run end to end on a real phone call. What it has not had is your customers on the other end of it, and that is the only test that counts.
We switch it on for you, with us watching. You start with one action, usually a deposit, on one agent. We sit over the first calls with you and read every one of them. If anything is off you tell us and we fix it that week, because at this stage there are few enough of you that we can. When you are happy, you widen it.
Nothing beyond the agent you already have. Payments are part of what an agent can do rather than a paid add-on, so there is no upgrade to buy, no per-transaction fee from us and no cut of what you are paid. The text is billed like any other agent text, and Stripe's own processing fee is between you and Stripe.
Anyone whose no-shows cost real money: trades taking callout deposits, clinics and studios holding an appointment, and anybody making collections calls.
A Stripe account and five minutes to make a restricted key. If you already take payments online, you already have everything.
The same loop runs on Windcave → for the many New Zealand businesses who bank that way. Nothing changes from the caller's side.
To start building your agent, complete the form, or ask our agent to get you started. No card needed for the demo.
The questions we hear most. If yours isn't here, ring our live demo agent on 03 242 1262, it'll either answer or queue a callback from a human.
The same in-call payment loop for businesses banking with Windcave rather than Stripe.
The agent rings the invoices that have gone past due, in your name and your wording, and can take the payment on the call.
How the agent handles a booking call end to end, and where a deposit fits into it.
What happens to the calls that arrive once the office is dark, which is when a deposit is hardest to chase.
Put your own numbers in and see what the calls you never hear about are worth.
What Talkify connects to today, and what your agent can do once it is connected.