01
Section
Problem
Foundation
If the requested slot is not confirmed, the request should stay visible.
Use Cases
Booking Requests
Appointments, reservations, and scheduled follow-up workflows.
Bookings need dates, times, and notes so the team can keep the calendar moving.
At a glance
What EnterestOS keeps visible
Always visible
Tracked
Who responded
Tracked
What needs a reply
Tracked
What is waiting
Tracked
What is completed
Tracked
Which projects are active
Tracked
What changed recently
02
Section
Solution
Priority
EnterestOS keeps the booking request open until the appointment is actually confirmed.
03
Section
Before EnterestOS
Lifecycle
The scheduling request sits in email and can get lost if the booking takes more than one reply.
04
Section
After EnterestOS
Closure
The calendar request remains visible until the slot is confirmed or completed.
05
Section
Workflow
Visibility
Keep the statuses small and obvious.
Reply ↓ Waiting ↓ Done
06
Section
Steps to Set Up
Visibility
Wire the booking page without changing the design.
- Create a project for the booking workflow.
- Capture the booking form fields.
- Generate the integration prompt.
- Add tracking after submit success.
- Submit one booking request and confirm it lands in the inbox.
07
Section
Form Structure
Visibility
Booking requests usually need time, contact, and notes.
export function BookingRequestForm() {
return (
<form>
<input name="date" />
<input name="time" />
<input name="email" />
<input name="phone" />
<textarea name="message" />
<button type="submit">Book appointment</button>
</form>
);
}08
Section
trackResponse() Call
Visibility
Track the request after the submit succeeds.
await enterestos.trackResponse({
type: 'booking_request',
payload: { date, time, email, phone, message },
});09
Section
Best Practices
Visibility
Make it easy to see whether the booking is confirmed or still pending.
- Use Waiting while the slot is being confirmed.
- Keep the request visible until the calendar is settled.
- Keep the original booking context attached to the submission.
- Close the loop only once the booking is actually done.
010
Section
Result
Visibility
The team can confirm appointments without losing track of what was requested.
011
Section
Common Questions
Visibility
Booking workflows should stay visible until they are truly done.
- What if the time changes? Keep the submission in Waiting until the new slot is confirmed.
- Can I keep the existing booking page? Yes, only wire the submit path.
- What status should I use first? Usually Reply.