Install the widget
Publish a floating or inline Fetchply chat, configure its opening mode, and verify the live installation.
Open the selected agent and choose Deploy. Copy code from your own dashboard so it contains the correct host and agent ID.
Place the provided script before the closing </body> tag. Load it once per page. Choose a platform in Deploy for builder-specific steps.
Use the iframe from Deploy → Advanced. Set a responsive width and an accessible title. Keep clipboard permission if your experience needs it.
In the embedded app, open Settings → Widget embed, then Open theme editor. Turn on Fetchply Chat under App embeds and save the theme.
How it appears on mobile
On phones the chat opens as a panel that covers about 85% of the screen and rests against the bottom edge, so visitors can still see part of your page above it. To use the whole screen, tap the expand control (the upward chevron) in the top corner of the chat. Tap it again (it becomes a downward chevron) to return to the shorter view. Closing the chat resets it to the shorter view the next time it opens. On desktop the widget keeps its usual fixed size.
Open chat from your own button
After the floating script loads, add data-fetchply-open to a button to open chat. Use data-fetchply-message with a text value to open chat and submit that message.
The agent knows which page the visitor is on
With the floating widget installed, the agent is told the address and title of the page the visitor is chatting from, so questions like "is this product in stock?" or "does this apply to the plan on this page?" get grounded answers without the visitor pasting a link. Only the page address and title are shared: anything after ? or # in the address (such as search terms or tracking codes) is removed before it reaches the agent, and nothing the visitor types on your page is ever read.
Verify
Publish and clear stale previews
Save the production site. Use a private window to avoid an old cached page or prior conversation state.
Test both breakpoints
Open the launcher on a desktop and a narrow mobile viewport. Check focus, scrolling, close behavior, and overlap with site controls.
Send a message
Confirm the reply and check Inbox for the new Widget conversation.
Do not paste a secret into widget code. The agent ID is public by design; API keys and integration credentials are not.
Widget and branding
Configure the visitor-facing Fetchply experience, publish it on a website, and verify it across screen sizes.
Identify logged
Tell the chat who is signed in so the agent greets people by name and your inbox shows whose conversation is whose. Examples for Shopify, WordPress and Next.js.