- Ya
- 14 Agosti 2026, 06:01 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 67b575d
The callback already reached the member's calendar, as an event titled "Lead Callback" with their comment in the description. Nothing said whose call it was, nothing said what number to dial, and nothing led back to the lead — so a member looking at their calendar had to go and find the lead by hand, which is the search the calendar entry existed to save them. It now carries the lead's name in the title, their number in the location, and a site-relative deep link back to the lead on the event and in its description. The description repeats the contact details deliberately: a calendar is read where the CRM is not, and a callback you cannot act on without opening another application is a reminder to go and look something up. The lead page now composes a callback in the calendar's own event dialog, so the request can carry a whole event — title, guests, reminders, colour — and this passes all of it through. Every field but the instant is optional; a caller that sends only the original three still gets a properly titled, properly linked entry built from the lead. Resolving a callback withdraws its notification as well as cancelling its event. Otherwise a call made at two minutes past leaves a card still asking for it, and a snoozed one that comes back tomorrow to ask again.