Day-Two Operations

Day-two operations begin after the site is live and real customers can shop, book, submit forms, open tickets, receive email, and appear in reporting. This guide turns the console into a repeatable operating rhythm instead of a one-time launch tool.

Operating Model

Daily Opening Checklist

Run this at the start of each business day.

Daily Customer Triage

1. Open Inbox.
2. Sort by newest, unassigned, or highest-priority source.
3. Open each customer context before replying.
4. Check orders, bookings, forms, tickets, and communication history.
5. Assign ownership when a reply needs another operator.
6. Reply from the correct workspace identity.
7. Close, snooze, or escalate the item based on the team’s policy.

Daily Booking Operations

1. Confirm new bookings

   Steps: Review new bookings, verify intake, confirm payment or deposit, and make sure the assigned staff member sees the event.

2. Handle reschedules

   Steps: Use the manage-booking or console reschedule path, confirm calendar conflicts, and verify the customer receives updated details.

3. Handle cancellations

   Steps: Apply the cancellation policy, refund when required, update the booking status, and note the reason.

4. Manage no-shows

   Steps: Mark the booking accurately, follow the customer communication policy, and update staff notes.

5. Update availability

   Steps: Add schedule overrides for closures, special hours, holidays, staff outages, or capacity changes.

Daily Commerce Operations

1. Fulfill paid orders

   Steps: Review paid orders, confirm inventory, pack or prepare service delivery, update fulfillment status, and add tracking when available.

2. Handle pickup or delivery

   Steps: Confirm customer instructions, promised timing, contact details, and any delivery constraints.

3. Manage refunds

   Steps: Confirm refund eligibility, issue the refund through the approved payment flow, update order notes, and notify the customer.

4. Handle failed payments

   Steps: Review payment status, retry rules, customer messages, and product or booking reservation impact.

5. Watch inventory

   Steps: Update stock, hide unavailable products when needed, and verify the public shop reflects the change.

Daily Content And Site Operations

Use this rhythm to keep the public site current:

1. Review any time-sensitive homepage, banner, promotion, event, or seasonal content.
2. Confirm product, service, and booking entry points reflect current availability.
3. Publish approved page or story changes.
4. Check help content for questions that appeared in inbox or tickets.
5. Verify the public site after every content save.
6. Check social preview and search metadata for high-traffic pages when the change affects title, description, image, or canonical URL.

Weekly Business Review

Run this once per week with the workspace owner.

Monthly Administration

Review team access

Remove departed users, adjust roles, and confirm least-privilege access.

Review Stripe Connect

Confirm payout account, dispute contact, tax settings, refund handling, and statement descriptor.

Review Google integrations

Confirm analytics property, ads conversions, Business Profile links, and local business details.

Review domain and email

Confirm DNS, certificate, sender reputation, reply-to, and support routing.

Review policies

Keep privacy, terms, refunds, cancellations, waivers, shipping, and consent language accurate.

Review products and services

Archive stale offers, update prices, and remove expired promotions.

Review help content

Convert repeat support questions into public help articles or better form copy.

Incident Response

Treat these as customer-impacting incidents:

• Public site outage or production domain failure.
• Checkout cannot complete.
• Booking cannot complete.
• Customers are charged incorrectly.
• Emails are sent from the wrong identity or to the wrong recipient.
• Customer records, orders, bookings, or tickets appear under the wrong workspace.
• Google Ads traffic points to a broken or stale destination.
• A disconnected integration silently stops reporting or delivering operational events.

First Response

1. Identify the affected workspace, URL, customer path, and time window.
2. Stop new traffic or hide the broken public action when possible.
3. Preserve evidence: screenshots, order IDs, booking IDs, customer IDs, email timestamps, and integration event IDs.
4. Find the console source of truth that controls the broken public behavior.
5. Fix configuration first when the issue is configuration-driven.
6. Retest only the affected path.
7. Communicate the customer impact and next action to the workspace owner.

Common Incident Playbooks

Use these playbooks when a customer-facing path is already live and the team needs a fast, reversible response. The first goal is to reduce customer impact, preserve evidence, and identify the console source of truth; the second goal is to make the path safe before traffic resumes.

Checkout Is Broken

Check in this order:

1. Product visibility, inventory, variant, price, tax, and shipping settings.
2. Stripe Connect account status and payment method availability.
3. Checkout policy and required customer fields.
4. Domain, return URL, and confirmation URL behavior.
5. Order creation, payment status, notification, and customer portal history.

Mitigate by hiding the product, disabling the checkout entry point, or pausing ads until the purchase path passes again.

Booking Is Broken

Check in this order:

1. Service visibility, duration, price, staff, and location.
2. Availability, buffer, lead time, holidays, overrides, and capacity.
3. Calendar integration status and conflict behavior.
4. Intake, consent, payment, and confirmation requirements.
5. Booking record, calendar event, notification, and manage-booking URL.

Mitigate by hiding the service, adjusting availability, or moving the customer to a manual scheduling path until the booking path passes again.

Emails Are Not Sending

Check in this order:

1. Sender domain and reply-to settings.
2. Customer email address and opt-in state.
3. Notification template and trigger.
4. Internal recipient configuration.
5. Recent bounces, provider errors, and domain authentication.

Mitigate by using an approved manual communication path and recording the customer contact in the console.

Google Tracking Is Missing

Check in this order:

1. Correct Google Analytics property and stream.
2. Correct Google Ads account and conversion label.
3. Production domain is the landing URL.
4. Conversion event fires only after the intended customer action.
5. Consent, tag loading, and browser blockers.
6. Reporting delay windows before declaring data missing.

Mitigate by pausing campaign spend only when attribution is required for active optimization or compliance.

Change Management

Use this process for any change that affects public customer behavior:

1. Name the customer path affected by the change.
2. Identify the console source of truth.
3. Make the smallest possible configuration change.
4. Save and verify the public site.
5. Test the downstream record: customer, order, booking, ticket, form, notification, analytics event, or webhook.
6. Record the change in the operator handoff channel.

High-risk changes include:

• Payment settings.
• Domain and sender settings.
• Booking availability and cancellation policies.
• Product prices, inventory, tax, and shipping.
• Published navigation and homepage entry points.
• Google Ads conversion destinations.
• Webhook endpoints.
• Team access and admin roles.

Handoff Notes

Every operator handoff should include:

• What changed.
• Which customer path was tested.
• Which console record proves it worked.
• Which public URL was verified.
• Known customer impact.
• Owner for the next check.

Handoffs should be written so the next operator can continue without reconstructing the investigation. Include the exact public URL, console record, customer-visible state, and any action that was intentionally deferred.

Healthy Workspace Signals

A healthy workspace usually has:

• No unassigned urgent inbox items.
• Today’s bookings confirmed and visible to staff.
• Paid orders moving through fulfillment.
• Failed payments and refunds reviewed.
• Public site content matching current operations.
• Analytics and ads reporting current activity.
• Google Business Profile links pointing to live customer paths.
• Domain, email, and webhook integrations connected.
• Support questions feeding back into help content and forms.

When To Re-Run Launch QA

Re-run the relevant launch QA section after:

• A production domain change.
• A new product category, service category, or checkout path.
• A new paid campaign.
• A Stripe Connect account change.
• A calendar provider change.
• A major homepage, navigation, or policy update.
• A new email sender or notification workflow.
• A customer-impacting incident.