Release Notes

YXAI.October26.02

Home reminders, hosted pages, and the CRM REST API — October 20 to November 2, 2026.

YXAI.October26.02

Release period: October 20 – November 2, 2026

Summary

This release adds reminders you can create from Home, a REST API for the same CRM operations as MCP, and richer follow-up on forms and Buy Pages. Profile settings give Branding and the Digital Business Card their own tabs. Web agents tease an offer before they share it, and Deploy can open the chat after a delay or a scroll. Knowledge Base web pages can be added from a pasted list.

Reminders you create yourself

Home reminders can be created on their own, with or without a lead, contact, company, or opportunity. New reminders and existing CRM follow-ups can be edited—type, notes, dates, and owner. When ownership is left automatic, a linked record goes to that record’s owner or routed assignee, and a reminder with no record stays with you. Home lists your open reminders together with due CRM follow-ups, soonest first.

MCP can list, get, create, update, and delete these reminders. Ad hoc reminders appear on Home. The CRM action email and the morning briefing continue to cover CRM follow-ups.

Branding and the Digital Business Card

Paid Profile Settings gives Branding and Digital Business Card their own tabs. Calendar Booking keeps the public booking link and booking profile, and the booking profile starts expanded. Branding adds a Profile Text color for the name, bio, and heading on the public booking page. Until a color is saved, text follows the page background so a white page stays readable. Chat colors are unchanged.

The sales area in the app switcher, breadcrumb, and mobile navigation is labeled Customers.

Tags on Find Prospects imports

Find Prospects can attach extra tags when you add companies, leads, or contacts. New records keep Prospecting and also receive the tags you chose on that add. Companies already in the CRM keep their current tags. Contacts you choose to include get the new tag merged onto the tags they already have.

Times on or after the day you asked for

When someone asks for a meeting after a date—“after November 3”, “starting Monday”, “not before the 3rd”—offered slots begin on that bound. “After” starts the next day. “On or after”, “from”, and “starting” include the named day. The reply says the times are on or after that day. The host’s maximum booking window still applies, and a start date past that window is reported as nothing open then.

Add many web pages at once

Add Web Pages, in Single Page mode, accepts a list of URLs, one per line, up to 50. Blank lines are ignored, and duplicate addresses collapse. Each address is scraped as its own page and assigned to the knowledge bases you select. Crawl Site still starts from one URL. If some addresses fail to save, the ones that succeeded stay saved and the failures remain in the box.

Offers are teased before they are shared

A web agent shares an offer when the conversation fits that offer, or the visitor asks for it, and the required fields are already collected. A fitting turn with those fields already in hand gets a short tease, then the fulfillment. A fitting turn that still needs a field asks for the highest missing field and holds the link. Details collected on an earlier visit stay personalization context until this conversation has teased the offer or the visitor has asked for it. A calendar offer that has just become eligible is still fulfilled on that turn.

Open the chat on a timer or a scroll

Deploy → Beckons adds Open the chat. The panel opens after a delay, or after the visitor scrolls, once per visit. Beckon copy, colors, and per-page triggers stay where they are. Closing the chat keeps it closed for the rest of the visit. Hero placement is left as it is, because that chat is already on the page. Installed widgets pick the setting up from live agent info.

Lead Source names the agent or form

A lead created by an agent or a form stores that agent or form’s name as Lead Source. Public chat, profile chat, agent test chat, Form Concierge, the digital business card, and a lead created while an agent books a meeting all set it. The channel—Public Chat, Form Concierge, and the rest—stays the field that drives tier playbooks. The name shows on the lead details, list, kanban card, and creation history. Manual, import, API, and inbound-email leads leave it blank. The field is set by the server.

Post-submit messages can use the answers

On a form, After submit is Post-submit chat or Post-submit redirect. Both accept the same {{field_name}} tokens as offer emails, filled from that submission.

Chat still supports markdown links, and the tokens are replaced before the Help opener is shown. A redirect must be an http or https address, and each submitted value is URL-encoded. A skipped optional field becomes blank. A token that is not a field on the form is left as written, and that leftover token keeps the visitor on the chat opener. A PDF field inserts the uploaded filename. A Buy Page that charges still continues to Stripe. Embeds, and Buy Page forms that are not checking out, follow the redirect.

REST API for CRM

Professional and Enterprise workspaces can call the same CRM operations as MCP at /api/v1, with a user OAuth access token. Reads use the crm:read scope. Writes use crm:write. Send the workspace on X-YouEx-Workspace-Id when the caller belongs to more than one workspace. Workspace Settings → Integrations shows a connection card to owners and admins when the REST API is included on the plan. The in-app record editor stays inside the product.

Edit saved email drafts from MCP

MCP can update or delete an unsent email draft stored on a lead or a contact. Subject and body can change; an empty field keeps the current value. Drafts that are already sent, scheduled, or in the middle of sending are left in place. Email list campaigns can be listed and, before sending starts, updated for tone, length, or verbatim settings. Those settings copy onto the unsent drafts.

Copyright © 2026