OWNER UPDATE · APPOINTMENTS & PAYMENTS
Your appointment panel.
Upcoming appointments, payment verification, form submission status, WhatsApp and Google Meet in one private view.
Deploy the update below before opening the panel for the first time. Use the Google browser profile for the account that owns the calendar.
Open private appointment panelThis page contains setup instructions only. Appointment data is loaded inside Google Apps Script after checking the owner’s Google identity. The public patient booking page stays accessible.
1. Replace the complete Code.gs
Open your existing booking project in Google Apps Script. In Editor → Code.gs, select all the contents and paste the complete file below. Click Save project.
2. Replace the complete Agenda.html
In Editor → Agenda.html, replace all the contents with the complete file below, then click Save project. The owner panel, English calendar and appointment management page are already included inside Code.gs; no additional Apps Script file is needed.
3. Deploy a new version
- Choose Deploy → Manage deployments.
- Select your existing web app and click Edit (pencil icon).
- Under Version, choose New version, then click Deploy.
- Keep the existing web-app URL and deployment settings. Return here and click Open private appointment panel.
Keep all existing Script Properties and triggers. No setup function, new secret or Telegram pairing is required. The backend-only form-status view has already been configured in Supabase.
Using the panel
- View upcoming appointments or the last 30 days. Search by name or email and filter payment status. Counts apply to appointments loaded; use Cargar más / Load more when available.
- Select your display time zone. Each card shows the appointment time, patient contact details and service.
- Open WhatsApp, Google Meet or the Calendar event directly from the appointment.
- View whether the pre-session form is awaiting submission, was submitted after this booking, or was submitted earlier. Form answers remain in the separate clinical portal. An unavailable status is shown if the portal cannot be checked.
Confirm a Payoneer payment
- Check the actual payment in your own Payoneer account.
- Find the matching appointment and click Marcar como pagada / Mark as paid.
- Check the box confirming you verified receipt of USD 35 for this appointment, then confirm.
- The payment is recorded as verified. For new pre-bookings, Meet is prepared and the same Calendar event is confirmed before the invitation and final email are sent. The patient receives the final confirmation in the booking language, including the date, local time, Google Meet and management link.
If something is interrupted
If the result is uncertain, use the same confirmation button to check it again. The server reads the existing payment record and uses one confirmation-email key per appointment. Repeated clicks do not send another confirmation.
If payment was saved but email delivery is uncertain, the panel keeps the payment verified and asks you to check Sent. It does not automatically resend an ambiguous email. If Calendar or Meet is still being prepared, payment stays verified and the time remains held; use Complete appointment confirmation. The existing maintenance trigger also retries. A confirmed paid appointment with no email delivery attempt offers Complete confirmation delivery.
Private access
The panel requires the active calendar owner’s Google account on every request. If Google does not identify that account, access stays blocked. Open the link directly in that Google browser profile; do not change the public deployment to run as every visiting patient.
The signed panel access expires after 30 minutes. Details are hidden after 15 minutes of inactivity or when you click Ocultar datos / Hide details. This hides the panel; it does not sign you out of Google.
Verification
Automated checks cover authorization, expired access, manual verification, Calendar interruption recovery, duplicate email prevention, bilingual messages and client states using mocked Google services. Supabase metadata-view permissions and a backend-role read were checked against the configured project. The new Apps Script deployment, owner-account access on your device and live final email delivery still require verification after deployment.