> ## Documentation Index
> Fetch the complete documentation index at: https://help.statisfy.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Workbench Overview
> Start your day with a curated queue of AI-prepared actions — review, edit, and send in a few clicks.
**Alpha feature.** The Workbench is currently available to a small group of users while we refine it. Features and behavior may change, and you may notice rough edges. We'd love your feedback as you try it — reach out to [Statisfy support](mailto:support@statisfy.com).
The Workbench is your daily starting point for customer success work. Statisfy reviews the accounts you own, identifies what needs your attention, and prepares ready-to-act items — drafted emails, Slack replies, meeting prep, and follow-up tasks — in a single, curated queue. You stay in control: nothing is sent until you review it and click send.
Think of it as a focused to-do list where the work comes pre-drafted. Instead of deciding *what* to do and then *doing* it, you scan a short list, make small edits, and act.
### What the Workbench does for you
A curated queue of the accounts and conversations that need attention now — not an endless notification feed.
Each item arrives with a ready-to-send draft based on your customer data, recent activity, and account context.
Review and edit every draft before it goes out. Nothing is sent automatically.
Send the email, post the Slack reply, mark the meeting prep reviewed, or create the task — without leaving the page.
### Accessing the Workbench
Click **Workbench** in the navigation at the top of your workspace, next to **Dashboard**.
A count badge next to the **Workbench** heading shows how many items are waiting for you.
Don't see the **Workbench** tab? It's currently in a limited alpha and isn't enabled for your account yet. Contact your administrator or [Statisfy support](mailto:support@statisfy.com) to request access.
### How it works
The Workbench focuses on **your book of business** — the accounts you own.
1. **Statisfy reviews your accounts** throughout the day, looking for situations that typically need a customer success touch.
2. **It prepares an action** for each one — for example, a drafted reply to an unanswered email, a prep brief for tomorrow's meeting, or a follow-up task after a call.
3. **You review the queue**, open an item, edit the draft if needed, and act on it.
4. **The item moves to your History** once you send it or dismiss it, so your Active queue always reflects what's still open.
You can also ask **Stella** to prepare something new — drafts you request in chat can land in your Workbench queue alongside the items Statisfy surfaces on its own.
### What the Workbench watches for
The Workbench looks across your accounts for the kinds of moments where a timely action makes a difference:
| Situation | What it helps you do |
| ----------------------------- | ----------------------------------------------------------- |
| **Renewal approaching** | Get ahead of an upcoming renewal with a plan or outreach |
| **Health declining** | Respond when an account's health score drops |
| **Usage dropping** | Reach out when product usage falls off |
| **Account gone quiet** | Re-engage accounts with no recent contact |
| **New stakeholder** | Introduce yourself when a new contact appears at an account |
| **Unanswered customer email** | Reply to a customer message that's still waiting on you |
| **Unanswered Slack message** | Respond to a customer message in a shared Slack channel |
| **Upcoming meeting** | Walk in prepared with a tailored prep brief |
| **Recent meeting** | Follow up with an email and next steps after a call |
When a single account shows several related signals at once — say, a health drop and a usage drop — the Workbench can combine them into one action with shared reasoning, rather than several separate items.
### Action types
Each item is one of a few types, and each opens the right tools for the job:
| Type | What you do | How it's sent |
| ----------------- | --------------------------------- | ----------------------------------------------------------- |
| **Email** | Review and edit a drafted email | Sent from your connected Gmail |
| **Slack** | Review and edit a drafted reply | Posted to the customer Slack conversation that triggered it |
| **Meeting** | Review a pre-meeting prep brief | Marked as reviewed (nothing is sent) |
| **Task / Ticket** | Review a suggested follow-up task | Created in Statisfy |
### Working through your queue
The queue has two modes, switched with the **Active** and **History** buttons at the top:
* **Active** — items still waiting for your action.
* **History** — items you've already sent or dismissed.
**Filtering the Active queue.** Use the type filter to narrow the list: **All types**, **Emails**, **Slack**, **Meetings**, **Tickets**, or **Tasks**.
**Reading a card.** Each item shows a title, a short subtitle (for example, a meeting time and attendees), an icon for its type, and how long ago it was prepared. The most recently prepared items appear at the top. Items that share the same source — for example, several drafts tied to the same meeting or email thread — are grouped together.
**When you're caught up.** An empty Active queue shows **"You're all caught up!"** — there are no pending actions, and you can ask Stella to prepare something new.
Start your day on the Workbench. Work down the list, then filter to a single type (like **Emails**) to batch similar work.
### Reviewing and sending an action
Click any item to open it on the right. You can edit before you act — changes save as you type, so there's no separate save step.
Review the recipients (**To**, **CC**, and **BCC**), the subject, and the body. Adjust recipients or wording as needed — start typing a name to search for a recipient. When the draft comes from an email template, any **CC** and **BCC** recipients defined on that template are carried over automatically.
A note marked **"For your eyes only — not included in sent email"** may appear above the draft. This is context for you and is never sent to the customer.
When the draft is ready, click **Send via Gmail**. After it sends, the item shows **"Sent via Gmail"** and moves to your History.
Sending email requires a connected Gmail account. If you see **"Connect Gmail to send"**, connect Gmail first. See [Email & Calendar Integration](/integrations/email_and_calendar_integration).
The draft shows which channel it will post to (**"Will post to #channel"**). Edit the **Message**, then click **Send to Slack**. The reply posts to the conversation that triggered the action, and the item shows **"Posted to Slack"** once sent.
Slack formatting is posted as Slack-style text (mrkdwn), so keep it plain — no HTML or email formatting.
A meeting item opens a prep brief — account context, recent activity, talking points, and suggested action items. Review and edit it, then click **Mark Reviewed**. Nothing is sent; this simply confirms you've reviewed the brief and clears it from your queue.
A task item shows the suggested follow-up details for you to review. Adjust the fields if needed, then click **Create task** to add it to Statisfy. Resolve any flagged errors before creating.
### See the context behind an action
Every action is backed by the conversation or event that prompted it — the email thread, the Slack conversation, or the meeting. Open the **context panel** to review that source material without leaving the action.
Click the context icon at the top of the action (it's labeled with the customer's name, or **View context**) to open the panel on the right. It shows:
* A pinned **customer header** — name, health, and a link to the full account.
* A **Recent Activity** timeline for the account.
* The source for that action type:
* **Email** — the **Original Thread** with its message count. Click **Read full** to read the entire thread.
* **Slack** — the **#channel** conversation. Click **Read full** to read the whole thread.
* **Meeting** — the **Meeting** details and **Attendees**, plus **Key Takeaways** and **Outcomes** for past meetings. Click **View full** for the complete summary.
### Refine a draft with Stella
Each action has its own Stella chat that already knows which item you're working on — use it to refine the draft, ask for more detail, or pull in extra context, all in plain English.
1. Click **Ask Stella** on the action. The Stella panel opens with the heading **"Asking about \[action title]"**.
2. Tell Stella what you want — for example, *"make this more concise,"* *"mention the renewal date,"* or *"pull in the latest support tickets."* Stella can rephrase, edit, or regenerate the draft and pull more context for the artifact.
3. When Stella proposes a change, review it before it's applied. Once you accept, you'll see **"Stella revision applied."** Finish reviewing a proposed change before continuing the chat.
On items you've already sent or dismissed, the chat is **Read-only** — you can ask questions about the action, but Stella won't make edits.
### Version history
As you and Stella make changes, the Workbench keeps a version history for your current session, so you can step back to an earlier draft.
* Open it from the version pill (for example, **v3**) on the action to see the **Version history**.
* Each entry is labeled by where it came from — **Original**, **You edited**, **Stella applied**, or **Restored** — along with when it was created.
* Click **Restore this version** to load an earlier draft back into the editor. It then auto-saves as your current draft.
Version history is kept for your **current session only** and is cleared when you reload the page. For fine-grained undo while typing, use the editor toolbar.
### Dismissing an action
If an item isn't relevant, click **Dismiss**, then confirm. Dismissed items leave your Active queue and are kept in History so you have a record.
Dismissing an item helps Statisfy learn what's useful to you. If you regularly dismiss a certain kind of suggestion, the Workbench can prioritize differently over time.
### Reviewing your History
Switch to **History** to see everything you've already handled. You can filter by:
* **Date range** — **Last 7 Days**, **Last 30 Days**, or a **Custom Range**
* **Type** — the same type filters as the Active queue
* **State** — **All states**, **Executed**, or **Dismissed**
Completed items carry a status that reflects what happened — **Sent** (email), **Posted** (Slack), **Reviewed** (meeting prep), **Created** (task), or **Dismissed**.
### Requirements
| To act on… | You need… |
| -------------------- | -------------------------------------------------------------------------------------------------------- |
| Email actions | A connected Gmail account ([Email & Calendar Integration](/integrations/email_and_calendar_integration)) |
| Slack actions | The [Slack integration](/integrations/slack) connected to your customer channels |
| Accurate suggestions | Synced account, activity, and health data so the Workbench has full context |
### Tips for getting the most from the Workbench
Edit freely. The drafts are a strong starting point, but a one-line personal touch — referencing something specific the customer said — makes outreach land better.
* Check the Workbench at the start of your day, the way you'd check your inbox.
* Open the context panel before sending, so your reply matches what was actually said.
* Use the action's Stella chat to refine a draft instead of rewriting it from scratch.
* Dismiss what isn't useful instead of ignoring it, so your queue stays a true to-do list.
* Use the type filters to batch similar work (clear all emails, then all meeting prep).
### Third-party tools (MCP)
The Workbench can use connected [third-party MCP tools](/integrations/third_party_mcp_servers) (for example, Jira) when it prepares actions. An admin enables them under **Settings → Workbench Agent**:
* Turn on **Enable third-party MCP tools for the workbench**.
* Select which tools the workbench may use from each connected server.
* Optionally add an **injected prompt** that steers when and how it uses them (for example, *"File a Jira ticket when a customer reports a hardware issue"*).
Tools marked **approval-required** on the Integrations page pause for review before they run — the review shows up as a tool-approval action in your queue, rather than executing automatically.
### Previewing the Workbench for a user
Admins can see what the Workbench *would* prepare for a specific person and account — a safe dry run that reads their data but **creates, sends, and executes nothing**. It's useful for checking how the Workbench behaves for a teammate before they rely on it.
Open **Settings → Workbench Preview**. On the **Preview workbench** panel:
1. **User** — choose the person to run as. The preview uses that user's book of business and permissions.
2. **Account** — pick the account to focus on.
3. **Activity (optional)** — leave it on **Whole account (or pick one activity)** to scan the whole account, or select a single activity (like one email thread) to scope the preview to just that.
4. Click **Run preview**.
The preview thinks through the account the same way the live Workbench does and shows the actions it *would* draft — emails, Slack replies, tasks, and meeting prep — along with its reasoning. Nothing is added to anyone's queue, and no email, message, or task is created or sent.
Workbench Preview is available to **admins** and is completely read-only, so you can run it as often as you like without affecting the user, their queue, or your customers.
### Related
Ask Stella to prepare drafts and answer questions about your customers.
Review and approve automated workflow actions before they execute.
Track upcoming and overdue renewals across your portfolio.
Monitor health, renewals, and key metrics at a glance.