Refunds and No-Shows for Celebrity Video Call Bookings

A booking with a celebrity can fail in three different ways, and each one needs its own rule. A recorded video can arrive late. A scheduled call can be missed by the fan or the talent. A live event can be cancelled. If your terms treat all three the same, you will refund when you should not or refuse when you should refund, and you will be arguing each case from scratch.

This guide gives you a rule for each case, a table of fault and default outcome, a dispute process, and the card-network facts that sit behind a chargeback. It is written for an operator of a platform like the white-label Thrillz clone we sell, but the rules apply to any marketplace selling talent time. It is not legal advice; consumer rules differ by country, so ask a local adviser to review your final text.

Why bookings fail

Most failures come from a short list of causes. Knowing them tells you which rule to write.

• Talent unavailable. The talent is travelling, ill, busy or simply does not open the request. For a recorded request the effect is lateness; for a session it is a missed call.
• Fan absent. The fan forgets, arrives late or cannot get online.
• Technical failure. A dropped connection, a calling-service problem, or a phone that will not record.
• Time-zone mix-up. The fan and the talent read the same time differently. This is the most common avoidable cause of missed calls.
• Brief problems. The video is made but does not match the instructions, usually because the brief was vague.
• Platform error. A booking is double-booked, a notification fails, or a slot shows as free when it is not.
• Event cancelled. A live session is moved or called off by the talent or the operator.

Some of these are fault on one side and some are no one's fault. A policy that separates them is fairer and easier to defend. The sections below do that.

Three cases, three rules

Write one rule per case and a default outcome. The table is a starting point, not a legal text; adjust it to your market and your roster.

Cameo's terms of service illustrate the first row. They say the talent has up to seven days or longer to fulfil or decline a request, and that if a request is not fulfilled within the stated timeframe the platform may refund or credit the booking, or convert it to a standard request and refund the difference. They also say a completed video cannot be returned or refunded, and a tip is not refundable. That is a useful model: delivery controls refunds, not satisfaction.

Case one: the late recorded request

This is the simplest rule and the one most likely to be tested. The window starts when the talent can see the request and ends at a stated time. If the talent has not delivered or declined by then, the order goes to refund. Decide three things.

1. The window. A typical setup gives talent a fixed timeframe, for example 24 to 72 hours. Cameo's talent page says talent have four days; its terms say up to seven days or longer. Choose a window you can keep.
2. The fan's warning. Show a notice that the window is closing, and tell the fan what happens next, so a refund is not a surprise.
3. The remedy. Refund to the original payment method, platform credit, or conversion to a longer window. Say which, and whether the fan chooses.

Case two: the missed scheduled session

Here fault matters. Define "present" first: a person is present if they have joined the session within a set number of minutes of the start. Decide the grace period, for example 10 or 15 minutes. If the talent is absent, the fan gets a refund or a rebooking. If the fan is absent after the grace period, the talent kept the time free and is paid. If both joined and the call failed, treat it as a technical failure. Keep a record of join times so you can tell which case applies.

Case three: the cancelled live event

An event sold to many fans is the largest exposure, because one cancellation creates a refund for every ticket. State in the terms that the operator may cancel or reschedule an event, that ticket holders may then choose a refund or a transfer, and when the refund is paid. Where the event happens but the fan cannot attend, say whether tickets are non-refundable.

What the platform does today

In the product we deliver, the delivery window and refund conditions are settings in the admin panel. Fans pay when they request or book, and the money is tied to the order. If a request is not delivered in the agreed window, the fan may be eligible for a refund under the rules you configure. Admins review refund requests, disputes and policy violations in one dashboard and issue refunds. Fans follow order status in real time, and direct chat lets a fan clarify a brief before the video is made, which prevents the kind of misunderstanding that creates refund requests.

At launch, most operators decide refunds by hand. That suits low volume, because staff can judge odd cases, and it gives you a record of what actually goes wrong before you automate anything. When volume grows, you may want more: automatic cancellation and refund when a window lapses, no-show handling for sessions, rebooking flows, and deadlines that differ by talent tier. We set these up for your build, with the exact scope confirmed with us at kickoff, and you can describe your policy on the contact page. The Thrillz clone features page lists the admin and booking tools that ship with the platform.

If you are choosing software, ask any vendor to walk you through a late order, a refund and a payout on a live demo; the Thrillz clone script demo logins let you try the fan, talent and admin paths yourself, including a refund issued from the dashboard. One practical order of work avoids rework: write the policy, run it by hand for a few weeks, note the cases it did not cover, and then automate the ones that repeat.

Time zones and reminders

A missed call is often a time mix-up rather than a decision. Two habits remove most of them.

• Name the time zone in every confirmation. "Thursday 19:00" is not enough. Write the date, the time and the zone, and show it in the fan's own zone where you can.
• Send reminders to both sides. One a day ahead and one shortly before the start. The product has email and push alerts for bookings; a reminder schedule is a notification setup you configure, and we can set the sequence for your build.
• Put the join link in the reminder. The fewer taps, the fewer late arrivals.
• Watch daylight saving changes. Bookings across a clock change are a known source of off-by-an-hour errors. Re-send confirmations when a session falls close to one.

