> For the complete documentation index, see [llms.txt](https://schedulink.io/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://schedulink.io/help-center/release-notes/august-2026.md).

# August 2026

Ask the assistant from inside the app, a Day view on the schedule, and form status at a glance.

## New

### Ask the assistant from inside the app

When you're not sure how something works, you can now ask and get an answer without leaving the page you're on.

There's a small icon at the bottom right of every page. Click it and ask in plain English. It handles how-to questions like "how do I add a sub-event" or "how do I put the school name in an email", diagnostic ones like "why didn't my email send", and definitions like "what does Ready mean on a task".

Answers come from our help center, with a link to the page they came from so you can read the detail if you want it. Everyone at your studio can use it, photographers and front desk included.

### A Day view on the scheduling page

Planning a single shoot day is easier on a page built for one day.

The scheduling page now has a Day view alongside Week. Everything on that day is sorted by start time, employee rows follow the same order, and when a job needs three photographers their rows sit together at that job's place in the sequence. Anyone with nothing on that day drops to the bottom.

Your choice of Day or Week is remembered, and Day opens on today. The 3 Day view has been removed. Scheduling

### Filter the schedule by where people are up to

You can now see at a glance who has responded to an assignment and who is on site.

The scheduling page has a new status filter with five states: pending, accepted, declined, checked in and checked out. Pending means they haven't answered yet, checked in means they're at the shoot now, checked out means they've finished.

On a shoot morning, filtering to checked in tells you who has arrived without ringing anyone. Scheduling

### Form status on the event page

You can now see how a form is doing without opening it.

Every form listed on an event carries a badge. **Waiting to send** means the send date hasn't arrived. **Sent** means it's gone out and nobody has responded. **3 of 5 submitted** means three of the five contacts have submitted the form. **Expired** means the due date passed with responses still missing.

The count is the useful part, because scanning an event now tells you who still owes you a response. Forms

### Import files can set which template a record uses

The accounts, contacts and employees import templates all have a new **Template Name** column.

Fill it in and each record is created from that template, carrying its custom fields. Leave it blank and the record is created without one, as before.

Build the template first, because the import matches on name and a name that doesn't match fails the whole file. Copy it exactly from Templates.

One limitation: the import selects the template and its fields, but doesn't fill those fields with data. You add the values afterwards. Preparing your data for import

### Salutation on the contacts import

Salutations can now come in with the rest of your contact data.

The contacts import template has a new **Salutation** column for Mr, Mrs, Dr and so on, so they land with the import rather than being added to each record afterwards. They show in display names and pull into automated emails as usual.

### Send an email to anyone at the account

Sending an email by hand from an event no longer limits you to the people already on that event.

Previously the contact list offered only contacts attached to that event, or contacts holding the role the email was aimed at, so anyone else meant editing the event first. It now lists every contact on the account.

This applies to manual sends. Automated emails still go to roles, and where they look is set in Organization. Automated emails

### Edit an employee or contact already on an event

Changing someone's role on a job no longer means removing them and adding them back.

Open the event, find the person in the Employees or Contacts section, and choose **Modify**. The dialog you used to add them opens with their details filled in, ready to change.

Both sections have also been rearranged to match Tasks, Emails and Forms, so the Add button and the row actions are where you expect them.

### Tasks can have a start time

A task that has to happen at a particular moment can now say so.

Tasks with an absolute start date can carry a time as well, set on the task itself or when you add one, using a date and time picker.

That makes them work as timed reminders, for yourself or for whoever the task is assigned to. Tasks without a specific time still start at 8am in your studio's timezone, as before. Tasks

### Record counts on every list

Your Accounts, Events, Tasks, Contacts and Employees lists now tell you how much you're looking at.

A count sits under the list reading 21 to 40 of 360. It respects the filters you've applied, so it also shows how much a filter caught, which is a quick way to spot one that's narrower than you meant. Working with lists

### Jump between records without leaving the page

Looking up a related record no longer costs you your place.

The account name in an event's header is now clickable and opens the account in the slide-in drawer. The same is true on a task, where both the event and the account are clickable. Accounts and contacts

## Fixed

### Task template steps stay in the order you left them

Editing a task template and backing out without saving was reordering the whole step list, and so was deleting a step. Anyone who did it by accident came back to a template whose sequence had to be worked out again. Steps now hold their order.

### Adding a form to an event template reaches existing jobs

Attaching a form template to an event template was only affecting jobs created afterwards. It now lands on every event using that template which isn't already complete, which is how tasks and emails already behaved.

### Group events are removed from your calendar

When an event gained a sub-event and became a group event, it stopped being schedulable but stayed on your Google Calendar, so a two-day shoot showed three entries. The parent is now removed and only the sub-events show. Sub-events and your calendar

### Event dates in emails read MM/DD/YYYY

The `event_start_date` placeholder was producing YYYY/MM/DD in sent emails. It now matches the format used everywhere else.

### Dates match across the account page

Event dates and task dates were formatted differently on the same screen. Both now read as Month Day, Year.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://schedulink.io/help-center/release-notes/august-2026.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
