ChairHold
Tactical

How to handle a rescheduling request as a solo beauty pro

· 22 min read · back to blog

A rescheduling request looks like the polite version of a cancellation. The client is not abandoning the appointment — they are moving it. The relationship stays intact. The deposit stays on file. The booking continues. But a reschedule that arrives 18 hours before the appointment, from a client who rescheduled this same booking twice already, is not meaningfully different from a same-day cancellation. The chair is still empty. The slot is still unfillable. The difference is that the word "reschedule" carries none of the policy weight that "cancel" carries in a well-written booking policy — which is exactly why clients use it. This guide covers the full system for handling reschedule requests: what happens to the deposit, how many reschedules to allow per booking cycle, how to detect the client who is using reschedule as a softer cancellation, the operational difference between a within-window and outside-window reschedule, and the scripts for each scenario.

Rescheduling is not cancellation — until it is

The operational distinction between a reschedule and a cancellation is timing and intent. A reschedule within your policy window — typically more than 48 hours before the appointment — means the client has given you enough advance notice to potentially fill the slot, and their intent is to rebook rather than exit the relationship. A cancellation with that same 48-hour notice is functionally identical in terms of your calendar impact but carries different policy weight: if you have a cancellation fee, it triggers; if you have a deposit with a non-refundable clause after the policy window, it may not apply.

The ambiguity lives in the late reschedule. A client who contacts you 20 hours before a Tuesday morning appointment and says "I need to reschedule — can we do next week?" has produced the same outcome as a last-minute cancellation: an empty slot with zero fill probability. The difference is that your cancellation policy probably says something about what happens to the deposit if a client cancels within 24 hours, but may say nothing specific about what happens if they reschedule within 24 hours. That gap is where most solo pros lose money and relationship equity simultaneously — they feel they cannot apply the cancellation clause because the client technically rescheduled, so they absorb the slot loss, the deposit remains in limbo, and the pattern repeats next month.

The fix is to write a reschedule policy that is explicit — not as part of the cancellation clause, but as its own named section — that covers four scenarios: within-window reschedule (standard), outside-window reschedule (forfeiture or transfer with conditions), reschedule limit per booking cycle (the chronic rescheduler cap), and the deposit hold window if the new slot is not booked immediately (the indefinite-reschedule-hold prevention clause). Each of these is worth handling in its own section, because each produces a different conversation and requires a different script.

The four types of reschedule requests

Type 1: Client-initiated, within policy window (>48h notice)

This is the standard case. The client messages you more than 48 hours before the appointment, explains they need to move it, and wants to find a new slot. The slot is still potentially fillable — some clients who contact you can fill a 48-hour-out opening; for complex services like color corrections or lash installs, the fill rate is lower because not every walk-in can absorb a 2-3 hour slot, but for haircuts and simple color services, 48-hour openings fill reasonably well during normal seasons.

Policy response: deposit transfers to the new slot. One reschedule per booking cycle at no cost to the client. Confirm the new slot in the same message (do not leave the rebooking open-ended). If no new slot is agreed within 14 days, the deposit is forfeited — this is the indefinite-hold prevention clause. Without it, deposits sit in limbo while the client "looks at their schedule" for months, tying up your calendar management and creating an unresolvable booking state.

This is also the most common reschedule type, and it is genuinely fine. The system is working. The client gave adequate notice, you have a path to fill the slot or at minimum moved the appointment to a time they will actually attend. The only error to avoid here is letting the deposit float indefinitely on an unbooked future slot — confirm the new time in the same message and set the 14-day forfeiture window if they cannot commit.

Type 2: Client-initiated, outside policy window (<48h but >same-day notice)

The client contacts you 18-36 hours before the appointment. This is the gray zone. It is close enough to the appointment that fill probability drops sharply — a 24-hour opening for a 2.5-hour color service may fill 15-25% of the time under normal conditions; for the same opening during peak season, slightly better; for a specialized service like a lash install or PMU session where the client needs to have done a patch test and have intake paperwork on file, fill probability approaches zero.

Policy response: treat the outside-window reschedule the same as a late-cancellation for deposit purposes. The deposit is forfeited or a portion of it is retained (you define the percentage in your policy — common ranges are 50% retention for 24-48h reschedule, 100% retention for same-day or under-24h reschedule). The client may still rebook at full price with a new deposit for the new slot. The reason to enforce this rather than extending the same within-window grace is that the financial risk is identical — your material cost is partially or fully consumed (ordered product, reserved time), and the slot is effectively unfillable.

