Reservasi Immoderma

Problem

Problem

Campaign interest needs a focused handoff into a reservation process without pretending that a submitted form is already a confirmed clinical appointment.

Bryan's role and attribution

Bryan's role and attribution

A collaborative DSI and Immoderma system. Bryan contributed to translating the marketing journey into a clear digital reservation surface and operating handoff.

What exists

What exists

A public reservation form covering contact details, branch, treatment, date, time, notes, and explicit acknowledgement that WhatsApp confirmation is still required.

How it works

How it works

The visitor submits a request without logging in, the Immoderma team checks treatment and schedule availability, and the team confirms the reservation through WhatsApp.

Publicly evidenced stack

Publicly evidenced stack

The public page evidences a responsive web form and human WhatsApp handoff. Back-end and operational infrastructure are not publicly specified.

Known limitations

Known limitations

• Submitting the form does not guarantee availability; confirmation remains a human operational step.
• The portfolio does not publish customer submissions, patient records, internal scheduling data, or conversion metrics.
• The visible flow demonstrates the request experience, not the complete internal reservation operation.

What I learned

What I learned

• A clear reservation experience must distinguish request, verification, and confirmation.
• Human handoff can be a designed part of the system rather than a hidden exception.
• No-login flows reduce friction but need explicit consent and expectation setting.