Reach a person
The chat on this site runs on Masheev. Ask it a question about the product.
Setup, channels, integrations and billing questions.
support@masheev.comAccess, deletion and other data requests.
privacy@masheev.comReport a vulnerability or a security concern.
security@masheev.comSet up Masheev
- 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.
- Add an AI agent. Give it only approved business instructions, knowledge, and escalation rules.
- Create an inbox for web chat, voice or SMS. WhatsApp, Instagram and Google Reviews can be connected once your account is approved.
- Send one test message or call from a different device. Check that it appears in the right inbox and that someone on your team can take over.
- Review team access, business hours, recording settings, usage limits, and billing before inviting customers.
Don’t use real customer details while testing. If you need help, include the workspace name, the channel, the time and timezone, the error you see, and a screenshot with personal details removed.
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 set up an approved Twilio number, then create the matching Voice or SMS inbox. Before customers use it, confirm country permissions, the recording notice, opt-out handling and spending limits, and run one test call or text in each direction from outside.
Email and social channels
WhatsApp, Instagram and Google Reviews are on request. Availability depends on approval from the provider, your account’s eligibility and our review. Please don’t promise customers a date, and don’t connect someone else’s account to test.
Integrations
- Open your workspace settings and select Integrations.
- Choose the provider and review the exact account, asset, and permissions before approving access.
- Run one non-destructive test using the intended workspace and provider asset.
- 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
- Check the service status page before changing settings or reconnecting a provider.
- For a message problem, record the Masheev message ID, provider ID if shown, channel, direction, timestamp, timezone, and final visible state.
- Do not resend while delivery is unknown. The original may still arrive and create a duplicate.
- 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
These are built, but each one needs an approval from a provider or an app store before it opens for your account.
Release binaries exist, but App Store and Google Play approvals remain open.
Before release: Complete physical-device acceptance and both store reviews before public release.
Email is implemented but production provider evidence and review remain launch gates.
Before release: Complete Gmail/Microsoft reviewer-safe production evidence.
WhatsApp is implemented but Meta App Review and Masheev-ingestion evidence remain open.
Before release: Complete Meta review and production inbox/webhook proof.
Instagram messaging is implemented but Advanced Access and reviewer evidence remain open.
Before release: Complete Meta review with a stable professional reviewer account.
Google Reviews is implemented but Business Profile eligibility and review remain open.
Before release: Complete Google verification and reviewer-safe production evidence.
Not available at launch
These capabilities are intentionally unavailable. Masheev would rather refuse than show an unfinished workflow as successful.
SAML/OIDC enterprise SSO is not implemented in the production application.
Before release: Implement tenant configuration, enforcement, recovery and audit evidence before advertising it.
Durable outgoing webhook delivery is not implemented for launch.
Before release: Implement durable signed delivery, retries, DLQ recovery and production evidence.
Legacy Rules CRUD has no evaluator and is fail-closed for launch.
Before release: Implement and verify the evaluator before exposing or activating Rules.
Conversation surveys are not part of the launch product surface.
Before release: Complete product, delivery and evidence paths before activation.
Contact support
Email support@masheev.com. Include your workspace name, the affected channel or integration, the time and timezone, the exact error you see, and a screenshot with personal details removed if it helps.
Never send passwords, login links, one-time codes, API keys, OAuth tokens, full payment details, identity documents, or unnecessary customer message content.