Neo for Business
Join the waitlist

Neo for Business

Connect Neo to your website and your systems.

One tag, a plugin, or your own API. Neo only does what you allow.

Join the waitlistTalk to Neo

Ways to connect

From one tag to your whole system.

Pick one way, or use them together.

One script tag

Live

Website chat

Paste one tag on any website, and Neo answers your visitors.

  • Works only on the domain you registered
  • Arabic or English, following your page
  • Your brand color
  • Your team can take over any chat

Two plugins

Live

WordPress and WooCommerce

Download the ZIPs from the Neo app and upload them to WordPress. One adds the chat, the other connects your store.

  • Reads your catalog, stock, prices and order status live
  • Nothing is synced or copied

API actions

Live

Your own system

Neo calls your HTTPS API through actions you define and test in the Neo app.

  • A rule on each: Allowed, Ask me first, or Off
  • Your keys are stored encrypted
  • No DELETE, ever

Website chat API

Live

Your own chat window

Build your own chat on the website chat API. A client already runs one.

  • A visitor token lasts 7 days
  • Works only from your registered domain
  • Four endpoints, version 1

Server to server

On request

Engine API

Reply in your customers’ WhatsApp chats and read new messages, from your own server.

  • Keys come from the Neo team
  • An Idempotency-Key on every send
  • 120 requests a minute per key

Coming soonShopifyOnline store

How it works

Step by step, done with you.

The Neo team walks every step beside you.

  1. Get your tag or plugin.

    Add your website once in the Neo app. It gives you the exact tag, or the plugin ZIPs for WordPress.

  2. Add your actions, and test them.

    Point each one at your HTTPS API. It goes live only after a real test passes.

  3. Give each action a rule.

    Allowed, Ask me first, or Off. Ask me first waits for your OK before anything reaches your system.

  4. Switch it on, together.

    The Neo team switches it on with you.

For developers

A tag, a session, a send.

Swap the placeholders, like YOUR_SITE_ID, for the values the Neo app and the Neo team give you.

  1. Website chat tag

    Add it to your pages once. The Neo app gives you the exact tag, and it only works on the domain you registered.

    Request · HTML
    <script defer data-site="YOUR_SITE_ID" src="YOUR_WIDGET_URL"></script>

  2. Open a visitor session

    Your own chat window starts here: a visitor token for your registered domain. A token lasts 7 days.

    Request · curl
    curl -X POST "{NEO_API}/api/webchat/v1/sites/YOUR_SITE_ID/sessions" \
  -H "Content-Type: application/json" \
  -d '{ "origin": "https://YOUR_DOMAIN" }'
    Response · 201
    { "schemaVersion": 1, "token": "VISITOR_TOKEN", "expiresAt": "…" }

  3. Send a visitor’s message

    Send with the visitor’s token. Errors always come back as one shape. Version 1 has four endpoints, and the Neo team walks you through all four.

    Request · curl
    curl -X POST "{NEO_API}/api/webchat/v1/messages" \
  -H "Authorization: Bearer VISITOR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "id": "MESSAGE_UUID", "text": "Is the blue one in stock?" }'
    Response · 202
    { "schemaVersion": 1, "accepted": true, "messageId": "…" }
    Error · 401
    { "schemaVersion": 1, "error": "expired" }

  4. One action, start to finish

    You define the action and test it with the Neo team. When a customer asks, Neo calls your system and answers from what it returns.

    The action
    Name     Check an order
Method   GET            GET, POST, PUT or PATCH. Never DELETE
URL      https://YOUR_DOMAIN/api/orders/ORDER_ID
Key      YOUR_API_KEY   stored encrypted, never shown again
Rule     Allowed        or Ask me first, or Off
Test     passed         a real test runs before it goes live
    Request · HTTPS
    GET https://YOUR_DOMAIN/api/orders/ORDER_ID
    Response · 200
    { "status": "YOUR_ORDER_STATUS", "eta": "YOUR_DELIVERY_TIME" }

  5. Send into a WhatsApp chat

    Engine API, from your server, with a key from the Neo team. Retry with the same Idempotency-Key and it never goes out twice. 120 requests a minute per key.

    Request · curl
    curl -X POST "{NEO_API}/engine/v1/messages" \
  -H "Authorization: Bearer YOUR_ENGINE_KEY" \
  -H "Idempotency-Key: A_NEW_UUID_PER_SEND" \
  -H "Content-Type: application/json" \
  -d '{ "conversation_id": "CONVERSATION_ID", "text": "Your order is on its way." }'
    Response · 201
    { "message": { "id": "…", "conversation_id": "…", "status": "…" } }

  6. Read what happened

    Events come in order, up to 200 a page. Keep next_cursor and pass it back to carry on where you stopped.

    Request · curl
    curl "{NEO_API}/engine/v1/events?cursor=NEXT_CURSOR&limit=200" \
  -H "Authorization: Bearer YOUR_ENGINE_KEY"
    Response · 200
    { "data": [ … ], "page": { "next_cursor": "…", "has_more": false } }

Engine API keys come only from the Neo team.

Request API access

Safe by design

Your system stays yours.

Neo works inside the limits you set, and the code holds them.

Locked to your domain.

The chat and its API answer only the exact domain you registered.

Keys stay encrypted.

Stored encrypted and never shown again. Neo itself never sees them.

No delete.

Actions use GET, POST, PUT or PATCH. Never DELETE.

Ask me first means it.

Nothing reaches your system until you approve.

No double sends.

Every engine API send needs an Idempotency-Key. A retry with the same key gets the first answer back.

A steady pace.

120 requests a minute for each engine API key.

Your Neo, connected with you.

When your spot opens, the Neo team connects it with you, and your 24 free days start.

Join the waitlistRequest API access
Ask Neo