In-page placement
Put your Aijent inside a page, already open, instead of waiting in the corner.
In-page placement puts your Aijent inside a page, already open, as part of the content, instead of waiting in the corner. It works well on landing pages, where a conversation usually outperforms a form. Turn it on from the In-page Aijent tab (on Relay Growth, the In-page Aijent section of the Installation tab), then paste the in-page code exactly where you want it to appear. It is available on Growth, Pro and Relay Growth. It is not on Starter or Relay Starter.
Normally your Aijent waits in the corner until somebody clicks it. In-page placement puts it directly into a page, already open, as part of the content.
The difference matters. A launcher asks somebody to take an action first. An in-page Aijent is simply there, mid-conversation, where a button would otherwise be.
Where it works well
Landing pages. A conversation in the middle of a landing page usually outperforms a form, because it starts by helping rather than asking.
One high-intent page. Your pricing page, or the page describing your most considered product, where visitors have questions and a form cannot answer them.
Campaign pages where you are paying for the traffic and want the best possible chance of a conversation.
It is not meant for every page. Used everywhere it stops feeling deliberate.
Turning it on
- Open your Aijent and go to the In-page Aijent tab. On Relay Growth, it is the In-page Aijent section at the bottom of the Installation tab.
- Turn on Show this Aijent inside a page. The look options and your code appear underneath.
- Under How it looks on your pages, choose how it should look, then click Save changes. See below.
- Copy the code under Your in-page code further down. It is one paste containing both a marker and the script.
- Paste it into your page exactly where you want the Aijent to appear. The place you paste it is the place it shows up.
Every platform install guide has a section at the bottom with the exact steps for that platform, since where you paste it differs between a Shopify section, a WordPress block and a Webflow embed. A few platforms cannot host an in-page Aijent at all, and their guides say so.
You add it the same way you would any other code block: an HTML or embed block in your page builder.
How it looks on your pages
These choices are saved with your Aijent, like the rest of its settings. A change reaches every page that already has the in-page code, so there is nothing to paste again. They apply to every in-page Aijent on your site for that Aijent.
- Coloured header. Uses the same coloured header as your launcher's chat window, in your Aijent's colour, instead of the slim white strip.
- Show the launcher after scrolling past. Your launcher appears whenever no in-page Aijent is on screen, carrying on the same conversation, and steps aside again while one is in view.
- Returning visitors start with a clean chat. Someone coming back sees a fresh "Welcome back" instead of their earlier messages, with a link to show them. Your Aijent still remembers the conversation, and the full history stays in your dashboard.
- Open at this height straight away. Opens at full height and stays that size, like an open chat window, a little shorter on a phone so it fits the screen. Leave it unticked and it starts small, then grows as the conversation goes.
- Height. How tall it can be, between 360 and 800 pixels. About 520 looks like a standard chat window.
What happens on those pages
On any page carrying the in-page code, your Aijent appears inside the content and the floating launcher steps aside, unless you chose Show the launcher after scrolling past. Every other page on your site keeps the launcher exactly as before.
That is deliberate. Two of the same Aijent on screen at once would be confusing, so the in-page one wins where you have placed it.
The proactive behaviours, such as the teaser bubble or opening automatically, are switched off on those pages. Your Aijent is already open, so there is nothing to attract attention to.
How it behaves
It opens with your normal greeting for a new conversation, the same first line your launcher uses. A returning visitor picks up where they left off, unless you chose a clean chat for returning visitors.
It starts compact and grows, unless you chose to open it at its full height.
On a phone it goes full screen when somebody starts typing, so they can actually see what they are writing, and returns to the page afterwards.
It appears as the page is scrolled to it, rather than loading everything up front.
More than one on a page
You can place it as many times as you like on the same page. A long sales page might have one after the pricing and another at the very bottom, so a visitor never has to scroll back to ask a question.
They all share one conversation. Somebody who asks a question in the first box and scrolls down to the second finds the same conversation waiting, not a fresh greeting. It is one visitor and one conversation, however many boxes they pass.
A box catches up when it scrolls back into view, including anything said in the launcher's chat window. If two are on screen at once, they will not mirror each other as the visitor types. A box is never changed while a reply is on its way, and never loses messages it is showing.
On a phone, typing opens one full-screen chat. Tapping to type in any box opens a single full-screen chat on the same conversation. Closing it returns the visitor to where they were, and every box catches up.
Testing it
Open the page in a brand new private or incognito window and scroll to where you placed it. Check it appears where you intended, that the launcher is absent on that page, and that it is still present on your other pages.
Check it on a phone too. In-page placement is more sensitive to layout than a corner launcher, because it has to live inside your design.
In-page placement is available on Growth, Pro and Relay Growth. You can see your current plan and change it on your billing page.