Explanation

Rehearse before going live

Set everything up and read what Shuffl would send before anyone on your team hears from it.

For Workspace owners and administrators

Have your agent do thisPaste the prompt into Claude Code, Cursor or another agent. It follows this guide over MCP and asks before it changes anything others will see.Show the prompt

Help me with "Rehearse before going live" in my Shuffl workspace.

1. Read the guide: https://shuffl.ai/docs/markdown/go-live
2. Add Shuffl's MCP server: https://shuffl.ai/api/mcp
   Claude Code: claude mcp add --transport http shuffl https://shuffl.ai/api/mcp
   When the browser opens, choose my workspace and allow the access the guide needs.
3. Work through the steps in order: Go live. Do what you can over MCP and tell me which steps only I can do in the browser or in Slack.

Show me what you will change and who it affects, and wait for my yes before publishing, inviting or sending anything.

On this page

App links open your signed-in workspace. Check the selected workspace before making changes.

What rehearsal is

A new workspace starts in rehearsal. Every program runs on your real people and settings: Pulse picks its questions, Connections makes its pairs, celebrations and playbook steps come due. Nothing Shuffl starts on a schedule reaches your team until you go live.

Each message that would have gone out is held instead, with the exact Slack message or email. Owners and administrators still receive their own, so they feel what the team will get. Answers to a person’s own question or praise arrive as usual.

Read what was held and what is coming

While messages are waiting, administrators see how many on Home and above every page, with Review and send. Setup → Go live lists each held message with who it was for; open one to read it as the person would.

Coming up shows the next four weeks from today’s settings and People: Pulse sends, Connections rounds, celebrations, playbook steps and automation actions. Change a program and the list changes with it, so you can tune a schedule before anyone notices.

Choose who hears first

Right after Slack connects, Setup asks who hears from Shuffl first. Pick a few people to start a pilot, which is the suggested choice, go live for everyone, or keep rehearsing.

If messages wait a day, owners and administrators get a reminder in Slack and by email. A second one comes the day before the oldest held messages pass seven days and can no longer be sent.

Pilot with one group

To try Shuffl with a few people first, choose a pilot group on the Go live page. Everyone in that People group hears from Shuffl for real, and everyone else stays held. Any group works: the HR team, or a list of volunteers.

The pilot follows the group, so adding someone to it brings them in. The held list shows what the pilot received beside what was held, and Home counts both. Going live still releases held messages for everyone.

Go live

Open Setup → Go live and choose Go live. The confirmation says what happens next.
Held messages from the last seven days are sent now, exactly as you previewed them. Older ones are dropped, so a closed question or a stale introduction never arrives late.
From then on every scheduled message reaches its people. Back to rehearsal, on the same page, holds new messages again; it never unsends anything.