BPPP/smb-online
2
0
Fork 0
Code Issues 15 Pull Requests Actions Packages Projects Releases Wiki Activity

Booking confirmation email + customer self-service cancel/reschedule #18

New Issue
Closed
opened 2026-07-23 14:07:57 +02:00 by mivanchenko · 1 comment
mivanchenko commented 2026-07-23 14:07:57 +02:00
Owner
Copy Link
Copy Source

Parent

#14

What to build

The email side of the customer experience: a confirmation email on booking, and a token-linked
self-service page where a customer can cancel or reschedule without ever creating an account.

  • On booking creation (from ticket 2's engine, regardless of whether it came through ticket 3's
    public page or ticket 6's owner-manual-entry path), send a confirmation email via SMTP (mailcow)
    containing the booking details and a link embedding the ticket-2 signed cancel/reschedule token.
  • Sender address: the client's own domain (noreply@<client-domain>) when configured, falling back
    to a mivanchenko.de address otherwise. SMTP host/credentials come from environment
    configuration — this ticket does not set up the mail relay itself (that's a separate
    infra/triage item), only sends through whatever SMTP endpoint is configured.
  • A small "manage your booking" page reachable via the emailed link: shows the booking, offers
    "Cancel" and "Reschedule" (reschedule reuses ticket 2's slot-picking UI/logic against the same
    service/resource).
  • Clear feedback on an expired/already-used link (distinct from a generic error).

Acceptance criteria

  • Completing a booking (via ticket 3's public page) results in a confirmation email being sent
    with correct booking details and a working manage-booking link.
  • Following the link lets the customer cancel the booking, which is reflected immediately in
    the database (status becomes cancelled).
  • Following the link lets the customer reschedule to a different available slot for the same
    service/resource, protected by the same double-booking constraint as ticket 2.
  • An expired or already-used link shows a clear message distinct from a generic server error.
  • Sender address uses the client's configured domain when present, otherwise the fallback
    address.

Blocked by

  • #16 (Availability engine + booking API)
## Parent #14 ## What to build The email side of the customer experience: a confirmation email on booking, and a token-linked self-service page where a customer can cancel or reschedule without ever creating an account. - On booking creation (from ticket 2's engine, regardless of whether it came through ticket 3's public page or ticket 6's owner-manual-entry path), send a confirmation email via SMTP (mailcow) containing the booking details and a link embedding the ticket-2 signed cancel/reschedule token. - Sender address: the client's own domain (`noreply@<client-domain>`) when configured, falling back to a `mivanchenko.de` address otherwise. SMTP host/credentials come from environment configuration — this ticket does not set up the mail relay itself (that's a separate infra/triage item), only sends through whatever SMTP endpoint is configured. - A small "manage your booking" page reachable via the emailed link: shows the booking, offers "Cancel" and "Reschedule" (reschedule reuses ticket 2's slot-picking UI/logic against the same service/resource). - Clear feedback on an expired/already-used link (distinct from a generic error). ## Acceptance criteria - [ ] Completing a booking (via ticket 3's public page) results in a confirmation email being sent with correct booking details and a working manage-booking link. - [ ] Following the link lets the customer cancel the booking, which is reflected immediately in the database (status becomes cancelled). - [ ] Following the link lets the customer reschedule to a different available slot for the same service/resource, protected by the same double-booking constraint as ticket 2. - [ ] An expired or already-used link shows a clear message distinct from a generic server error. - [ ] Sender address uses the client's configured domain when present, otherwise the fallback address. ## Blocked by - #16 (Availability engine + booking API)
mivanchenko added the bookingready-for-agentenhancement labels 2026-07-23 14:07:57 +02:00
mivanchenko added a new dependency 2026-07-23 14:09:18 +02:00
#25 Decommission Easy!Appointments + n8n booking-sync
mivanchenko commented 2026-08-03 17:41:25 +02:00
Author
Owner
Copy Link
Copy Source

Shipped in commit 644c99e ("Booking confirmation email + customer self-service cancel/reschedule (#18)"). Closing — this was already implemented, just never closed in the tracker.

Shipped in commit 644c99e ("Booking confirmation email + customer self-service cancel/reschedule (#18)"). Closing — this was already implemented, just never closed in the tracker.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
booking
Booking / Easy!Appointments
 bug
Something is broken
 crm
Back office / CRM
 enhancement
New feature or request
 infra
Infrastructure
 n8n
n8n workflows
 needs-info
Waiting on reporter for more information
 needs-triage
Maintainer needs to evaluate this issue
 ops
Operational / runtime
 ready-for-agent
Fully specified, ready for an AFK agent
 ready-for-human
Requires human implementation
 security
Security / secrets hardening
 tech-debt
Refactor / debt
 wontfix
Will not be actioned
No Label booking enhancement ready-for-agent
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Administrator mivanchenko
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#25 Decommission Easy!Appointments + n8n booking-sync
BPPP/smb-online
Depends on
#16 Availability engine + booking API (create/cancel/reschedule)
BPPP/smb-online
Reference: BPPP/smb-online#18
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?