Most solo pros do not enforce this. They transfer the deposit to the new slot regardless of timing because the word "reschedule" softens the obligation. The cumulative cost of this pattern is significant — across 8-12 late reschedules per year at an average service value of $145, a pro who treats all reschedules identically regardless of notice timing is effectively absorbing $1,160–$1,740 in uncompensated slot losses annually that their written cancellation policy would have covered if the client had used the word "cancel" instead.

Type 3: Client-initiated, same-day or <24h notice

A same-day reschedule is a cancellation with a rebooking ask attached to it. The slot is gone. Fill probability for a same-day opening on a color service is 4-8% under normal conditions — nearly zero. The deposit should be handled exactly as a same-day cancellation would be under your policy: forfeited in full. The client can rebook for a future date with a new deposit.

The key failure mode here is the pro who hears "reschedule" and thinks "this is different from cancel — I should waive the penalty because they are still coming, just on a different day." Same-day notice changes nothing about the slot loss. The distinction that matters is whether you had enough notice to fill the slot, not whether the client's intention is to rebook. A client who cancels with 72 hours notice and a client who reschedules with 6 hours notice have produced opposite outcomes for your calendar — the former gave you a fillable window; the latter did not.

Type 4: Operator-initiated reschedule (you need to move the appointment)

This happens. You take a personal day unexpectedly, you are sick, your space is unavailable, a family situation arises. When you initiate the reschedule, the deposit situation is reversed: the client's deposit must transfer in full to the new slot with no conditions. If the client cannot make the new slot you propose, the deposit is refunded in full. No forfeiture language applies on operator-initiated changes.

The pro's obligation here is also timeliness: give as much notice as possible. A same-day operator reschedule on a color client who has already driven to the shop, found parking, and sat in the chair is operationally catastrophic for the relationship regardless of how the deposit is handled. The policy cannot retroactively repair that experience — the only lever is advance notice.

A practical detail: if you anticipate needing to reschedule a specific client because of a scheduling conflict you created (double-booked, miscalculated service time), proactively contact them at least 48 hours before. Same-day operator reschedules for non-emergency reasons are avoidable with basic calendar hygiene and should be rare — if they are happening more than once or twice per quarter, the calendar management system itself has a problem.

The deposit transfer framework: what happens to the money

The deposit was collected before the appointment as a commitment anchor. It covered at least the adjusted material cost of the service (material cost × 1.30) and served as evidence that the client would actually show up. When a reschedule request arrives, the deposit question is: does the commitment still exist in a form that is worth preserving?

The answer depends entirely on notice timing and whether this is the first reschedule on this booking cycle. Here is the decision matrix that most well-run solo practices use:

The 14-day new-slot confirmation window is often missed in policies written by solo pros. Without it, a client can "reschedule" indefinitely by accepting deposit transfer after deposit transfer without ever committing to a real date. The deposit technically remains on account, but it is doing nothing to protect your calendar — it is just money held against a booking that may never materialize. The 14-day window converts an open-ended float into a concrete deadline: if we cannot find a slot within two weeks, the commitment that the deposit represented has expired.

The 14-day window also helps the chronic rescheduler situation. A client who accepts a reschedule that results in a 14-day rebooking window, then fails to book within that window, has effectively self-selected out of the process — the deposit is forfeited automatically by policy, and you do not have to initiate a confrontational conversation about chronic rescheduling.

The reschedule limit: how many times is too many

One reschedule per booking cycle is the standard for most solo beauty practices. A booking cycle is defined as the period from when a client books an appointment through when that service is rendered and complete. Within that cycle — which might span two to four weeks from booking to service date — the client gets one reschedule with deposit transfer if they give adequate notice.

The second reschedule request on the same booking is the flag. Clients who reschedule twice before a service has been rendered are demonstrating that they have either a genuine scheduling problem that makes the commitment structure of a deposit booking unsuitable for them right now, or they are testing whether "reschedule" will continue to work indefinitely as a soft exit from a booking without triggering the forfeiture clause.

