Skip to main content
NextIntent watches how each visitor moves through a website, notices the moment one of them gets stuck or is weighing a decision, and either says one sentence built from facts the site supplied or records the moment for you to read. The Shopify app is one client of the same NextIntent. Everything it does, a site of any kind can do through the console and the API.

​
What it reads

The SDK on your pages reads movement, not words: where the visitor is, how long they have been there, what they scroll back to, what they hover on long enough to count as attention, how many clicks in the last ten seconds, whether a form was submitted and whether the page answered with a validation message. It also reads the cart when the page reports one. It never reads what a visitor types into a field; values are hashed on the page before they leave it. See Privacy and data. From those signals the engine keeps a live picture of each visitor for the length of the visit, called the fold. A moment is judged from that picture, never from a single event.

​
The moments it recognises

The engine looks at a visitor when they go still and asks whether this is a moment worth acting on. The rules are the same on every site; the store rules only apply on cart and product pages. On a site of any kind it recognises:
  • Dwelling on a high-intent page. A pricing, plan, demo, contact, trial, quote or comparison page, settled on for a while, then still.
  • A form stall. A form page with time on it and no submit, where the visitor is not typing. On a phone an idle stretch on a form usually means the keyboard is up, so the bar is higher there.
  • A failed attempt. The same form submitted twice with the same values, a validation message the page repeated, or a submit followed by rapid clicking on the same form.
  • Struggle. Rapid clicks, scroll thrashing (many direction changes in a minute), churning through help pages, bouncing back and forth between two pages.
  • Deliberation. Several product, pricing or comparison pages over a couple of minutes with steady reading and no thrash. Nothing is wrong; the visitor is choosing.
  • Settled attention. A hover that stays on one element (a plan name, a feature row) long enough to count.
  • A churn-risk path. A billing, cancel or downgrade page.
  • Store situations. The cart sitting still, a discount code the page declined, options flipped without adding, the size a shopper cannot buy. These are described for shop owners in The moment.
A visitor is not looked at in the first 30 seconds of a visit or the first 20 seconds on a page, and not while they are typing. Someone who has been still for the whole page, someone on a media page, someone on a careers page, and someone who just converted are left alone. Each visitor is engaged at most once per visit.

​
What it decides

For each moment the engine reaches one of three answers. Engage means this is the moment, with a mode (sales, support or retention) and a tier: a nudge is a short warm opening on the topic in front of the visitor; an assist is aimed at one specific evidenced need, a stalled form or two plans held side by side. Wait means right visitor, wrong instant, and the visitor is looked at again in about two minutes. Quiet means a non-target (someone on a careers page, a parked tab) and the visitor is left alone for a long window. Every decision is recorded with the reason the moment surfaced, the answer, and what happened next. That record is the Moments view.

​
What it can say

On a site with a facts sheet, an engage produces one sentence built from the sheet: the free shipping line and the gap to it, a return window, a delivery promise, a size note for the product on the page, or an offer when the sheet allows offers and the visitor’s own code was declined. The sentence is checked against the sheet before it is shown; a claim the sheet does not back is dropped and the visitor sees nothing. The page shows it as a card, a browser event for your own rendering, or a popup tool campaign. See The card and The facts sheet. On a site with no facts sheet the engine still decides and records every moment, and writes what it would have said, but nothing is shown to the visitor. That is watch mode by another route, and it is the right starting point for any site: read what it saw for a week, then give it facts.

​
What a chat agent gets

A chat agent that supports MCP can ask NextIntent about the visitor it is talking to: what they are doing right now, the pages they came through, whether they have visited before, and what the engine made of the visit. It gets an opaque visitor id and behaviour, never a name or an email unless the site has visitor identification on. See Chat agents and MCP.

​
The pieces