Ably pub/sub messaging pushes live data table updates row updated, row deleted, bulk update to every open tab the moment a change happens. Socket.io handles server push notifications so alerts surface the instant they matter. No refresh button. No polling. No stale data ever. An email marketing platform where the data on the screen is always the data in the database.
A teammate updates a lead, a row gets deleted, a bulk action lands a thousand records and every other open tab in your business sees the change before the rep who made it can even reach for the mouse. The whole pipeline runs on Ably for data sync and Socket.io for server push, so the data on every screen is always the live state of the database.
Change Origin
A teammate edits a lead status in the dashboard. A rep deletes a stale record on mobile. A bulk operation reassigns three hundred leads to a new owner. An API integration imports a fresh batch from a webhook. Every one of these write actions enters the same pipeline, regardless of where the change originated or who triggered it.
Ably Pub/Sub
The moment the change commits, the backend publishes an event to the right Ably channel datatable:leads, datatable:contacts, datatable:deals with a payload describing what changed. The events are typed: row_updated for inline edits, row_deleted for removals, bulk_update for multi record operations. Every client subscribed to that channel is about to find out, in real time.
Cross Tab Delivery
Every browser tab subscribed to the channel across every teammate, every device, every session receives the event the moment it ships. A manager watching the lead board on a desktop, a rep checking the same record on a laptop, a sales operations specialist running a cross pipeline report on a second monitor all three see the update at the same time, without anyone touching a refresh button.
Instant Render
The data table updates the row in place. Deleted rows disappear. Bulk operations land across the visible page with a single render pass. Socket.io push notifications surface the moment they matter a high value lead converted, an SLA breach, a manager assigned a deal. The whole interface keeps the state on the screen aligned with the state in the database, always, without anyone asking for it.
Once a team works in an environment where the screen always reflects the database in real time where two reps never accidentally touch the same lead, where the manager never asks is this number current, where the refresh button might as well be removed from the keyboard there's no version of the old way that still feels acceptable.
TThe classic sales team disaster two reps spotting the same lead, both reaching out, both unaware the other is already in the conversation disappears the moment every screen reflects the live state of the database. A status change shows up on every teammate's view in real time, so the rep who would have made the duplicate call sees the update before they pick up the phone.
The pipeline view stops being a snapshot from when the page loaded and starts being a live feed of every deal in motion. A card moves on a rep's screen, the manager sees the same move on their screen, the cross pipeline rollup updates the forecast all in the same second. The leadership meeting opens to the current reality of the business, not a screenshot from this morning.
The trust tax of working in a tool where data might be stale the second guessing, the manual refresh, the email asking somebody to confirm disappears entirely. The number on the screen is always the number in the database. Conversations that used to start with is this current now start with what should we do about it, which is the only kind of conversation that actually moves the business forward.
A bulk reassignment of three hundred leads to a new rep used to mean every teammate's view was wrong until they refreshed. Now the change lands on every open tab at the same time. The new owner sees their accounts populate live, the old owner sees their list shrink, the manager sees the rebalance happen on the dashboard no refresh, no confusion, no inconsistent state across the team.
A high value lead converts and the assigned rep gets the toast immediately. An SLA timer breaches and the manager sees the alert on their screen, not in tomorrow's email digest. Socket.io push delivers the message to the active session the instant the event fires, so the team acts on what just happened, not on what happened sometime today.
Anyone who has worked in a CRM long enough has trained themselves to refresh the page every few minutes, just in case. That reflex disappears. The page stays open, the data keeps flowing, and the cognitive overhead of remembering to manually check for updates gets given back to the actual work. It is the kind of small change that turns out to matter every hour of every day.
TThe classic sales team disaster two reps spotting the same lead, both reaching out, both unaware the other is already in the conversation disappears the moment every screen reflects the live state of the database. A status change shows up on every teammate's view in real time, so the rep who would have made the duplicate call sees the update before they pick up the phone.
The pipeline view stops being a snapshot from when the page loaded and starts being a live feed of every deal in motion. A card moves on a rep's screen, the manager sees the same move on their screen, the cross pipeline rollup updates the forecast all in the same second. The leadership meeting opens to the current reality of the business, not a screenshot from this morning.
The trust tax of working in a tool where data might be stale the second guessing, the manual refresh, the email asking somebody to confirm disappears entirely. The number on the screen is always the number in the database. Conversations that used to start with is this current now start with what should we do about it, which is the only kind of conversation that actually moves the business forward.
A bulk reassignment of three hundred leads to a new rep used to mean every teammate's view was wrong until they refreshed. Now the change lands on every open tab at the same time. The new owner sees their accounts populate live, the old owner sees their list shrink, the manager sees the rebalance happen on the dashboard no refresh, no confusion, no inconsistent state across the team.
A high value lead converts and the assigned rep gets the toast immediately. An SLA timer breaches and the manager sees the alert on their screen, not in tomorrow's email digest. Socket.io push delivers the message to the active session the instant the event fires, so the team acts on what just happened, not on what happened sometime today.
Anyone who has worked in a CRM long enough has trained themselves to refresh the page every few minutes, just in case. That reflex disappears. The page stays open, the data keeps flowing, and the cognitive overhead of remembering to manually check for updates gets given back to the actual work. It is the kind of small change that turns out to matter every hour of every day.
Update. Publish. Broadcast. Receive. Render. Notify. Synced. Every screen, every team, every time without anyone touching the reload button.
6800+
STeams working from live data,
not refresh buttons
Sales representatives, sales managers, customer success teams, operations specialists, and engineering leaders use EVOX real time updates as the foundation for collaborative work. The data table is the canvas. The Ably channel is the wire. The Socket.io push is the alert. Every team a small sales unit running concurrent outreach or a larger organisation with hundreds of users on the same workspace gets the same guarantee: what you see on screen is what is actually in the database, right now, with no stale data anywhere.
Pub/Sub
Push Notifications
Perceived Lag
Tabs in Sync
Ably pub/sub messaging publishes row_updated, row_deleted, and bulk_update events to channels every connected client subscribes to. Tables, dashboards, pipelines, and reports all update in place the moment a change commits to the database. The data on the screen and the data in the system are the same number, always.
A complete real time backbone built into the same email marketing software your team already uses. Ably pub/sub for data sync, Socket.io for push notifications, typed row events for granular updates, and cross tab synchronisation that keeps every screen aligned with the database. No refresh, no polling, no stale data anywhere on the platform.
Every data table on the platform leads, contacts, deals, campaigns, reports receives live updates the moment a change commits. Typed events for row updated, row deleted, and bulk update mean the UI knows exactly what changed and can render the smallest possible diff, with no full table reloads and no flicker.
Ably runs the messaging backbone for all live data sync. Channels are scoped per data type (datatable:leads, datatable:contacts) and per workspace, so every client gets exactly the events it cares about and nothing else. The infrastructure scales to thousands of concurrent connections without breaking a sweat.
Socket.io handles server push for events that need a human in the loop high value lead alerts, SLA breaches, deal closed won, manager mentions, real time activity feeds. Toasts and badges fire the moment the event ships, surfaced to the active session of the user who needs to see them.
Every browser tab subscribed to the workspace receives the same events at the same time. A rep with the lead list open in one tab, a deal detail in another, and a dashboard on a second monitor sees consistent state across all three windows, even when the update originated from a different teammate or a different device.
The refresh button stops being part of the workflow. Pages stay open, data keeps flowing, and the cognitive overhead of manually checking for updates disappears entirely. Long running sessions on a dashboard or a Kanban board stay accurate for hours without anyone reloading anything.
The state on every screen is always the live state of the database. Connection drops are detected and recovered, missed events are replayed on reconnect, and any divergence between client and server is resolved automatically. The number on the screen and the number in the system are always the same number.
Every data table on the platform leads, contacts, deals, campaigns, reports receives live updates the moment a change commits. Typed events for row updated, row deleted, and bulk update mean the UI knows exactly what changed and can render the smallest possible diff, with no full table reloads and no flicker.
Ably runs the messaging backbone for all live data sync. Channels are scoped per data type (datatable:leads, datatable:contacts) and per workspace, so every client gets exactly the events it cares about and nothing else. The infrastructure scales to thousands of concurrent connections without breaking a sweat.
Socket.io handles server push for events that need a human in the loop high value lead alerts, SLA breaches, deal closed won, manager mentions, real time activity feeds. Toasts and badges fire the moment the event ships, surfaced to the active session of the user who needs to see them.
Every browser tab subscribed to the workspace receives the same events at the same time. A rep with the lead list open in one tab, a deal detail in another, and a dashboard on a second monitor sees consistent state across all three windows, even when the update originated from a different teammate or a different device.
The refresh button stops being part of the workflow. Pages stay open, data keeps flowing, and the cognitive overhead of manually checking for updates disappears entirely. Long running sessions on a dashboard or a Kanban board stay accurate for hours without anyone reloading anything.
The state on every screen is always the live state of the database. Connection drops are detected and recovered, missed events are replayed on reconnect, and any divergence between client and server is resolved automatically. The number on the screen and the number in the system are always the same number.
Common questions about how EVOX real time updates work under the hood, what Ably and Socket.io each handle, and what users actually see on screen as the data changes.
The two systems handle different jobs. Ably runs the pub/sub backbone for live data table updates row updated, row deleted, bulk update events on channels every client subscribes to. Socket.io handles server push notifications for events that need a human in the loop toast alerts, live badge counts, mentions, and SLA breaches. Together they give the platform two complementary layers: live state for the tables, and live alerts for the moments that matter.
Ably for data. Socket.io for alerts. Every screen, every team, every time synced before anyone reaches for the reload button.