Both of those scenarios resolve the same way: the second reschedule is treated as a cancellation. The deposit is forfeited under your cancellation policy terms. The client is welcome to rebook at any time with a new deposit and is subject to the same policies. The message is not punitive — it is a clear statement that the booking structure requires actual commitment, and that two reschedules within one cycle exceeds what the commitment structure is designed to absorb.

The one-reschedule limit prevents a specific failure mode that is almost invisible until it becomes a pattern: the client who books, reschedules once, reschedules again, reschedules a third time, and finally no-shows six weeks after the original booking date — with the original deposit still nominally "on account" because each reschedule was framed as a continuation of the original booking. When you look back at that slot in your booking system, you see one client, one deposit, three months of calendar clutter, and ultimately an empty chair. The one-reschedule limit is the mechanism that prevents that chain from forming.

The chronic rescheduler: the reschedule-as-cancellation pattern

The chronic rescheduler is a different problem from the client who reschedules a single booking twice. The chronic rescheduler books, attends perhaps 60-70% of their appointments, and reschedules the remaining 30-40% — not on a single booking cycle but as a persistent relationship pattern across months or years. Each individual reschedule appears to be within policy: first reschedule on a given booking, often with enough notice that it looks legitimate. The problem is only visible when you look at the pattern across all their appointments rather than at each appointment in isolation.

Identifying the chronic rescheduler requires tracking at the client level, not the booking level. In a booking system where each appointment is treated as an independent transaction, you will not see the pattern — each reschedule is within policy, so each one gets absorbed individually. In a client-level view — what is this specific person's booking history — the pattern becomes obvious: they have rescheduled 4 of their last 7 appointments. That is a 57% reschedule rate, which is not a scheduling problem. It is a commitment problem.

Why does this happen? Chronic reschedulers have typically discovered that "reschedule" carries less consequence than "cancel" — the word triggers no policy, no fee, no uncomfortable conversation, no deposit forfeiture — so they use it reflexively when they are not sure they will make an appointment. They book with genuine intent, something comes up, and rather than canceling (which feels final and implies they are breaking a commitment) they reschedule (which preserves the relationship and implies the commitment is merely deferred). This is not malicious — it is a natural response to an asymmetric incentive structure where reschedule has no consequence and cancel has a defined one.

The fix is to make reschedule-as-cancellation visible and name it. Once a client has rescheduled 3 of their last 6 appointments, or 2 of their last 3, the pattern is real enough to address. The conversation is not a confrontation — it is a policy clarification delivered matter-of-factly: your practice has a one-reschedule-per-booking-cycle limit and you are flagging that the rescheduling pattern is approaching the point where the booking structure may not be a good fit for their current schedule.

A subset of chronic reschedulers will course-correct when the pattern is named. They were not aware it had become habitual. They will rebook and maintain better, and the relationship continues. A smaller subset will not adjust — they will reschedule the next appointment too, and the one after that. For those clients, the one-reschedule-per-cycle limit eventually triggers deposit forfeiture, and the relationship naturally resolves without a confrontational firing conversation.

The reschedule-as-cancellation detection flag

One pattern deserves specific attention: the client who reschedules consistently within 24-48 hours of the appointment. This is the most diagnostic timing for reschedule-as-cancellation behavior because it corresponds exactly to the period when the client knows the appointment is coming, something else has come up, and they have two options: cancel (and face the late-cancellation forfeiture) or reschedule (and avoid it). The client who reschedules twice in three appointments within that 24-48h window is almost certainly using reschedule to avoid the cancellation policy.

The distinction between this pattern and a client who genuinely has scheduling instability: the genuine scheduling-instability client usually reschedules with more notice, not consistently in the 24-48h window. A client with a job that shifts schedule at the last minute reschedules at the last minute across all their obligations — their pattern is erratic. The reschedule-as-avoidance client reschedules specifically in the window that produces the maximum benefit (avoiding the cancellation policy) with the minimum notice that still allows the word "reschedule" to be used without triggering your within-24h policy. The timing is too consistent to be coincidental.

Once you have identified this pattern in a client, the practical response is to change their tier in your mental model of their account — not to fire them immediately, but to treat their next booking as higher-risk. For complex and high-value services (full color, lash installs, PMU), consider requiring an elevated deposit for their next appointment. For simpler services, the standard deposit plus the one-reschedule limit will eventually resolve the pattern naturally — when the second reschedule triggers forfeiture, the behavior either changes or the client exits the book.

