Deposits and payments

The payment link goes out during the conversation, and its real status is tracked to the end — paid, pending, or nothing at all.

7 days, 20 answered calls, no card

The task it takes over

A deposit asked for during the conversation gets paid; one asked for the next day does not. It is that simple, and it separates a confirmed booking from a slot held for nothing.

This add-on creates the payment request at your provider, sends the link to the person, and tracks the real status of that payment rather than the hope it went through. A file changes state once money arrives, not once a link was sent.

It decides nothing on your behalf. Cancellation, refund and exception rules stay yours: the conversation applies them where they are clear, and passes the situation to whoever is responsible where they are not. Refunding is no automatic act.

Step by step

  1. Request

    The provider's link, rather than an improvised amount

    The payment request is created at your payment provider, on the amount your rules set for that service. The conversation sets no price that is not in your price list.

  2. Send

    During the conversation, rather than after

    The link goes out on the channel where somebody already is. A deposit sent later is a deposit to chase, which is exactly what this avoids.

  3. Track

    The real status, to the end

    Status comes from the provider. Until the payment is confirmed, the file says so, and a retry creates no second payment request.

  4. Stop

    Follow-up ends on receipt

    Once payment arrives, follow-up stops and the file moves on. Where it does not arrive, whichever rule you set decides what happens to the booking.

What the add-on covers

The add-on covers your business’s payments. It creates the payment request at your provider and tracks its status until the money arrives, for the files you authorised.

It replaces neither accepting an estimate nor authorising a repair. A connected store order and a restaurant order already carry their own payment: in those cases this add-on is not needed.

What this changes, in practice

Salons, gyms, classes & shops

A deposit reduces no-shows at the busiest hours. A cancellation rule is stated as somebody books, rather than discovered afterwards.

Restaurants & caterers

Groups and events confirm with a deposit. A held date stops being a verbal promise, and a room knows what is genuinely booked.

Contractors & trades

A materials deposit ahead of ordering is common. The amount comes from whatever you defined for that type of work, and the trace stays on the customer file.

Garages & auto repair

A specially ordered part gets paid up front in many shops. The payment request is attached to whichever repair order it belongs to.

What it receives

  • A payment provider and an authorised account
  • Deposit amounts set by your rules
  • Files where a request is authorised
  • Cancellation, refund and exception rules

What it produces

  • A payment request created at your provider
  • A link sent on the channel of the conversation
  • A status tracked and reconciled, uncertainty included
  • A situation passed to a responsible person where a rule falls short

A refund, an exception and an out-of-rule cancellation are your decisions. A payment request does not turn into permission to refund.

What the add-on includes

The add-on carries its own monthly volume of payment requests, which you follow in your app.

  • Payment requests per month, reset at each period
  • A retry on the same payment does not count a second time
  • Service texts carrying the link are included in your base
  • Connected store orders belong to the Store orders add-on

Your contract with your payment provider stays yours, at its own rates.

With your payment provider

The merchant account stays yours, and the money reaches you. The connection is authorised from your account at the provider.

  • Payment providerIt creates the payment request, receives its status and matches it to the file, with the permission you give from your merchant account; the merchant contract stays between the provider and you.

Questions about this add-on

Does the money pass through Zenvox?

No. The merchant account stays yours and the money reaches you, under your contract with your payment provider.

Does the file move once the link is sent?

No. The file changes state once money arrives. Status comes from the provider; until the payment is confirmed, the file says so, and a retry creates no second payment request.

Can it issue a refund?

No. A refund, an exception and an out-of-rule cancellation are your decisions: a payment request does not turn into permission to refund.

I already sell through connected orders. Do I need this as well?

Not for those orders: a connected store order and a restaurant order already carry their own payment, and this add-on is not needed in those cases. It serves any other billing.

Where does the deposit amount come from?

From your rules for that service. The conversation sets no price that is not in your price list, and the request is created at your provider on that amount.

Where to next

What comes ahead of payment, or a full store order.

Deposits and payments

The payment link goes out during the conversation, and its real status is tracked to the end — paid, pending, or nothing at all.

Start your free trial7 days, 20 answered calls, no card