Cake emails you when a session books, and Google events carry the piece
Three ways a session can book, and all three now email you. A session Cake writes into your Cake sessions calendar carries the piece and the client, plus your request form answers. You set the deposit mode, the hold window, and how long a time offer stands.
Cake emails you when a session books
Cake emails you when a session books, whichever way it booked:
- a client picking a time
- a deposit you confirmed
- an approval where you waived the deposit
It names the client and the session, and it opens with the booking.
Google events carry the piece and the client
Available to artists who have connected Google Calendar.
A session Cake writes into your Cake sessions calendar carries the piece and the client, plus the answers to the questions on your request form, in the order you ask them. You reconnect nothing and grant no new access. Events Cake wrote before this change keep their old text until something rewrites them.
You set one deposit mode in settings
Settings holds one mode:
- collect the deposit in Cake
- collect it outside Cake
- waive it
The mode arrives preselected on every approval, and you can change it for one request without moving your default. Approval freezes the mode, so a later default change reaches new requests only.
Collecting outside Cake now takes a payment link of your own, beside Venmo, Zelle, and Cash App on the page where your client pays. Your client sees every destination you saved there. Collecting in Cake is not open yet, and Cake says so when you pick it.
You set the hold window and the time offer window
Cake set both before. You set them now. The hold window is how long a held time waits for your confirm. The time offer window is how long the times you offered stand before they lapse. Both sit in settings. With confirm every booking turned on, a client picking a time with no deposit holds it rather than books it.
Custom questions and the new-or-returning answer read in full
A custom question used to cut off after one line, and Cake was dropping the answer telling you whether a client is new or returning. Both read in full on the request page, in the email about a new request, and at phone width.
The lead reference names the thread
The reference the client led with now heads the conversation, the row in your thread list, and the client card on Home and Requests. Step through to another reference the client sent, or upload your own.
Smaller fixes 10 lines
- Clear your queue and Home says something different the next day. Home and Requests now count an approved request with a reply waiting the same way: it needs you.
- These updates thank the artist who asked for a change, by linking her Cake profile once she has said yes. This one thanks two.
- The handles releases, media, and changelog belong to Cake's own pages.
- A check blocks two words Cake overused from every email, and the note that welcomes you when you claim your handle reads plainer.
- Two practice studios run on production, so a change gets walked through a booking end to end before it reaches yours.
- Four tests that failed at random stopped failing.
- When Cake opens your studio to help you, it lands on yours, and a check runs that on every change.
- A release can no longer report success while the old files are still being served.
- The hourly production check reads the direct payment disclosure off the page.
- Founder work for today, the artist list, provisioning, waitlist reviews, and spend sit on one back office screen. The page they replaced is gone.