How deposit-first booking changes the reschedule dynamic

The entire reschedule management framework above presupposes that you collected a deposit at booking. This is not a minor assumption — it is the structural difference between a system that can enforce a reschedule policy and one that cannot.

In a DM-first booking model where no deposit is collected upfront, a reschedule request arrives and you have zero leverage. You can note the reschedule, accept it, move the calendar entry, and hope the client shows up for the new slot. You cannot apply forfeiture because there is nothing to forfeit. You cannot enforce the one-reschedule limit because the second reschedule on a booking with no deposit produces the same outcome as the first: an empty slot that cost you nothing to fill (no deposit refund) and produces nothing (no forfeiture revenue). Without a deposit, the "reschedule limit" is policy language with no mechanical enforcement behind it — a statement of preference, not a real constraint.

In a deposit-first booking model, the reschedule request has a real object to work with: the deposit that is already collected. The deposit transfer framework above becomes executable because there is money to transfer or forfeit. The one-reschedule limit becomes enforceable because the second reschedule triggers deposit forfeiture per the policy the client agreed to at booking. The chronic rescheduler pattern self-corrects more quickly because each reschedule either costs the client something (outside-window forfeiture) or uses up their one within-policy reschedule (triggering forfeiture on the next event within that cycle).

The show rate difference also matters for the reschedule context. Deposit- confirmed clients reschedule at a lower rate than DM-first clients — the deposit itself reduces the probability of a reschedule request because the client has already put money into the appointment and has a stronger incentive to actually attend. Industry data on solo beauty booking systems consistently shows that deposit-confirmed appointments have reschedule rates of 8-14%, while DM-first bookings that reach the 48-hour mark without a cancellation still reschedule at 20-28%. The deposit did not just change what happens when a reschedule arrives — it reduced the frequency of reschedules in the first place.

This is the compounding effect. Fewer reschedules means less policy application, less awkward conversation, less calendar management overhead, and less reliance on the one-reschedule limit to protect the book. The deposit does work before the reschedule conversation ever needs to happen.

Writing your reschedule policy

The reschedule policy should live as a named section in your booking policy, separate from your cancellation clause. Most booking platforms allow a policy block that clients read and accept at checkout — if yours does, this text should appear there. If your booking is still done through DMs with manual calendar management, the policy should be linked in your bio and referenced in your booking confirmation message.

A complete reschedule policy in plain language:

Rescheduling

One reschedule per booking is allowed at no additional cost when requested more than 48 hours before your appointment. Your deposit will transfer to the new appointment date. A new date must be confirmed within 14 days of the reschedule request or your deposit will be forfeited.

Reschedule requests made within 48 hours of your appointment (but more than 24 hours before) result in 50% of your deposit being retained. The remaining 50% may be applied toward your rebooked appointment.

Reschedule requests made within 24 hours of your appointment are treated as same-day cancellations: your deposit is forfeited in full. You are welcome to rebook with a new deposit.

A second reschedule on a single booking will be treated as a cancellation regardless of notice timing. Deposit forfeiture terms apply as stated in the cancellation policy.

The language above is direct and does not use softer framings like "we understand life happens" or "we try to be flexible." That framing signals that the policy is negotiable, which invites exceptions. The policy is stated as fixed procedure, not as conditional rules with goodwill exceptions. This is the same principle that applies to cancellation policy language: the moment you imply flexibility, you create the expectation of flexibility, and enforcing the policy later requires more friction than if the policy language had been neutral from the start.

Scripts for each reschedule type

Script 1: Client >48h reschedule (first time, within window)

When a client sends a reschedule request with adequate notice and this is their first reschedule on this booking:

"Got it — no problem on the reschedule. Your deposit carries over to your new slot. I have [specific available times] open this week and [specific available times] next week. Which works for you? If you need more time to check, let me know within 14 days — after that the deposit won't be able to hold without a new booking confirmed."

Key elements: confirm the transfer explicitly (the client needs to hear it, not just assume it), offer specific times rather than asking them to "check your calendar and get back to me" (open-ended rebooking asks convert poorly), and state the 14-day window matter-of-factly as part of the rebooking confirmation, not as a warning.

Script 2: Client 24-48h reschedule (outside window, first time)

