A release goes out while a patient fills your form, and the form resets. Keep their place through every deploy.

Worked example, step by step

1. 10:00Patient. Starts the intake form on her phone.
2. 10:02Developer. Merges a change to the doctors page. A new deployment goes live.
3. 10:03Vercel. Routes the patient’s requests to the deployment she started on.
4. 10:06Patient. Submits the form. Nothing she typed is lost.
5. 10:06Salesforce. The intake arrives as a new patient enquiry for the front desk.
6. 10:07New visitors. Get the updated doctors page.

The clinic ships updates during clinic hours, and no patient has to start the form again.

Worked example, step by step

1. Mon 11:00Developer. Adds two headlines behind one flag in the microsite.
2. Mon 15:00Account director. Checks both on the preview link with the client.
3. Tue 09:00Vercel. The flag shows headline A or B to each visitor.
4. Tue to FriSalesforce. Logs each lead with the headline the visitor saw.
5. MonAccount director. Shows the client which headline brought more leads, then switches the flag.

One site and one flag do the job of two microsites, and the client sees leads per headline.

Worked example, step by step

1. 14:00Customer. Opens the tracking link from the WhatsApp message.
2. 14:00Vercel. Streams the page. The parcel status and address show first.
3. 14:00Tracking database. Returns the driver’s last scan, which fills in a moment later.
4. 14:01Customer. Sees the delivery window and closes the page.
5. 17:00Service lead. Checks Speed Insights for how fast the page loads on phones.

Customers see their parcel status first, before the slower systems answer.