AESTARAestar / Docs / Guides / The schedule
The schedule
Day, week, month and timeline. The schedule is also what Ava reads before she offers a caller a time, which is why keeping it honest matters more here than in most software.
Schedule has four views — Day, Week, Month and Timeline — and a map panel underneath that drops a pin on each of the day's job addresses. Drag a window to move it, click one to edit it, and filter by person, service or status. Every stop opens Apple Maps or Google Maps with the address already in it.
The map is pins from job addresses, not live GPS. Nobody's truck is being tracked, and the screen says so. Live GPS is on the Upcoming list.
Why Ava can be trusted with it
Day, week and map views. Google Calendar sync. Ava checks the calendar before she offers a slot, and she only tells the caller they are booked once the booking has saved. She does not offer a time and hope.
Google Calendar
Connecting Google Calendar is optional and takes one click from Settings. Connected, the open times Ava offers are the real open times on that calendar, and the bookings land there so anyone already living in Google sees them. Not connected, she books into the Aestar schedule instead, which works fine — it just means Google does not know about it.
Other calendars are covered on the Integrations page along with everything else that is and is not connected.
Time
Techs clock in and log hours against a job from their own phone. That lands in Timesheets.
| What it does | Status |
|---|---|
| Day, week and map views | Live |
| Assign and reassign jobs | Live |
| Google Calendar sync | Live |
| Time tracking against jobs | Live |
| Live GPS for techs | Coming next |
| Maintenance plans and recurring visits | Coming next |
Still stuck?
Ask Ava. She answers questions about Aestar itself — pricing, setup, what she does on a call — and she will tell you when something is not built yet.
Generated from the Aestar codebase at commit ceb26e3, last shipped September 23, 2026. Prices, statuses and screen names on this page are read from the running code, not typed by hand — so this page changes when the product does.