"Thanks for reaching out. Because this is within 48 hours of your appointment, my reschedule policy applies — I'll retain 50% of your deposit for the slot, and the other 50% is available as a credit toward your next booking. I have [specific available times] if you'd like to get something on the books. The credit is good for 30 days."

State the retention matter-of-factly at the top rather than apologizing for it or burying it. Offering specific rebooking times immediately reduces the probability the client disengages entirely — most clients who receive this message will rebook if a clear path is offered. A 30-day credit window is long enough to feel reasonable and short enough to prevent indefinite float.

Script 3: Client same-day / <24h reschedule

"I received your message — because this is same-day, my policy treats this as a same-day cancellation: your deposit won't carry over. You're welcome to rebook anytime and a new deposit will apply. I hope everything is okay."

The final sentence softens without changing the policy outcome. Do not apologize for applying the policy — it was agreed to at booking. The short message format is intentional: same-day situations involve a time-sensitive window where you may still be trying to fill the slot, and a long message wastes time.

Script 4: Second reschedule on same booking (reschedule limit reached)

"I see this is the second time we've needed to move this appointment. My policy allows one reschedule per booking — at this point, this falls under my cancellation terms, so the deposit won't transfer to a new slot. You're absolutely welcome to rebook anytime — just know a new deposit will apply and the same policy will be in place. I hope we can find a time that works better."

The phrase "I see this is the second time" grounds the message in a factual observation rather than an accusation. Naming the policy clause ("one reschedule per booking") makes the outcome predictable rather than arbitrary. The offer to rebook is genuine — this is not a firing, it is a policy application.

Script 5: Addressing the chronic rescheduler pattern (proactive conversation)

"I wanted to flag something before we confirm your next booking. Looking at your history, you've rescheduled [X] of your last [Y] appointments — I want to make sure the booking structure works for you. Going forward I'll be applying the one-reschedule-per-booking policy strictly, including deposit forfeiture on second reschedules or reschedules outside the 48-hour window. If your schedule has gotten less predictable, I'd rather we figure out a timing approach that actually works. Happy to chat through it."

This conversation is uncomfortable enough that most solo pros avoid it indefinitely. The avoidance is costlier than the conversation — each unremarked reschedule reinforces the pattern. Naming the pattern once, with factual data (not accusation) and a clear statement of going-forward enforcement, is almost always enough. Most clients do not want to be fired and will adjust when they understand the pattern has been noticed.

Script 6: Operator-initiated reschedule

"I need to reach out about your [date] appointment — I have to reschedule due to [brief reason]. I'm so sorry for the inconvenience. Your deposit is fully transferred to whatever new date works for you, and if the options I have available don't work with your schedule, I'll refund it in full. I have [specific available times] — does any of those work?"

The apology is warranted here because you are the source of the disruption. The deposit outcome is stated explicitly (full transfer or full refund if unavailable) before offering times. Give at least two to three specific options rather than asking them to suggest times — the burden of flexibility is yours when you initiate the reschedule.

Handling pushback on reschedule policy

Three objections appear regularly when reschedule policy is applied for the first time with an existing client who has not encountered it before:

"I didn't know about this policy." If the policy was not stated at booking, this is a fair point and you should waive the forfeiture this time while making the policy explicit going forward. If the policy was visible at booking (in the checkout flow, in the confirmation message, in your booking page), acknowledge that it may not have been read but apply it — and follow with: "Going forward it's in your booking confirmation so you'll have it on file." Do not waive a policy that was clearly stated because the client says they were not aware of it — that establishes that claiming unawareness suspends the policy.

"I'm still coming — just on a different day." This is the core reschedule-as-no-consequence framing. The response is a restatement: "I know, and I'm glad you want to rebook. The timing is what the policy covers — it is about whether the slot can be filled, not about whether you plan to come back. A [same-day/within-24h/second] reschedule means the slot is effectively lost, which is what the deposit covers." Do not get into a debate about intent. The policy covers timing, not intent.

"But I've been coming here for two years." Acknowledge the relationship genuinely, but do not waive the policy. "I appreciate that, and I want to keep seeing you. This policy applies across the board because it is the only way the booking system is fair to everyone — I cannot make exceptions without applying them to all clients at the same tenure. The policy works the same for you as for any client."

Six common mistakes

