What it is

A drop-in SDK that turns a landing page's existing web form into an agent-guided conversation, in place. The agent reads the form you already have, asks for what is missing one thing at a time, writes the answers into your real inputs, and hands the visitor back to your own submit button.

It is not a chat bubble in the corner. The conversation stands where the fields were.

Where the idea comes from

In the early days of interactive voice, VXML expressed a web form as audio: the form was still the form, and the voice layer was a way through it. This is the same move for the web. The form stays the source of truth — its fields, its validation, its action, its submit handler — and the agent becomes a way through it for a visitor who would otherwise have closed the tab.

That constraint is what makes it installable. There is no new form to build, no schema to author, and no second lead path to reconcile. What to collect is read off the markup; what the agent is for is configured on the Namakina side.

The fields give way to a conversation, in the place they were.

What a visitor experiences

A short panel takes the place of the fields, with a thin progress strip above it. The agent asks for one field at a time — chips for a choice, a text box for the rest — and the text box is always there, so the visitor can answer, ask a question, or say they are not sure at any moment, including mid-field. The agent answers and carries on.

Where the campaign supports it, the agent can put a richer block on the page: a question unit with image tiles, a set of option cards each with a reason it fits, or a plan the visitor can copy and keep. See What the agent renders.

What it is not

• It does not replace your form. The <form>, its action, its inputs and its submit button are never swapped out. See Submit.
• It does not tick your consent box. Disclosure blocks and their checkboxes are detected and locked; the agent may point at them and never fills them.
• It has no callbacks. There is no onReady, no onSubmit, and no custom DOM event. The public surface is three functions and the data-nam-* attributes.
• It is not a one-way bet. Every page carries a built-in holdout, so the arm that gets the agent is measured against the page exactly as it was. See Rollout and holdout.

Next

Quickstart is the ten-minute version: an .npmrc line, an install, three attributes and a script tag.