When the receptionist creates a booking, refund, escalation or callback request, its email and enabled integration updates are now recorded alongside the saved request.
Interrupted update processing can resume separately, with checks to avoid queueing the same message twice. The conversation can continue without waiting for email delivery.
Saved requests retain their updates
For new bookings, refunds, escalations and callback requests created by the receptionist, the instruction to prepare related email and enabled integration updates is recorded with the request. A processing interruption between those steps no longer leaves a saved request without that instruction.
Verification and the checks required to save the request still apply. Retrying an update does not create another booking, refund or escalation.
Updates recover independently
Email and integration updates track their progress separately. A problem preparing an email does not prevent an enabled integration update from being queued, and the same recipient or integration message is checked before another copy is added.
Refund updates retain available proof-upload details. If processing stops before those details are ready, the update may take longer while recovery checks run. Email preferences and enabled integration settings still apply.
What to expect
The receptionist can continue after saving the request while its updates are prepared separately. Updates may arrive later, and repeated processing failures can still require checking. This does not guarantee that a recipient mailbox or connected service will accept an update.
These changes address request saving and update processing. They do not establish a measured improvement in end-to-end audible call latency.