S·A·Y — Semantic Action Yield
Ordinary bots just give you answers. SayP is an Autonomous Action Engine that connects your existing ERP and CRM software to WhatsApp with zero code. Just say it; SayP understands, triggers your APIs in the background, and executes transactions to your database in seconds.
SayPartner AI
Online
Field teams and warehouse staff aren't at desks. Using ERP on mobile is painful, and training costs are sky-high.
7 clicks to create an invoice, mandatory login for a stock query. Wasted time kills productivity.
Market assistants only talk. They inform but never create invoices or update stock. Bot ≠ Executor.
We're middleware. We sit in front of your system — we don't break it, we just let humans talk to it.
| Feature | Traditional Chatbot | SayPartner AI |
|---|---|---|
| Operation | Q&A loop | ✓ Direct API Calls |
| Capability | Informational / Guidance | ✓ Executes Real Actions |
| Data Access | Read-only | ✓ Full CRUD Authority |
| Integration | Months of custom dev | ✓ 5 Minutes via Swagger |
Your Project → SayP AI → WhatsApp — real-time action flow
4-layer isolated architecture: Domain → Application → Infrastructure → API.
Every customer is fully isolated. Data and integrations never mix.
Rule-based, Pattern Matching, and AI-Powered hybrid classification.
WhatsApp
SayP AI Engine Customer API (REST / MCP)Cloud API integration, webhooks, 24-hour window management, message retry.
Natural language → JSON command extraction, confidence scoring, slot filling.
REST API (Swagger) or MCP Protocol with plugins for .NET, Node.js and Go — 2 integration paths.
Company-level isolation, user roles, department management.
HMAC-SHA256 webhook verification, API key auth, JWT tokens.
Message stats, command success rates, 7-day breakdown.
Turkish and English NLU, automatic language detection.
Understands photos and voice recordings sent via WhatsApp.
Skip AI calls on repeated requests — speed and cost optimization.
Just paste your Swagger URL. SayP discovers all endpoints, analyzes with AI, and makes them instantly available. Best for APIs accessible from the internet with static tokens.
Add a lightweight plugin to your project. Controllers are auto-discovered. No token expiration, works with private APIs. Available for .NET, Node.js, and Go.
"How many MacBooks in stock?"
"Create a 5-laptop invoice for ABC Ltd."
"Add new customer: John Smith, 0532..."
"Book a VIP cabin for 2 guests."
Let your employees manage systems by typing on WhatsApp. Stop wasting time with complex interfaces.
SayP acts as a middleware — we relay messages between WhatsApp and your system's API. We do not store your ERP/CRM data. Conversation logs are kept temporarily for debugging (configurable retention). All communication uses HTTPS with HMAC-SHA256 webhook verification.
REST integration connects via Swagger URL — no code changes needed, but requires a public API and a non-expiring token. MCP integration uses a lightweight plugin inside your project — supports private APIs, no token expiration, automatic controller discovery. For JWT-based APIs, MCP is recommended.
OpenClaw is an open-source autonomous AI agent for developers — it runs locally, communicates between AI agents, and is used for coding/chat. SayP is a Business Action Engine — it connects your ERP/CRM to WhatsApp so employees can execute real transactions (create invoices, update stock) via natural language. SayP doesn't compete with OpenClaw; they solve completely different problems.
SayP includes a confirmation mechanism for write operations (POST, PUT, DELETE). Before executing destructive commands, SayP asks for confirmation on WhatsApp. Additionally, you can disable specific endpoints from the Portal dashboard.
For REST integration: any language with Swagger/OpenAPI support. For MCP plugin: we provide official plugins for .NET (NuGet), Node.js (npm — Express, Fastify, NestJS), and Go (Gin, Echo, Chi, net/http). Any API that speaks HTTP can be integrated.
Not with MCP! The MCP plugin runs inside your application — SayP connects to the plugin endpoint, and the plugin makes internal calls to your controllers. Your API can remain completely private. For REST integration, the API needs to be accessible from SayP's servers (public, VPN, or IP whitelist).