- Shipped
- September 7, 2026 at 1:18 AM UTC
- Author
- Kamo
- Commit
- ee2790c
Scheduling a callback told the lead nothing. The dialog said so outright — "The lead is not notified" — and the only way to get a customer the time in writing was to leave the CRM and write the email by hand. With the box ticked, the lead becomes a guest of the callback's event. That is what the rest of the platform already means by "this person is coming": the ATTENDEE line is what lets their acceptance come back, the guest row is what records that they were told and at which SEQUENCE, and that same row disappearing is what retracts the call from their calendar when a member changes their mind. No column, no second copy of the truth. Three lifecycle points, because two of them are the ones a customer cannot recover from on their own. Booking writes to them. Moving the call writes again, at the next sequence, so their calendar replaces the entry rather than gaining a second one. Cancelling the callback retracts it — but marking one CONTACTED does not, because that call happened, and telling somebody you have just spoken to that it is cancelled is a lie their calendar would then act on. A lead with no address on file is never invited however the box was left: a guest with an empty address on the event would report an invitation that could not be sent. The lead is appended to whoever else is on the call rather than replacing them, and skipped when the composer already named them, so nobody is invited twice. The timeline records it, and deliberately as what was asked for rather than what was delivered — delivery is asynchronous and best-effort, and a note claiming a letter arrived would be worse than no note. But a colleague picking the lead up next has to be able to see that the customer already holds this time, or they ring them cold about a call they think was never mentioned.