17 SEPTEMBER 2026 · SCHEDULING
A clearer path from availability to a booking
A scheduling link is only useful when your availability can be saved and a visitor can complete the booking. The 17 September change addresses failures when saving availability, a dead end in the public booking flow and how the selected day is interpreted in the scheduling page's timezone. These are connected steps in the same experience: the host sets the available time, the visitor chooses a slot and the booking flow carries that choice forward.
When preparing a new scheduling link, save your availability and open the booking page as a visitor. Check that the intended slots appear in the right timezone and that the booking confirmation matches the selected day. This is especially useful for agencies booking client meetings across timezones.
- Availability saving and validation updated.
- Public booking flow corrected.
- Slot-day handling aligned with the scheduling page's timezone.
Explore scheduling
Review the scheduling workflow and the role it can play in your client handoff.
Explore this workflow ↗10 SEPTEMBER 2026 · CRM
Turn a won deal into a project
The 10 September update fixes a status mismatch that prevented some deal-to-project conversions from completing. A won engagement can move into the project workflow with a valid starting status, ready for the delivery team to build out the work.
After conversion, confirm the client and commercial context, then add the delivery stages, owners and dates. Keep the approved scope and important sales notes close to the project so the team can start without reconstructing the agreement from a separate conversation.
- Corrected the project status created during deal conversion.
- Added checks to catch this status mismatch.
- Kept the project setup ready for delivery planning.
See the CRM-to-delivery workflow
Keep commercial context close to the project that follows.
Explore this workflow ↗6 SEPTEMBER 2026 · PROPOSALS
Choose the client and confirm the recipient in context
A proposal often needs a little coordination before it leaves the workspace: which client it belongs to, whether that client already exists and who should receive it. The 6 September proposal work adds an inline client selector, a quick-create route for a client and a sending dialog with an explicit recipient. That keeps these decisions next to the proposal instead of leaving the sender to infer them.
Sending requires a recipient, with a clear message when one is missing. The proposal also checks that its linked client and deal belong to the workspace. Select the client, review the scope and amount, then confirm the intended email address in the sending dialog. This keeps the decision clear when a client has several stakeholders or more than one engagement underway.
- Inline selection and quick creation for proposal clients.
- A recipient-focused sending dialog.
- Validation for a missing recipient and checks around linked client and deal ownership.
Explore proposals and signatures
Connect the proposed scope, recipient and agreement before delivery begins.
Explore this workflow ↗6 SEPTEMBER 2026 · FILE HANDLING
Keep proposal images and protected files connected
The 6 September work adds an image-upload widget for proposals and improves access to protected file links. Proposal authors can add an image alongside the content it supports, while updated file handling keeps stored assets connected to the pages that display them.
Preview the proposal after adding the image and check how it appears in the recipient's view. Look at the crop, readable details and surrounding content before sending. If an image or attachment does not load, contact support with the affected page, approximate time and error message. Keep private file links and access tokens out of a public message.
Review client-facing access
Use the portal guide to review the client's view and the information you intend to share.
Explore this workflow ↗06 / PRODUCT DEVELOPMENT NOTES
Tell us what would improve your working day
Product feedback is most useful when it starts with the work you are trying to finish. Describe the task, how you handle it today and where the process gets difficult. For example, an account lead preparing several proposals may need a clearer way to choose the recipient, while a project owner may need more context after winning a deal.
If a workflow behaves differently from the update described here, contact support with the workspace, steps taken and result. Include the approximate time and timezone, plus a screenshot or error message when it helps. The feature guides explain the surrounding workflow, while support can help with availability and behavior in your own workspace.
Get help with a workflow
Find documentation or contact the team with the observed behavior.
Explore this workflow ↗Report an availability issue
Find the details to include when something stops working.
Explore this workflow ↗THE PRACTICAL DETAILS
Questions, answered.
When will I see an update in my workspace?
Entry dates record development work. Contact support@flowboardhq.com to check availability in your workspace, especially if a change affects an upcoming client handoff or a workflow you rely on.
Does the changelog list every product change?
The changelog highlights improvements to common agency workflows. Follow the linked feature guides for setup instructions and use the contact page if you have a question about another part of the product.
How do I report a problem related to an entry?
Email support@flowboardhq.com with the workflow, workspace context, steps taken, expected result and observed result. Include the approximate time and timezone. Keep credentials and private client material out of the initial report.
Where can I suggest the next improvement?
Send feedback or a feature request to support@flowboardhq.com. Describe the work you are trying to complete, how you handle it today and the point that needs improvement. Include an example of the next action you would like to make easier.