What We Shipped This Week: September 10 – 17, 2026

Your bank, your store, and your second Outlook inbox all join Sabi this week: 19 updates shipped and 99 customer-reported issues resolved. Here's everything, in plain English.

---

📊 The Week in Numbers

• 19 updates shipped to production
• 99 support tickets resolved
• Bank connections were the most-requested missing app on the board — 6 tickets closed by one launch

---

🏦 Connect Your Bank

• Your bank is now in Sabi — the Plaid tile had said "coming soon" for months. This week it went live: link any bank through Plaid's secure sign-in, read-only, and ask Sabi about balances and recent transactions. Link more than one bank and she'll merge them into a single picture. Venmo and Robinhood work through it too. This closed 6 tickets from customers who'd been asking.
• Sabi knows which bank you linked — when you connect a second bank she says so by name ("I see you connected Robinhood") instead of a generic "you connected Plaid."

🛍️ Shopify, Done Properly

• A guided Shopify connection — Shopify stopped issuing the kind of access token our old form asked for, so 7 of the last 9 connection attempts failed on a form field. The new Sabi-built dialog walks you through creating an app in your Shopify dashboard, checks the store answers before saving anything, and tells you exactly which field to fix if it doesn't. New stores can connect for the first time.
• Step-by-step guide — the full walkthrough with screenshots is at meetsabi.com/posts/how-to-connect-shopify, and the dialog links straight to it.

✉️ Email & Documents

• Two Outlook accounts, finally — multi-account Outlook was built a month ago but the switch was never flipped. Five customers who could only see one inbox can now add a second (work + personal) with the "+ Add account" button.
• Custom-domain mailboxes are live — last week we said this was rolling out. It's on: connect any custom or self-hosted mailbox from the Connections page, not just Gmail, iCloud, and Yahoo.
• Reconnecting Gmail actually fixes it — reconnecting Gmail, Google Calendar, Docs, Sheets, or Drive used to add a fresh connection next to the broken one, and Sabi kept reaching for the broken one. Now the dead connection is retired and the new one takes over. We also repaired the accounts this had already affected (8 customers).
• Big BCC lists send first time — sending or drafting to 35+ recipients was failing with an encoding error and retrying. Fixed at the root; Sabi no longer hand-assembles the message.
• Google Docs can't be wiped blank — one customer's documents were being emptied when Sabi cleared a document and ran out of room before writing the replacement. A whole-document clear with nothing to put back is now refused outright.

🎥 Meetings

• Full Zoom transcripts, saved for good — a two-hour meeting was being silently cut short, so the recap missed most of it. Sabi now downloads the full transcript, saves it to your Library, and answers from there next time you ask. Recurring meetings get one document per occurrence.

🎁 Referrals

• "Sabi's Most Generous" — the Referrals page now has a weekly leaderboard next to your rewards: the top five members whose friends activated Sabi Pro in the last 7 days, with gold, silver, and bronze medals and a "You" marker on your own row. First name and last initial only.

🧠 A Smarter, More Honest Assistant

• Pricing questions get a real answer — ask about monthly vs. Founding Member and Sabi now explains the difference (price lock vs. monthly that may rise) alongside the billing link, instead of just "use the link I sent."
• Morning check-ins don't repeat stale money news — a remembered invoice is no longer reported as "still unpaid" once the memory is out of date.

🛡️ Reliability Behind the Scenes

• iMessage outage, fixed and hardened — a configuration slip during our production move meant Sabi stopped receiving texts for a few hours last week. It was corrected quickly, and the check that failed was rebuilt so a future settings change can't trip it again.
• Fewer silent misfires — a recalled memory ending in an emoji, a research task that also needed a live web search, or a momentary network blip during memory recall could each quietly kill a reply. All three now recover on their own.

---

Questions or something not working the way you'd expect? Just tell Sabi — every piece of feedback lands on our board and gets looked at quickly.