For client-facing teams

Know what changed. In words you can repeat.

Every release, Sabí writes a plain version for your team and one for customers. No developer translation needed.

Your week, before and after

Before

You hear about changes from customers.

You're not sure which page is still true.

A developer explained it twice. You still can't explain it to a client.

Every answer means another message to product.

After

A plain "what changed" for every release.

One version for your team, one for customers.

Every page shows where it came from, so you know it's current.

Answers you can find without asking.

Know what changed, in plain words.

A short summary of each release, written for people who talk to customers.

SabíWhat changed · for your team

Release 8.3

NewPause a subscription
Tell customers: they can pause for up to 3 months. Billing stops, nothing is deleted.
ChangedCancel plan moved under Manage plan.
No actionBehind-the-scenes cleanup.

Words you can sell with.

A plain version of each new feature, ready for client calls and stakeholder updates.

SabíRelease 8.3

The change: pause a subscription.

Take a break without cancelling

Go to Billing, click Manage plan, then Pause. Pick 1 to 3 months. Billing stops until then.

Checked in the product

Answer with the source in hand.

Reply with the page and the change behind it, so you can say what shipped and when.

SabíCustomer chat
Will I lose my data if I pause?
No. Everything stays. Billing just stops until the pause ends.Pause your plan · Updated today
Backed by change #884

You stay in control.

You check customer pages first. Team pages can go straight out, if you want.

See what changed, and what Sabí left alone.

In beta: Sabí tries the steps in a test copy of your product before you publish.

SabíSettings · Publishing rules

Who approves what

CustomersYour teamDevelopers
You check firstPublishes on its own
Your productHelp centre · Pause your plan
BeforeClick Cancel plan.No longer true
After · todayClick Manage plan, then Pause.Checked in the product
Joost, from the support team, smiling

A typical week

  1. Tuesday, 3 pm

    Pausing a subscription ships.

  2. Tuesday, 5 pm

    Joost's team reads what changed, and what to tell customers.

  3. Wednesday, 10 am

    A customer wants a break instead of cancelling.

Joost already knows the answer.

Make the case to your manager

The problem

Every release changes the answers, and your team finds out from customers.

What a pilot needs

One setup session, and someone to approve customer pages for the first weeks.

What we measure

Questions your team sends to product or engineering each week.

Send this page to your manager →

Questions

Can customers see this?

Only what you've approved. Team pages stay internal.

Does it update our help centre?

If your help centre lives in Notion, yes. Confluence and one more help centre app are coming soon.

How do I know a page is current?

Every page shows the code change it came from.

Are the steps in customer pages checked?

In beta, yes: Sabí tries the steps in a test copy of your product and attaches a screenshot of each.

See it on your own product.

Book a demoTry it on your code