Get back to the work that needs you

Set up Masheev

1. Sign in at app.masheev.com and create or select your workspace. You can set up and test straight away. We review new workspaces in the background, and channels go live once the review is complete.
2. Add an AI agent. Give it only approved business instructions, knowledge, and escalation rules.
3. Create an inbox for web chat, voice, or SMS. Provider-gated beta channels can be connected only when your account is eligible.
4. Send one production-safe test from an external device. Confirm that the message or call appears in the intended inbox and that a human can take over.
5. Review team access, business hours, recording settings, usage limits, and billing before inviting customers.

Do not use real customer personal data while testing. If you need help, include the workspace name, channel, time and timezone, visible error, and a sanitized screenshot.

Channels and inboxes

Web chat

Create a Chat inbox, assign an AI agent, then use the inbox embed instructions to add the widget to your website. Test on your real public origin and confirm that the conversation is visible only inside the correct workspace.

Voice and SMS

Connect or provision an approved Twilio number, then create the matching Voice or SMS inbox. Confirm country permissions, recording disclosure, opt-out handling, spending limits, and one external inbound and outbound test before customer use.

Email and social channels

Email, WhatsApp, Instagram, and Google Reviews are private betas. Availability depends on provider approval, account eligibility, and Masheev review. Do not promise a launch date or connect an unrelated customer asset for testing.

Integrations

1. Open your workspace settings and select Integrations.
2. Choose the provider and review the exact account, asset, and permissions before approving access.
3. Run one non-destructive test using the intended workspace and provider asset.
4. If the integration shows Invalid or Reconnect required, reconnect as an organization owner or admin who also controls the provider asset.

Never email an OAuth token, API key, password, or verification code to support. For a failed connection, send the provider name, timestamp, visible error, and workspace name.

Billing and cancellation

The pricing page is the current source for plan fees, included usage, and usage rates. In Masheev, open your workspace Billing page to review the plan, balance, invoices, top-ups, and payment state.

• Complete card authentication only inside the secure Masheev and Stripe checkout. Support will never ask for full card details or a verification code.
• If a payment fails, send the invoice reference, amount, currency, time, and visible error. Do not repeatedly retry while the payment state is uncertain.
• Turn off renewal at any time in Billing. Paid plan access continues until the confirmed paid-period end, with no routine prorated subscription refund. Trials and unpaid subscriptions end immediately on cancellation. Mandatory legal rights and expressly approved refunds remain available. If Billing is unavailable, email support from an owner address with the workspace name for help.
• Refunds and service credits follow the applicable order form and Terms of Service. They are reconciled against provider and billing records, not estimated manually.

Start from the Masheev workspace list, select the workspace, then open Billing.

Privacy and account deletion

Submit an access, correction, export, or deletion request through the privacy request page or email privacy@masheev.com. Masheev verifies identity and scope before acting.

To permanently delete your user account, follow the public account deletion instructions. Organization-owned customer data may be governed by the organization's instructions and agreement with Masheev.

Report a suspected vulnerability or unauthorized access privately to security@masheev.com. Do not include secrets or unnecessary customer data.

Incidents and delivery issues

1. Check the service status page before changing settings or reconnecting a provider.
2. For a message problem, record the Masheev message ID, provider ID if shown, channel, direction, timestamp, timezone, and final visible state.
3. Do not resend while delivery is unknown. The original may still arrive and create a duplicate.
4. For a permanent failure, keep the terminal state and contact support if the expected failed-delivery credit is not reflected.

If multiple workspaces are affected, money or messages may be duplicated or lost, or a credential may be compromised, stop making changes and contact support immediately.

Current availability

The following capabilities are implemented but remain private beta while production provider or store evidence is completed.

Not available at launch

These capabilities are intentionally unavailable. Masheev fails closed rather than presenting an unfinished workflow as successful.

Contact support

Email support@masheev.com. Include your workspace name, the affected channel or integration, the time and timezone, the exact visible error, and a sanitized screenshot if useful.

Never send passwords, login links, one-time codes, API keys, OAuth tokens, full payment details, identity documents, or unnecessary customer message content.