No written reschedule policy. The most expensive omission. Without a written policy, every reschedule conversation is a new negotiation with no anchor point. This produces inconsistent outcomes across clients, creates resentment when one client perceives another was treated more favorably, and makes enforcement impossible without creating a conflict from scratch each time.

Treating all reschedules identically regardless of notice timing. A client who reschedules with 72 hours notice and a client who reschedules with 8 hours notice have produced different outcomes for your calendar. Treating both the same rewards the second client at the expense of the first and removes any incentive to give early notice — all reschedules become consequence-free, so the timing collapses toward last-minute.

No reschedule limit per booking cycle. Without a one-reschedule limit, a single booking can be rescheduled indefinitely. The client who reschedules three times and never shows has cost you three rounds of calendar blocking, three rebooking conversations, and one unrealized service slot — none of which would have been prevented by having a deposit without a reschedule limit. The limit is what the deposit protects.

No deadline for confirming the new slot. Accepting a deposit transfer without a deadline for booking the new appointment creates an open-ended liability: you are holding a client's deposit against a booking that may never materialize while the deposit prevents you from considering the account closed. The 14-day confirmation window closes this loop.

Not tracking reschedule patterns at the client level. If you only review bookings individually and not by client, the chronic rescheduler pattern is invisible. A client who reschedules 40% of their appointments looks like a series of individual policy applications — each one handled correctly — rather than a pattern that warrants a conversation. A simple note in your booking system or a client tracking spreadsheet is enough to surface this.

Avoiding the chronic rescheduler conversation. Indefinite avoidance of this conversation does not make the pattern stop — it reinforces it. Every unaddressed reschedule teaches the client that the pattern has no consequence. Naming it once — with data and without accusation — either resolves it or accelerates the natural exit of a client who was always going to create more friction than revenue.

Three-year compound: with and without a reschedule system

Consider two solo colorists with identical service menus and pricing. Colorist A handles reschedules case by case, has no written policy, and transfers deposits without conditions regardless of notice timing or how many times the booking has moved. Colorist B has a written reschedule policy, the one-reschedule limit, the 14-day rebooking window, and enforces outside-window forfeiture at 50%.

Both see approximately 10 reschedule requests per month across their books. Colorist A: all 10 reschedules result in deposit transfer, no forfeiture. Of those 10, about 3 per month are late reschedules (24-48h notice) and 1-2 per month are same-day reschedules. Two of those late and same-day reschedules per month result in no-shows on the rebooked appointment — the client rebooked but did not come. Average service value: $148. Direct cost of each no-show after reschedule: approximately $90 in unrecovered material and time cost. Monthly loss from late/same-day reschedules that absorb slot losses without compensation: approximately $200-$260. Annual leakage: $2,400-$3,120.

Colorist B: 10 reschedules per month. 4 are within-window first reschedules (deposit transfers at no cost — this is expected and fine). 3 are outside-window (24-48h) first reschedules: 50% retention = $74 × 3 = $222/month retained. 2 are same-day: 100% retention = $148 × 2 = $296/month retained. 1 is a second reschedule on a booking cycle: treated as cancellation, deposit forfeited = $148/month retained. Total reschedule-related revenue retained per month: approximately $666. Annual reschedule-related retention: approximately $7,992.

Three-year gap: Colorist A absorbs $7,200-$9,360 in slot losses over three years from unprotected reschedules. Colorist B retains $23,976 in reschedule-related deposit revenue over three years that would otherwise be absorbed or waived. The combined gap across three years: $31,176-$33,336 — from one written policy and one consistent conversation when the limit is reached.

The actual gap will vary by vertical, service mix, and client base characteristics. Lash artists and color specialists who see a high proportion of complex services with high material investment will see larger gaps because the forfeiture amounts are larger. Barbers and brow artists with shorter, lower-cost services will see smaller absolute gaps but similar percentages. The structural dynamic is identical regardless of vertical: the reschedule without a system is absorbing losses that a written policy would have recovered.

Operational checklists

Checklist 1: Setting up your reschedule policy (one-time, 30-45 min)

Checklist 2: When a reschedule request arrives (per-event, 5-10 min)

Checklist 3: Quarterly reschedule pattern review (15-20 min, every 90 days)

Hold the chair before the no-show does.

$9/mo flat. Deposits straight to your Stripe. Early access is 90 days free.