Build customer conversations into your product
Masheev brings customer conversations, AI agents, business knowledge and human handoff into one workspace. Start with a website assistant, then connect the business actions your customers actually need.
Start with a working customer journey
The fastest route is Integrate with AI: give your coding agent one page and let it inspect your existing app, plan, implement and verify the result. For a manual integration, start with a chat inbox in the dashboard and the Chat SDK.
Choose your integration path
| You need | Use | Runs where |
|---|---|---|
| Ready-made website assistant | @masheev/embed-sdk/js or /react | Your website, with a hosted widget iframe |
| Assistant actions in your app | Client tools calling your authenticated backend | Browser → your server → your service |
| Custom conversation UI | @masheev/embed-sdk/headless | Your React app |
| Editable UI components | Masheev component registry | Source copied into your app |
| Workspace and contact operations | Supported REST API or verified typed API client | Trusted backend |
| API access for a coding assistant | @masheev/mcp | Local stdio process in the assistant's host |
How the pieces fit
Your organization owns the data and configuration. An inbox connects a channel. An AI agent answers with your instructions and knowledge, calls available tools, and hands off when needed. A contact represents the customer; a conversation contains their messages and the team's replies.
The widget needs public inbox configuration. Management API keys and provider credentials stay on a backend. For signed-in users, your server computes an identity signature so a browser cannot impersonate another customer.
Connect existing services
Reuse your application's existing server adapters for order lookup, account help or booking. A browser tool calls your authenticated route; that route enforces customer and tenant permissions before contacting the service.
Custom application code is different from a native Masheev connector. Do not assume a Shopify, HubSpot, Salesforce or Stripe agent connector exists because your application already uses that provider. See business tools and availability.
Availability and account access
Web chat, supported APIs, AI agents and knowledge are launch capabilities. Developer SDK/MCP surfaces and several provider channels are beta. Generic custom incoming/outgoing webhooks and several native connectors are currently off. The availability reference is generated from the product registry; your workspace's permissions, subscription and provider state still apply.
For coding agents
All guides have a .md version, linked at the top of each page. Start at
/llms.txt for focused discovery, or use /llms-full.txt
when a single full document is needed. The OpenAPI snapshot
contains request and response schemas; it does not grant account access.