Our guide to celebrity video message occasions adds the date-driven side: gift buyers have deadlines, so the delivery window must be shorter than the date risk, and the checkout page should show the last safe day to order.

Write it into your terms

A policy that exists only in your head cannot be enforced. Put each rule where the fan sees it before paying, and again in the confirmation. A short block near the pay button works better than a link to a long document.

Consumer law varies. Some places give buyers cancellation rights for online purchases; others treat services at a set date differently from goods. As one example, the FTC's guidance on its mail, internet or telephone order rule says the rule applies to merchandise and does not cover services, which shows that a rule written for goods may not decide your case. Do not assume a rule applies or does not; ask counsel in each market you serve. For the money side of the terms, read our guide to high-risk payment processing if your gateway classes your business that way.

Handling disputes

A dispute is a fan and a talent disagreeing about what happened. Use the same steps every time so that decisions are comparable and you can explain them.

1. Collect evidence. The brief, the delivery or session log, join times, chat messages, and any message from either side.
2. Check the rule. Find the case in your table. Is it a late request, a missed session, a cancelled event or a brief problem?
3. Decide. Apply the default outcome. If you make an exception, write why.
4. Notify both sides. Tell the fan and the talent the decision in plain words, with the reason.
5. Act. Issue the refund, credit or rebooking, and adjust the talent's earnings if needed.
6. Record it. Keep a short note of the case and outcome. Over time, the log shows which kind of booking causes problems, and you can change the offer or the terms.

The admin dashboard collects refund requests, disputes and policy violations in one place for this. Speed matters: a prompt and fair reply to a late order usually ends the matter, while silence leads to a complaint to the card issuer.

A worked example

These numbers are invented. A fan books a 30-minute call priced at 120, and the platform keeps 25%, so the platform share is 30 and the talent share is 90. The talent does not join. After the grace period the fan writes in.

The example shows two things. The refund costs the platform money even when the platform did nothing wrong, because processing fees are often not returned. And the talent's record matters: repeated absences are a talent management issue, handled by a conversation and, if needed, suspension, as your terms with talent allow.

Gateway and chargeback considerations

Fans pay through gateways on your merchant accounts, so the gateway's dispute rules apply on top of yours. Read them before you launch. Stripe's documentation on how disputes work is a useful example of what a gateway describes, and other providers publish equivalent rules. As of October 2026, it describes these points for card payments.

• A dispute begins when a cardholder contests a payment with their bank. The disputed amount, plus a dispute fee, is debited from the merchant's balance, and the bank, not the gateway, decides the outcome.
• Card networks typically allow cardholders to dispute within 120 days of the original payment, and when a customer pays for a future service or event the window can start on the event date, not the payment date.
• A merchant who responds usually has 7 to 21 days to submit evidence, and the whole process can take two to three months.
• You cannot issue a refund outside the dispute process while a dispute is open, and the dispute fee generally is not returned even if you win.
• Some networks send an inquiry before a formal dispute. Answering it, or refunding in full, can close it without a dispute fee.

For a booking platform, the event-date rule matters. A fan can pay today for a session in six weeks, and the dispute clock may run from the session date. The consequence is practical: keep your booking records for a long time, and do not delete session logs after a month.

What to prepare before a chargeback happens:

1. A clear name on the card statement, so fans recognize the charge.
2. Stored evidence per booking: brief, delivered file, attendance log, confirmation emails showing the time and the terms.
3. A fast route to a refund for a fair complaint, because a refund is cheaper than a lost dispute plus a fee.
4. A named person who answers gateway notices within the deadline.
5. A monthly look at the share of bookings that become disputes. If it rises, change the offer.

Your gateway and your market set the exact rules, so ask your provider. We connect the gateways you choose, and the accounts and their fees are yours.

Operator checklist before the first booking

1. One rule written for each of the three cases, with fault, default outcome and decider.
2. A delivery window you can keep, and a notice that the window is closing.
3. A grace period for sessions and a definition of "present."
4. Time zone and daylight saving handling in confirmations and reminders.
5. Terms shown near the pay button, with the refund path stated.
6. A dispute process with six steps and a place to record each case.
7. Evidence stored for each booking for at least the length of the dispute window.
8. A named person for gateway notices and a monthly dispute review.
9. A legal review of the terms in each market.
10. A test run: one late order, one missed call and one cancelled event, taken through refund and payout.

Where to go next

Write the three rules first and test them against five real-looking cases before you publish. If you are still choosing which interactions to sell, read what the Thrillz app category is and Thrillz vs Cameo; the more scheduled formats you add, the more rules you need. The software price is the published price on the Thrillz clone development cost page, and costs such as refunds and payment fees sit around it. When you are ready, tell us about your policy on the contact page.