New Social planner

Community posting just became more powerful for developers and integration partners. You can now schedule and publish Community posts through the Social Planner Public API, including choosing which Community member the post should be published as. This makes it easier for marketplace apps and custom integrations to bring Community publishing into their own workflows.

List Community Members
Integration partners can now retrieve eligible Community members who can publish posts.

• Search by name
• Filter by location ID
• Retrieve member ID and account details

Create Community Posts
Schedule or publish Community posts via API.

• Set the author by passing a Community member ID
• Supports text, images, and media attachments
• Works with existing schedule and publish endpoints

Update and Delete Community Posts
Manage posts programmatically after they are created.

• Update content, scheduling, or author
• Delete posts when needed

Who gets this
Developers and integration partners using the Social Planner Public API. Community posting must be enabled for the location.

⚡ The Play

If you're building marketplace integrations or managing content for multiple clients, wire up the Social Planner API to post to each client's Community under the correct member identity — no manual logins, no copy-paste content calendars. Set up automated flows that pull from an approved content queue and publish at scheduled times across every account. This turns Community management into a repeatable, scalable service you can offer without lifting it manually each week.

New AI studio

Every published AI Studio site now measures itself. See page views, opt-ins and opt-in rate right inside your project, compare all your sites in Sites Analytics, and follow every lead from first visit to CRM contact. No setup or tracking code needed.

Analytics inside your project
Your project → More → Analytics → Overview
See page views, unique visitors, opt-ins and opt-in rate, with trends and the change from the previous period. Dig into top pages, time on page, traffic sources, devices, browsers, and countries — all filterable by date range.

Sites Analytics
AI Studio → Sites Analytics
Compare performance across all your published sites. Sort by any metric to find your top performers or sites that need attention.

Submissions tab
Your project → More → Analytics → Submissions
Every opt-in captured through your site shows here: name, email, the page they converted on, and the CRM contact it created. Use this to verify leads are flowing into your pipeline.

⚡ The Play

Pull up Sites Analytics weekly and rank your AI Studio landing pages by opt-in rate — your top performer is your proven template, so rebuild underperforming pages around its structure and messaging. Use the Submissions tab as your live lead-quality audit: if visitors are converting but the CRM contact record is thin on data, trace the gap back to your form fields and tighten them. If you manage multiple client sites, Sites Analytics gives you a single view to flag underperforming sites before your clients notice.

New

We've rewritten the guidance in the "View required fixes" modal so it matches how you registered your campaign.

• Guidance for your setup: The most common rejection reasons now have separate guidance for campaigns set up through the Chat Widget (Quick Setup) and through Manual Setup, since the fix is in a different place for each.
• Clearer next steps: Each reason explains in plain language what happened, then lists the specific actions to take.
• Know when it's not on you: Some rejections come from the carrier and require a resubmission rather than a fix. The modal now calls this out clearly.
• Handles all campaign types: Guidance covers both Standard Brand and Sole Prop A2P registrations.

Where to find it
Phone Numbers → Trust Center → View required fixes (next to any rejected campaign)

Who gets this
Anyone using A2P registration for SMS campaigns through Chat Widget quick setup or Manual setup.

⚡ The Play

The next time a client's A2P campaign gets rejected, open Trust Center before calling them — the updated modal will tell you exactly whether the issue is in Quick Setup or Manual Setup, so you can screenshot the right screen and resolve it without back-and-forth. If the rejection is carrier-side and requires a resubmission, use that language directly with the client so expectations are set from the start. Build a short internal SOP around these modal steps so your team can resolve A2P rejections consistently without escalating every one.

New AI studio

You can now take payments in apps built with AI Studio. Connect the products in your catalog, ask the agent to "add payments", and your app gets a secure, hosted checkout. Payments in AI Studio uses WashOS's native payments — your products, orders, payment providers and subscriptions are the ones already set up in your WashOS account, with nothing extra to configure.

Payments in a few clicks
More → Payments is a new settings tab. Turn Payments on, switch between test and live mode, and choose which catalog products your app can sell. Set each product to one fixed price, a selected set of variations, or the full catalog. Only the products and prices you allow can be shown or charged.

The agent adds the checkout for you
Ask the agent to add payments — it shows a card asking you to approve the connection, then builds a storefront and checkout into your app. The payment code is managed by the platform and is restored automatically if edited.

A hosted checkout
Card details are entered and processed in the platform's hosted checkout, never in your app's code. PayPal express checkout is supported. Coupon codes work at checkout, subscriptions work in checkout and upsells, and the checkout picks up your site's color scheme automatically. Bot protection runs on every purchase.

One-click post-purchase upsells
After a successful purchase, show buyers an offer page they can accept with one click — no re-entering card details. One-click works with saved cards from Stripe (3D Secure supported), Square, Authorize.net, NMI, Adyen, and Mercado Pago.

Product pages
Generated storefronts show product listings and detail pages from your catalog, with thumbnails and formatted descriptions.

Availability
Payments currently works only with apps built on TanStack Start. To add payments to an existing React project, go to Project Settings → Migrate to SSR to create an upgraded copy of your project while leaving the original live.

⚡ The Play

If you have an AI Studio app that qualifies leads or showcases services, bolt on a payment step so prospects can convert to buyers without leaving the experience — no redirect to a separate checkout page, no drop-off at the handoff. Set up a one-click post-purchase upsell immediately after the initial sale to offer a complementary product or higher-tier plan while purchase intent is still high. If your app is on React rather than TanStack Start, use Migrate to SSR to spin up a payments-ready copy and test it fully before switching your live version.