Forms can now pull context from the (demographics, insurance, provider, appointment details) into read-only or editable etc etc etc etc etc etc etc

Quick test of the improved tag and ensuring API still works.

Just a test for Daniel's endpoint adjustments. 🙏

Ya get meeee

Testing state of Canny updates fetching

THIS IS A TEST MESSAGE>

Product Update: We Added Canny 🎉

We’ve officially added Canny to SKED.

This is one of those “small change, big payoff” upgrades: a cleaner way to collect feedback, a more reliable way to prioritize what matters, and a more transparent way to show progress—without feedback getting lost across texts, calls, DMs, and scattered notes.

Very cool. Very nice.

Why We Added Canny

As SKED grows, the amount of feedback we receive grows too—and the places it comes from multiply:

customers and prospects

support tickets and SMS threads

onboarding calls

internal team notes

“quick asks” in conversations that don’t make it into the roadmap

The problem isn’t lack of feedback. The problem is that feedback becomes fragmented, hard to quantify, and easy to lose.

Canny solves that by giving us a single system to:

capture feedback in a structured way

let users vote on what matters most

connect feedback directly to product decisions

keep the loop closed by showing what’s planned/in progress/shipped

What This Means for Customers

1) A Clear, Consistent Way to Request Features

Instead of “hey can you add ___?” living in a random thread, feature requests can now live in one place, with context and clarity.

Users can:

submit a new request

describe the problem they’re trying to solve

add details and examples

see if it already exists (and vote instead of duplicating)

2) Voting = Better Prioritization

When requests are visible and vote-able, we get real signal:

how many customers want it

how strongly they care

what themes are emerging across clinics/offices

That makes our prioritization less “who asked last” and more “what creates the most value across the customer base.”

3) More Transparency Around Progress

Canny makes it easier for users to see movement:

what’s under consideration

what’s planned

what’s in progress

what’s shipped

This reduces uncertainty and builds trust: people can see that feedback isn’t disappearing into a black hole.

What This Means for Our Internal Team

1) One Source of Truth for Product Feedback

Instead of managing feedback across a million surfaces, we now have a single, durable system of record.

That means:

fewer “where did we put that request?”

less duplication

cleaner handoffs across support, success, sales, and product

2) Better Roadmap Inputs

Canny helps us translate raw feedback into actionable roadmap inputs:

requests grouped by theme

vote totals for weighting

customer context attached

status updates tied to delivery

It also helps defend prioritization decisions with evidence.

3) Closing the Loop Gets Easier

One of the hardest parts of product feedback is follow-up.

Canny makes it much easier to:

update a request’s status

communicate progress in a single place

notify requesters when something ships

This is a direct upgrade to customer experience and perceived responsiveness.

Yeah, we had a great team event

Hey everyone! 👋 We’ve just fixed a few bugs for our Forms product, so If you’ve used SKED forms before and had a bad experience, consider giving it another chance ♥️

Here’s what we fixed:

PS. This is just the most recent batch out of MANY bug fixes for forms. We’re committed to making Forms rock‑solid and user‑friendly—stay tuned for more! 🚀