KamoCRM

Three support/chat issues — NATS relay, auto-popup, topic fallback

FixMediaService
Cambia
20 de abril de 2026 a las 5:30 UTC
Autor
Kamo
Comprometerse
337a690

1. Switch SupportNotificationService and SupportStompRelayController from JetStream to core NATS — the CHAT_MESSAGES stream only covers chat.> so JetStream publish/subscribe to support.agent.* always failed with "No matching streams" and "503 No Responders". 2. Add notifyOwnerNewTicket() that sends a NEW_TICKET notification after each public ticket is created, carrying ticketId/ticketNumber/title so the frontend can auto-open the ticket chat window. 3. Fall back to the first active org topic when the requested topicTitle ("General Inquiry") is not found, so the public live-chat session can always be created even if that exact topic name doesn't exist.

Todos los cambios

Como lo que ves enviaste?

Todo llega a su espacio de trabajo por sí solo. Comience en el plan gratuito y lea esta página de nuevo en un mes.

Empieza gratis para siempreVer Precios