August 4th, 2026
CX Platform
The answer to most client questions is in an email thread — usually one from four weeks ago, behind a thousand other messages. Email 2.0 connects your mailbox to Stax.ai so the conversation lives with the client it's about: thread history sits next to the plan, the tasks, and the documents; you write knowing what's still outstanding; and those conversations feed Client Pulse, so how an account is trending reflects what's being said, not just what's been checked off.
It's all on a new foundation — near-real-time sync for Gmail and Outlook, threads that hold together, and the inbox views you work out of, with everything you already use carried forward. On top of that, CX adds an assistant that drafts with your client context in hand, folders and labels that mirror your mailbox, and a bulk email system that sends from your own domain.
Update On Your Time: The next time your mailbox disconnects, reconnecting will take you through our new email connection flow. Or to connect right away, open your settings, disconnect your mailbox, and reconnect it.
The new email assistant does more than autocomplete. It writes and adjusts your message for you — drafts a reply from scratch, tightens what you've written, changes the tone — and it answers questions using the context Stax.ai already holds about the client in front of you.
Ask it about a client, a thread, or what's still open on a plan:
Write and revise — draft a reply, rework a paragraph, adjust the tone of what you've written
Ask about a client — pull what Stax.ai knows about the company, plan, and contacts without leaving the message
Catch up on a thread — get the through-line of a long conversation before you answer
Check outstanding work — see which tasks are still open for that client so your reply reflects where things actually stand
You'll find the assistant in the compose window and alongside any open thread.
You can now create and manage folders and labels directly in Stax.ai, matching however your mailbox already works — labels if you're on Gmail, folders if you're on Outlook. Organize client mail the way you organize everything else, and the structure stays consistent between Stax.ai and your mailbox.
Bulk email has been rebuilt around your own sending domain. You can configure the mail delivery records for a domain you own, so campaigns send as you rather than on a shared sender — which protects your sender reputation and gets more of your mail into inboxes.
The new system adds:
Deliverability reporting — see how a campaign actually performed on delivery, not just that it was sent
Multi-domain support — configure more than one sending domain and choose which one a campaign goes out from
Open tracking — see who opened a bulk campaign
You can also send bulk email from a saved template.
Domain setup lives in Settings and will appear in your account within 48 hours. If you choose not to connect your domain, you can still send bulk emails through your connected inbox, however certain deliverability and open insights reporting may be limited.
Not every message in a connected mailbox belongs to the whole organization. You can now keep email to yourself two ways:
A blanket privacy rule — applies to everything synced from your mailbox
Per message — use Mark as private on any individual email
Private emails are excluded from organizational visibility, so the rest of your team won't see them in shared views.
The Verify Census File task in the client portal now supports both ways a plan sponsor actually works through a census.
If a sponsor downloads the census and uploads a corrected version, Approve moves them straight through. If they review it and have no changes to make, Approve asks them to confirm they're approving the census as-is, then completes the task.
Improvements
Email — You can disconnect a mailbox from Settings at any time; new mail stops syncing and everything already synced stays accessible.
Email — The compose toolbar is cleaner: AI tools stay disabled with a tooltip until you select text, inserting a template no longer brings stray formatting with it, and the inline editor dropped its redundant toolbar.
Email — Refreshed icons throughout the inbox.
Government Filings — Prior-year data for the 2024 Form 5500 is now in place, so prior-year figures carry forward on the filings you're preparing.
Fixes
Automations — The Create or Update Contact automation now ties a new contact to the correct plan and deal.
Automations — Create or Update Contact now creates a new contact when the email address is new instead of overwriting an existing record, and maps name, phone, role type, and internal-vs-external correctly.
Automations — Fixed a failure where launching a project couldn't create its deal because the funnel and stage couldn't be resolved.
Automations — Document auto-populate no longer fails on .docx templates, so the populated file is produced and can be converted to PDF.
Client Portals — Corrected an invite issue where a new portal user couldn't log in and a password reset reported the account didn't exist.
Client Portals — The outstanding-task reminder email option now appears only when there is actually a client task waiting in the portal.
Email — Bulk sends no longer stall when a recipient role resolves to no one; the message still goes out to everyone else on the list.
Email — Reminder emails no longer fail silently; sends land in your sent box as expected.
Email — Fixed thread grouping so replies stay attached to the original conversation.
Government Filings — Launching a filing no longer errors out when the client record can't be resolved.
Government Filings — The amendment toggle on filing launch now saves the setting you choose.
Government Filings — Corrected a case where a 5500 submission reported success while the filing stayed in Drafting; filing status now advances to Submitted as expected.
Platform — Refreshing a page no longer returns an intermittent 404.
Reporting — Milestone reports now list every plan status as a selectable option, including Terminating and Terminated.
To-Do Queues — Queues no longer break when the project lead sits in a different queue than the task assignees.