Stop copying lead details onto the calendar event

FixSecurityService
Shipped
August 14, 2026 at 4:04 PM UTC
Author
Kamo
Commit
d3b36af

The event carried the lead's name, number, email and best time to call, copied into its description when the call was booked. A copy of a record that is still being edited stops being true the first time somebody corrects a phone number, and a calendar quietly asserting a line that no longer reaches anyone is worse than one asserting nothing at all. The number was also being copied into the event's location, which is the single most damaging field to have go stale. The event now stores what the member authored and nothing else: their note, and a location only if they typed one. The lead is named through sourceId and deepLink, and a new callback-context endpoint answers what the lead looks like right now — so the dialog shows current details every time it is opened, and a lead edited between booking a call and making it shows its new details. Also adds rescheduling. A pending callback can be moved or restated, and its calendar event moves with it: they are two views of one promise, and letting them drift means the lead page says one time, the calendar says another, and the reminder fires against whichever the member is not looking at. A callback booked while the mirror was failing has no event to move, so rescheduling creates the one that should have existed.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing