Neople

The connectors take authenticated action in systems of record, not notifications.

The published catalog spans helpdesk and contact center with Zendesk, Freshdesk, Gorgias, Front, Trengo, Belco, CM.com, Genesys, Help Scout, Salesforce and Zoho Desk; order management and commerce with Shopify, Magento, WooCommerce, NetSuite, Lightspeed, Picqer, Monta, Mews, Afas, ChannelEngine, Sylius, Logic4, Sherpa, Afosto, Firmhouse, Stocky, Shopctrl and Fieldbuddy; carriers with UPS, DHL, DPD, FedEx and PostNL; returns and tracking with Returnless and Tracey; product feeds with Inriver and Channable; and messaging with WhatsApp, Telegram, Slack, Teams, Discord and Google Chat.

The actions are writes: Neople describes the agent checking an order, starting a return and updating an address inside the customer's systems once a workflow is approved, and the published WISMO workflow fetches order details from Shopify, fetches shipment details from Returnless and posts the reply in Zendesk. Unlisted systems are connected via API or login-based access.

The connector count differs by page: more than sixty platforms on the quick start page and homepage, more than a thousand in that page's own metadata, and more than three thousand systems reachable from Studio on the platform page. The named connectors are firmer ground than the totals.

Sourceneople.io integrations, platform and quick-start automation pagesread 2026-09-05

Two authoring surfaces sit over one multi step execution engine: a logic-based node view for visual thinkers and a sequential handbook view for teams that already run written SOPs, with Neople's stated position that either fits around an existing process. Both compose a real sequence with external calls interleaved, shown end to end in the published WISMO workflow as receive ticket, fetch order details from Shopify, fetch shipment details from Returnless, apply the agent instruction, create the response and send it in Zendesk.

Neople describes more complex workflows carrying custom logic and multiple integrations, and the agent executing the approved workflow itself, checking an order, starting a return or updating an address without a person to run the steps. Workflows are versioned, published, rolled back, and composed conversationally by asking the Neople in plain language to build one. Branching and retry behavior is implied by the logic-based view and by workflows with custom logic, but no condition, fallback or retry node is individually documented.

Sourceneople.io quick-start automation and platform pagesread 2026-09-05

The agent is grounded on a maintained corpus managed as its own surface. Knowledge is a first-class section of Neople Studio alongside Tasks, History, Insights, Integrations and Tone of voice, and the published workflow instruction editor attaches it directly, offering Knowledge, Actions and Web search as things an operator adds to a step.

Neople's own worked example makes the grounding behavior explicit: the agent is told to answer from the available knowledge base and ticket information, to search an attached returns policy document for a matching answer, and to say so honestly when it cannot find one, which is retrieval against customer documents with an instructed refusal rather than model recall. Each Neople is trained on the customer's own documentation, tools and historic conversations, and the pricing page confirms the knowledge base is one of the systems connected at go-live. The retrieval mechanism, index type, chunking and refresh behavior are not documented, so the corpus is established and its machinery is not.

Sourceneople.io quick-start automation, platform and pricing pagesread 2026-09-05

The customer holds the publish switch, and the permission model says who may throw it. A workflow cannot act until it is published, publication follows a test run on dummy data, and Neople states plainly that nothing goes live without the customer's approval. Roles are configurable against that boundary, with a published setting where agents can publish workflows and another where managers must approve changes, so an organization decides whether its support staff can ship agent behavior at all.

Behavior inside a workflow is authored in an instructions editor holding the goal and numbered steps, including an instruction to state honestly when an answer cannot be found, which is an operator-written refusal rule. After the fact there is action history, versioning and rollback to any earlier version, and escalation to a person is the product's premise, with the team keeping the moments that need one. The dedicated product specialist and CSM who optimize workflows on the paid plans are a service, not a platform control.

Sourceneople.io platform and quick-start automation pagesread 2026-09-05

Certification and customer facing controls are both documented. Neople states it is ISO 27001 certified and displays the certifying body's mark alongside IAF and ANAB accreditation marks, and it runs a live trust center at trust.neople.io on Vanta's EU instance, described as the place to request the subprocessor list and security documentation.

Single sign-on, roles and permissions, and a full audit trail are listed on the homepage, and the platform surface shows per-user roles with a configurable rule that agents may publish workflows while managers must approve changes. Neople also publishes GDPR compliance, a DPA, TLS protection on all traffic to and from the platform, a named information security officer contactable at a published address, and a stated position on EU AI Act transparency. The certificate's scope, number and audit period are not published on the public pages.

Sourceneople.io homepage and platform pages, trust.neople.io, neople.io privacy policyread 2026-09-05

A run level record and an account level audit trail are both presented as the point of the product. Neople frames the alternative as a black box and offers the opposite: every conversation, every action and every edit, so a customer always knows what the agent did and why.

History is a named Studio surface for viewing the Neople's past runs, and each run is inspectable step by step, the published example resolving into receive ticket, fetch order details, fetch shipment details, apply instruction, create response, send response. Versioning records what was live when, timestamped, with earlier versions retained. Insights reports per-workflow volume, total runs and handling time. Underneath sits a full audit trail listed as a security control alongside SSO and roles, so a customer's IT and security team can see who did what.

Sourceneople.io platform and homepageread 2026-09-05

State persists and the agent improves, but neither is an agent memory layer. Each Neople is trained on the customer's historic conversations as well as their documentation, the privacy policy names training the Neople as a distinct processing purpose using conversation content to evaluate performance and produce better replies, and Neople states the agent improves from the team's edits and feedback so results compound after go-live. Retention is governed and stated, with data returned or deleted within thirty days of contract termination.

