Compra, reunión agendada o un evento con nombre, escrito una vez la primera vez que el lead entra a esa fase.
Resultados en una fase. Una fase del Process Board puede registrar un resultado la primera vez que un lead entra: compra, reunión agendada o un evento personalizado con nombre, con un valor y una moneda opcionales. ioZen escribe ese evento propio una sola vez. Mover el mismo lead a esa fase otra vez no escribe otro. Esto no es un retorno de pauta guardado.
Importar a una campaña. Una campaña nueva de WhatsApp puede importar contactos, etiquetarlos y guardar un segmento listo por teléfono como audiencia. Las campañas apuntan a un segmento guardado, a filtros o a una búsqueda simple. Business y Enterprise.
Click-to-WhatsApp, en beta. Los hilos que empiezan en un anuncio de Meta Click-to-WhatsApp conservan la referencia y el ID de clic para que el analytics de fuente pueda agruparlos. El WhatsApp orgánico sigue sin atribución. Esto sigue en beta hasta completar una revisión en vivo de Test Events.
También. Cada número de WhatsApp puede publicar un enlace rastreado. Las conexiones de Google Ads ya configuradas mandan conversiones por Data Manager. Los Intake Bots en borrador y publicados cuentan para el límite del plan. Los archivados no, y no se pueden restaurar si ya estás en el tope.
A Process Board phase can record one outcome the first time a case enters it: purchase, meeting scheduled, or a named custom event, with optional value and currency. ioZen writes one first-party lifecycle event. Moving the same case into that phase again does not write another. Network sends follow configured platform credentials and do not depend on Intake Bot On Payment or On Meeting Booked flags. If no submission is found, only the first-party event is recorded. Test cards send to Meta Test Events only when a test sink is ready.
New campaign can open the Contact Center import wizard. The imported rows are tagged and saved as a phone-ready segment, then selected as the campaign audience. Campaigns target contacts only: saved segment, filters, or a simple search.
Google Ads conversion delivery now uses Data Manager for configured connections. ioZen sends one click ID plus available hashed customer data, validates setup without ingesting a test conversion, and keeps eligible legacy Ads connections available without duplicate Google delivery.
maxIntakeBots counts draft and published bots. Archived bots stay free and cannot be restored at cap. Duplicate and FlowApp copy respect the same limit as create.
WhatsApp conversations that start from a Meta Click-to-WhatsApp ad now keep the referral and click ID. The Intake Bot submission is stamped so source analytics can group those cases. Organic WhatsApp stays unattributed. Optionally, each number can send server-side Meta business-messaging conversions (LeadSubmitted, Purchase) to the WABA-linked dataset using the raw click ID and an optional Test Events code. Meta attributes those events for 7 days from the click. This is beta until a live Test Events check is completed.
Each WhatsApp number can now publish first-party /l/[slug] links. A click stores UTMs and click IDs, then opens WhatsApp with a short reference marker that is removed before the conversation is stored. A surviving token is a deterministic match and can reach ad networks. A 10-minute unique fallback is a first-party estimate only. Click-to-WhatsApp referrals still take precedence. Phone is not a LinkedIn match key; capture email in the Intake Bot or keep li_fat_id.
