Web agent

​

Quick start

<script src="https://nixflex.com/button.js"
  data-number="+447460044516"
  data-design="10"
  data-color="#7C6BEF"
  data-name="Basilo Pizza"
  data-chips="Book a table, Opening hours, Prices"></script>

​

Script attributes

​

Designs

​

How the chat behaves

• Knowledge: the web agent answers ONLY from the number’s web instructions (web_prompt). It does not use the voice agent’s call prompt. Empty instructions = a safe minimal fallback that tells visitors to call the business. Cap: 5,000 tokens (about 20,000 characters).
• Greeting: when the panel opens, the assistant sends one live greeting (“Hi there! How can I help you today?”) after a short typing animation.
• Memory: the visitor’s browser keeps the conversation and sends the last 20 messages with each request, so the assistant remembers context within and across visits on the same browser.
• Booking: the web agent cannot book, cancel, or change appointments. It tells visitors to call for those - the voice agent handles booking.
• Failed replies: network or server problems show a polite retry message; the visitor’s page is never affected.

​

Web calls (voice in the browser)

​

Conversations in the dashboard

• One inbox per number. All websites using that number feed the same inbox - the design used does not matter.
• Visitor identity: visitors are anonymous. Each browser gets a stable id, shown as a friendly number like Visitor 4821. The same browser stays the same visitor across visits (id lives in the browser’s localStorage). A different browser, device, or private window is a new visitor - that is normal for anonymous web chat.
• If a visitor leaves a name or phone number in the chat, it is right there in the messages - that is how you capture leads.
• Order: newest conversation first. Click any visitor to read the full thread (visitor left, agent right).
• Retention: conversations are kept for 90 days, then deleted automatically every night. There is no manual delete - the retention window is the lifecycle.

​

Managing by API

curl -X PATCH https://api.nixflex.com/v1/phone-numbers/+447460044516 \
  -H "Authorization: Bearer nxf_xxx:nxfs_xxx" \
  -H "Content-Type: application/json" \
  -d '{"web_prompt": "You are the web assistant for Basilo Pizza. Opening hours: ..."}'

POST https://api.nixflex.com/v1/widget/message
Content-Type: application/json

{
  "number": "+447460044516",
  "history": [
    { "role": "user", "content": "What time do you open?" }
  ],
  "session_id": "wsmsgd6m4tt9e1hi12"
}

{ "ok": true, "reply": "We open Mon to Fri, 9am to 6pm. Want to give us a call?" }

• history is the running conversation (user / assistant roles), newest last. Send the last 20 messages.
• session_id is any stable per-visitor string. It groups messages into one conversation in the dashboard. Omit it and the chat still works, but the conversation is not stored.
• Failures return { "ok": false, "reason": "..." } with HTTP 200 - reasons include unavailable (no credit or number not found) and server_error.

​

Pricing

​

Privacy and limits

• Visitors are anonymous - no cookies are set by Nixflex, no tracking across websites. The visitor id lives only in that browser’s localStorage for that site.
• Conversation content is stored for 90 days for the business owner, then deleted automatically.
• Web instructions cap: 5,000 tokens. Chat memory: last 20 messages.
• The widget script is served from https://nixflex.com/button.js and updates automatically - embeds never need re-copying for improvements.

​

FAQ