One conversation record
Envelen is not an email tool with AI added on top. Messages arrive through the product widget and stay connected to the customer, their organisation, plan, current page, assignment, and complete conversation history.
The Inbox gives teammates one place to understand what happened, who is responsible, and what should happen next.
- Verified customer identity
- Current product context
- Assignment and status history
- A clear author for every reply
AI with accountability
Envelen Copilot uses published Knowledge and safe conversation context to prepare a draft or recommend a handoff. During the supervised beta, a human teammate reviews every draft before anything reaches the customer.
That boundary keeps the speed of AI without hiding who made the final decision.
- Published Knowledge only
- Visible sources and rationale
- Human review before send
- Immediate handoff when evidence is weak
Built for products, not just channels
A short-lived support token identifies signed-in customers without trusting browser-supplied identity. Origin controls protect anonymous sessions, while scoped API keys and signed webhooks connect Envelen to the rest of your product.
The result is a support surface that can grow with the application instead of becoming a separate operational island.
- React widget SDK
- Versioned public API
- HMAC-signed webhooks
- Application-level boundaries
Limits that do not break support
Plans make conversation, teammate, application, and managed AI allowances visible. At the managed AI limit, human support continues. At the conversation limit, existing threads stay open while new threads wait for the next monthly reset. OpenAI or Mammouth BYOK stays outside the managed AI allowance.
The product tells the team what is limited before the limit changes the workflow.