Welcome to the
Help Center.

Evnao is AI customer-support software with a website widget, shared inbox, tickets, owner-approved Knowledge, human handoff, supported channels, and controlled Pro integrations.

Evnao sends the customer message and selected Knowledge context to the configured Google, NVIDIA NIM, OpenAI, or Anthropic provider. Processing and retention follow that provider and contract; Evnao does not promise universal provider-side Zero Data Retention.

The model can respond in multiple languages, but Evnao does not claim flawless native support for a fixed number of languages. The authenticated dashboard is currently English-first.

No. Evnao operates the managed AI runtime and applies the workspace plan limits. Customer workspaces do not upload provider API keys or select a private model endpoint.

Owners can publish articles, crawl a bounded website, resync a source, or upload supported text, PDF, and DOCX files. Native Zendesk, Intercom, and Notion synchronization is not live.

The dashboard accepts PDF, DOCX, TXT, Markdown, CSV, JSON, and HTML within enforced request and extraction limits. There is no public REST upload API today.

Evnao uses an advanced RAG (Retrieval-Augmented Generation) pipeline. By default, the AI is strictly instructed to only answer questions using the context provided in your Knowledge Base. If the answer doesn't exist, it is programmed to say 'I don't know' and route the conversation to a human.

Only through a Pro connected HTTPS action configured by the workspace owner. The standard widget does not accept trusted Stripe or order metadata from the browser.

Human agents use the Evnao 'Team Inbox'. When the AI routes a ticket, the agent sees the full chat history, a concise AI-generated summary of the problem, and the customer's intent. The agent takes over with full context.

A Pro owner can configure a connected POST action. Every write request waits for owner or admin approval and executes with an idempotency key. Evnao does not include a native refund provider today.

A customer can ask for a human and an agent can take ownership. The AI also avoids unsupported answers and can escalate. Configurable sentiment rules are not live today.

Teams and departments exist, and agents can be assigned. A full automatic routing-rule engine is not live today.

Install the provided script, configure allowed domains, publish the site, and run dashboard verification. There is no published React component package.

Yes. Pro workspaces can create HTTPS endpoints for supported Evnao events. Deliveries are signed with HMAC SHA-256, queued durably, retried with backoff, and visible in the developer settings.

Yes. Public API keys and customer-facing endpoints use scoped server-side limits. Evnao does not promise a universal 1,000 requests per minute; limits depend on the endpoint and plan.

Evnao implements tenant scoping, encrypted integration credentials, signed webhooks, MFA, hashed visitor capabilities, rate limits, and SSRF defenses. It is not currently represented as SOC 2 certified or HIPAA compliant, and it does not guarantee automatic removal of every PII type.

Evnao connects through Meta's Facebook Login bridge. You need an Instagram Professional account (Business or Creator) linked to a published Facebook Page where you have Full Control. Open Settings → Channels → Instagram → 'Launch Setup Wizard' for a step-by-step interactive walkthrough.

This error occurs when you run a Page-level operation (like subscribing webhooks or sending messages) with a personal User token or System User token. Switch the 'User or Page' selector in Graph API Explorer to your Facebook Page, confirm GET /me returns your Page ID, and retry.

User tokens created in Graph API Explorer expire in 1-2 hours by default. You must extend your User token to a 60-day token using Meta's Access Token Debugger, then run GET /me/accounts with that extended token to extract a permanent Page Access Token with 'Expires: Never'.

In your Meta Developer App, navigate to Use Cases → Add Use Case → 'Engage with customers on Messenger from Meta' and enable the pages_messaging permission. Reauthorize your token in Graph API Explorer, derive a fresh Page token, and resubscribe.

In Graph API Explorer, run GET /me/accounts?fields=id,name,access_token,instagram_business_account{id,username,name}. Your Instagram Account ID is the numeric value under data[].instagram_business_account.id (typically starting with 178414...).

Never identify Pages by name alone. In the GET /me/accounts response, look for the Page object where instagram_business_account.username matches your exact Instagram handle, and copy that specific numeric Page ID.

Meta requires an exact string match for the Verify Token. In Evnao, generate a secure Verify Token and paste the identical string into Meta's Webhook configuration. Ensure there are no leading/trailing spaces and that your Evnao workspace is saved.

While in Development mode, add your test Instagram account as an 'Instagram Tester' under Meta App → Roles. The test account must log into Instagram and accept the invite under Settings → Apps and Websites → Tester Invites before sending test DMs.

If a team member replies to a customer directly from the Instagram mobile app, Meta Business Suite, or the Evnao Inbox, Evnao detects the human echo event, records the message in Inbox, and immediately switches the conversation to HUMAN mode to pause AI auto-replies.

Evnao focuses primarily on high-intent customer support Direct Messages. Story replies and direct text DMs are ingested automatically. Dedicated public comment management can be routed to human queues.