Appointment, add a summary of how it's going to proceed/work after a submission

Is your feature request related to a problem? Please describe.

Tried it for the first time this week, I loved it!
But I was mostly in the dark of how it was going to work until I actually had an appointment booked.
I checked the calendar manually 156261 times a day because I was afraid of missing a booking. 🙈

Here are the questions I was asking myself

• Will I receive a notification?
• Will I receive an email ?
• Will the event have a reminder set? If so, with my default settings?
• Will the guest be able to book an appointment in the following hour?

Describe the solution you'd like

I think some of the UI could be a bit more clear, like those areas:

• What does Add time before and after the event really means?
  Is it to ensure you have enough time between events?
• What does Minimum time before next available slot means?
  Is it the minimum time between now and the first available slot ?

Tooltips ?

It may seems relatively straightforward, bu the fact that I was not really sure made me think we should maybe improve a bit on this area. Maybe add a small with a tooltip?, I dunno...

Summary

But more importantly, I would like to have a small summary of what is going to happen, similarely to what File Requests is doing.
I think it adds clarity to non technical or new users:

Something like this maybe?

People will be able to make appointments at the times you specified. There will be a minimum of 1 hour between each existing event and they will not be able to choose a slot before 1 hour from now.

Once the booking has been made, you will receive an e-mail, a notification and the event will have a 15-minute reminder, in accordance with your settings.

Describe alternatives you've considered

No response

Additional context

No response

Start by inspecting the appointment creation UI and the existing File Requests summary referenced in the issue. Trace how appointment settings, notifications, reminders, and available slots are presented, then define a summary or explanatory tooltips that reflect the configured behavior and verify the wording in the relevant UI.