# Availability

Generated from Masheev's product capability registry. This describes product scope,
not your workspace's effective permissions or provider connection state.

**Launch** means implemented within normal plan/account/provider requirements.
**Beta** means restricted eligibility or additional evidence is required.
**Off** means unavailable; do not implement or advertise it as a working integration.

| Capability | Status | Boundary |
| --- | --- | --- |
| marketing site | launch | Public marketing, pricing, legal, support, status, security and deletion resources are live. |
| web dashboard | launch | The production web dashboard is deployed with launch-off routes fail-closed. |
| mobile apps | beta | Release binaries exist, but App Store and Google Play approvals remain open. Complete physical-device acceptance and both store reviews before public release. |
| unified inbox | launch | Organization-scoped conversations, messages, status updates and human replies are implemented. |
| contacts | launch | Organization-scoped contacts, labels and lifecycle stages are implemented. |
| knowledge base | launch | Regional knowledge sources and agent retrieval are implemented. |
| ai agents | launch | Agent creation, configuration, activation and guarded tool execution are implemented. |
| analytics | launch | Production analytics endpoints and non-placeholder web/mobile views are implemented. |
| escalations | launch | Escalation assignment, conversation linkage and learning actions are implemented. |
| teams routing | launch | Organization teams, membership and routing controls are implemented with plan limits. |
| automations | launch | Supported workflow triggers/actions run through billed, idempotent queue execution. |
| billing | launch | Stripe collection, Lago metering and Masheev balance/entitlement logic are implemented. |
| audit log | launch | Organization security and operational audit events are customer-visible. |
| account deletion | launch | Authenticated account deletion and the public deletion instructions are implemented. |
| referrals | beta | Referral workflows are customer-visible but remain an early launch program. Complete production-safe attribution and reward reconciliation evidence. |
| sso | off | SAML/OIDC enterprise SSO is not implemented in the production application. Implement tenant configuration, enforcement, recovery and audit evidence before advertising it. |
| embedded chat | launch | Production embed Worker and signed widget sessions are available. |
| voice | launch | Twilio and ElevenLabs voice paths are implemented and production-configurable. |
| sms | launch | Twilio SMS inbound, outbound, suppression and delivery-state paths are implemented. |
| email | beta | Email is implemented but production provider evidence and review remain launch gates. Complete Gmail/Microsoft reviewer-safe production evidence. |
| whatsapp | beta | WhatsApp is implemented but Meta App Review and Masheev-ingestion evidence remain open. Complete Meta review and production inbox/webhook proof. |
| instagram | beta | Instagram messaging is implemented but Advanced Access and reviewer evidence remain open. Complete Meta review with a stable professional reviewer account. |
| google reviews | beta | Google Reviews is implemented but Business Profile eligibility and review remain open. Complete Google verification and reviewer-safe production evidence. |
| google calendar | beta | Calendar and Meet lifecycle actions are implemented while Google verification is pending. Complete external-user proof and Google Trust & Safety review. |
| microsoft calendar | beta | Calendar and Teams lifecycle actions are implemented while publisher verification is pending. Complete Entra publisher verification and reviewer-safe production evidence. |
| tableport | launch | TablePort OAuth and reservation actions are implemented with runtime health persistence. |
| twilio byok | launch | Organization-scoped Twilio credentials and phone-number paths are implemented. |
| voice cloning | off | Voice cloning processes a voiceprint-like biometric sample; consent today is the uploader's assertion, not the voice owner's written release. Collect and store the voice owner's written release, delete samples and clones on request and after 12 months unused, and publish the biometric retention policy (PRIVACY-13, AI-15). |
| elevenlabs byok | launch | Organization-scoped ElevenLabs credentials and voice paths are implemented. |
| public api | launch | API keys and supported public API routes are implemented. |
| transactional sms | off | Booking-scoped transactional SMS requires approved sender registration and transaction consent. Complete consent, STOP handling, provider registration and production delivery evidence before activation. |
| outgoing webhooks | off | Durable outgoing webhook delivery is not implemented for launch. Implement durable signed delivery, retries, DLQ recovery and production evidence. |
| rules | off | Legacy Rules CRUD has no evaluator and is fail-closed for launch. Implement and verify the evaluator before exposing or activating Rules. |
| surveys | off | Conversation surveys are not part of the launch product surface. Complete product, delivery and evidence paths before activation. |
| proactive start conversation | off | Proactive messaging lacks campaign-grade consent and quiet-hour controls. Enabling outbound AI voice or SMS also requires TCPA/AB 2905 and AI-disclosure legal review. Implement consent provenance, quiet hours and compliant delivery evidence. |
| outbound calling | off | Outbound AI calling is built behind consent, calling-window and opt-out controls but awaits launch gates. Counsel review (TCPA/TSR/PECR), TCPA/CIPA insurance, voice-provider determination, DNC/RND decision, live spikes S1+S3. |
| delayed workflow steps | off | Durable long-delay workflow execution is not implemented. Implement durable waits, retries and recovery before activation. |
| custom webhook integration | off | The generic custom webhook integration is not production-exposed. Complete region-aware signed inbound and durable outbound designs before exposure. |
| slack | off | Slack escalation notifications are not implemented for launch. Implement OAuth, notification delivery and revocation evidence. |
| shopify actions | off | No production Shopify adapter or customer action path exists. Implement, test and review before advertising availability. |
| stripe action tools | off | Stripe is the billing processor, not a customer-facing agent integration. Define and implement a scoped customer action integration before advertising it. |
| hubspot | off | HubSpot is roadmap-only and has no production adapter. Implement, test and review before advertising availability. |
| salesforce | off | Salesforce is roadmap-only and has no production adapter. Implement, test and review before advertising availability. |

## Before implementing

A schema or SDK type can exist for an unavailable capability. Check the account's
permissions and provider state before provisioning. Browser tools can call your
existing backend, but do not create native provider or unattended integrations.

Machine-readable: [capabilities.json](https://docs.masheev.com/capabilities.json).
Start with [Integrate with AI](https://docs.masheev.com/integrate.md).