Appointments, September 2026
451–459 of 459 · by appointment date
9 shown
More columns
| Lead | Canton | Product | Broker | Appointment | Status |
|---|---|---|---|---|---|
| 4526 | TI | Supplementary (VVG) | Uetliberg Broker | 30.09.2026 | Held |
| 4472 | BE | Basic health (KVG) | Uetliberg Broker | 30.09.2026 | Held |
| 4500 | ZH | Supplementary (VVG) | Aare Vorsorge AG | 30.09.2026 | Held |
| 4475 | BE | Basic health (KVG) | Seeufer Finanzplan | 30.09.2026 | Held |
| 3925 | BS | Supplementary (VVG) | Seeufer Finanzplan | 30.09.2026 | Held |
| 4166 | BE | Basic health (KVG) | Rheinfall Assekuranz | 30.09.2026 | Held |
| 4165 | FR | Basic health (KVG) | Bergsee Finanz | 30.09.2026 | Held |
| 4242 | VD | Car | Säntis Partner | 30.09.2026 | Held |
| 4559 | ZH | Basic health (KVG) | Lindenhof Beratung | 30.09.2026 | Held |
How it's calculated
These rows
select lead_id, created_at, channel, canton, product, broker, appointment_at, appointment_status, contract_signed_at, invoiced_at, invoice_amount_chf
from leads
where appointment_at >= timestamp '2026-09-01 00:00:00' at time zone 'Europe/Zurich'
and appointment_at < timestamp '2026-10-01 00:00:00' at time zone 'Europe/Zurich'
and appointment_status in ('scheduled', 'held')
order by appointment_at, lead_id
limit 50 offset 450The row count
select count(*) as total
from leads
where appointment_at >= timestamp '2026-09-01 00:00:00' at time zone 'Europe/Zurich'
and appointment_at < timestamp '2026-10-01 00:00:00' at time zone 'Europe/Zurich'
and appointment_status in ('scheduled', 'held')
The app runs these queries with parameters; here the values are written in, so they can be read or pasted into psql.