Learning absorbed into a model is not a memory layer, and neither is a ticket record the helpdesk already holds. Nothing documents what an agent retains between separate conversations with the same customer, at what scope, for how long, or how an operator inspects, edits or clears it, and no memory feature exists in Studio, whose named sections are Tasks, History, Insights, Integrations, Knowledge and Tone of voice. History is a log of past runs and the document corpus is reference material, so neither serves as memory.

Sourceneople.io privacy policy sections 1 and 2, platform and pricing pagesread 2026-09-05

Data stays in one region, stated as a property of the service rather than offered as a choice. Neople lists EU data residency alongside ISO 27001 and GDPR on its homepage, tells buyers their customer data stays in Europe, and states in its privacy policy that the services are mainly managed and operated from the European Economic Area, with transfers outside it only to adequate countries or under Standard Contractual Clauses, the named exceptions being the US model and credential subprocessors.

For the European support teams Neople sells to, that is the answer they want, but a buyer with a different requirement could not get a different one: there is no region selector, no menu of data centers, no VPC, no single-tenant option and no self-hosted or on-premises deployment. Adequacy findings and Standard Contractual Clauses are legal cover rather than a residency choice.

Sourceneople.io privacy policy section 3, homepage and quick-start automation pagesread 2026-09-05

A searchable template library lives inside the product. Neople's quick-start page shows a template picker with a search field and named, individually openable entries covering the recurring support jobs: WISMO with resolve-WISMO-tickets, FAQs, refunds with refund-eligible-orders, product information, returns with resolve-eligible-returns, and damaged orders. Neople frames the product around it, telling buyers to pick a template and connect their tools, to start from a template rather than a blank page, and that Neople comes loaded with ready-made templates, with an invitation to explore a full range of them.

A selected template arrives as a working multi-step workflow rather than a prompt: the published WISMO example runs receive ticket, fetch order details from Shopify, fetch shipment details from Returnless, apply the agent instruction, create the response and send it in Zendesk, sitting in a not-live state with a publish control. The visible set is six templates plus a search field implying more, and no per-template public page or count exists, so the catalog's depth is not established.

Sourceneople.io quick-start automation and platform pagesread 2026-09-05

Neople reaches widely but work travels one way. The agent works inside Zendesk, Freshdesk, Trengo, Gorgias, Zoho Desk, Front, Belco, CM.com, Genesys, Help Scout and Salesforce, and in messaging on WhatsApp, Telegram, Slack, Teams, Discord and Google Chat, in the customer's own tools rather than a Neople-branded surface, across English, German and Dutch-facing deployments. Every documented path starts with an inbound ticket.

The published workflow opens on receive ticket, the pricing model meters tickets handled, and no scheduled run, outbound campaign, proactive follow-up or event-driven initiation is documented on any product page. The privacy policy says conversations may be initiated by a Neople, but it names no mechanism, trigger type or configuration surface.

Sourceneople.io platform and homepage, privacy policy section 1read 2026-09-05

Three model providers are named in the legal tier, and the customer does not pick between them. The privacy policy states that personal data is transferred outside the EEA only in the context of services provided by OpenAI OpCo LLC, Cohere Inc and Anthropic PBC, alongside Bitwarden, each under a data processing agreement and Standard Contractual Clauses.

Bitwarden is credential management rather than a model provider, and Cohere alongside OpenAI is consistent with a retrieval stack using one provider for generation and another for embedding or reranking. No model dropdown, routing configuration, bring-your-own-key path or per-workflow model choice appears on any product page, and nothing documents which provider serves which function or whether a customer can influence it. The policy was last amended 4 July 2025 and says all three subprocessors while listing four entities, so the list may lag the current stack; the trust center holds the maintained list.

Sourceneople.io privacy policy section 3read 2026-09-05

No API, SDK, developer documentation, webhook reference or MCP endpoint is published, and there is no docs or developer subdomain. Every documented interface runs inward: Neople connects to the customer's systems, and where a tool is not on the standard list, Neople's own team makes the connection via API or login-based access during onboarding.

That is Neople calling out to other systems, with Neople's staff doing the work as a service rather than a customer capability. The product is deliberately positioned away from developer access, with the quick-start page promising no developers and no documentation to read, and the builder described as usable without one.

Sourceneople.io quick-start automation and platform pagesread 2026-09-05

Testing before release and reading the result both happen on customer facing surfaces. A workflow sits in a not-live state with a publish control, a Test action runs it step by step, and Neople tells buyers that nothing goes live without approval, that every workflow goes through their test environment first, and that they test it on dummy data and say when it is ready. Versioning sits underneath, with published versions listed by timestamp, one marked live, and rollback to any previous version.

The result is read in Studio's Insights view, which reports per workflow unique tickets, total runs, CSAT, automation rate and average handling time, and carries a dedicated Evaluations tab alongside top workflows and volume, so what is tested is the customer's own workflow. Neople's specialists build and optimize workflows under the Professional and Enterprise plans as a service; every surface above is one the customer operates.

Sourceneople.io platform, quick-start automation and pricing pagesread 2026-09-05

The agent reaches a system by signing into it when there is no interface to call. Neople states that its standard connector list covers Zendesk, Freshdesk, Trengo, Shopify, Slack, Teams, Zoho and sixty-odd others, and that where a specific tool is not on that list the connection is made via API or login-based access.

Login-based access means acting inside a third-party product through the interface a human would use, in a surface Neople does not control, and the platform page's account of the agent navigating, pulling and updating information in the customer's tools is consistent with it. No browser control, hosted session, virtual desktop or interface-automation product is documented.

Login-based access is a fallback connection method mentioned in a support FAQ, offered after an API, with no description of how a session is authenticated, supervised, recorded or bounded.

Sourceneople.io quick-start automation and platform pagesread 2026-09-05