Help Center

Answers, support lanes, and product guidance in one place.

Browse common questions about agents, knowledge files, billing, security, widgets, and workspace setup. If you need a person, use the right support email below.

Getting started

What is Aris888 AI?

Aris888 AI is a no-code platform for building and deploying governed AI agents with model routing, knowledge grounding, quality controls, analytics, and embeddable widgets.

Do I need engineers to launch an agent?

No. Admins can create agents, upload knowledge, configure behavior, and embed widgets from the dashboard. Engineering is only needed for advanced integrations or custom infrastructure.

What should I prepare before a demo?

Bring your target use case, example questions, a few source documents, deployment channel, success criteria, and any governance requirements such as audit, approvals, or data retention.

Can I test multiple use cases?

Yes. You can create separate agents for different audiences, workflows, languages, and knowledge scopes so each assistant can be evaluated independently.

Agents

What kinds of agents can I build?

Common examples include citizen service assistants, HR policy guides, legal intake helpers, finance explainers, support triage assistants, and internal knowledge concierges.

Can agents use different models?

Yes. The platform is designed around routing and provider flexibility, so teams can choose model behavior based on cost, quality, latency, or deployment policy.

How do I control agent tone and rules?

Use agent instructions, answer policies, knowledge scope, refusal behavior, and quality gates to shape how each agent responds.

Can I run agents in more than one language?

Yes. Agents can support multilingual workflows when their instructions, source content, and user-facing widget copy are configured for the target audiences.

Knowledge and answers

What files can I use as knowledge?

Teams commonly upload policies, manuals, FAQs, service guides, legal templates, HR documents, financial instructions, and operational playbooks.

How do agents stay grounded?

Agents answer from assigned knowledge sources and configured rules. For sensitive flows, teams can require citations, refusals, or escalation when confidence is low.

Can I update knowledge after launch?

Yes. Knowledge can be refreshed as policies and workflows change, then tested before relying on it in a public-facing channel.

What if an answer is wrong?

Use analytics, conversation review, source updates, instructions, and quality rules to correct behavior. For urgent issues, contact support with the agent name and example prompt.

Website widget

How do I add the widget to a website?

The widget is designed for one-script deployment. Configure branding and behavior in the dashboard, then place the generated embed snippet on the target site.

Can the widget match our brand?

Yes. You can align colors, welcome text, launcher behavior, and interface preferences so the assistant feels native to your site.

Can I disable the widget temporarily?

Yes. Teams can pause deployment or remove the embed while updating behavior, content, or compliance settings.

Does the widget work on mobile?

The widget and marketing pages are designed with responsive layouts. For production use, test the embed on the actual target pages and devices.

Billing and plans

How does pricing work?

Starter is free, Pro is $40/month, and Enterprise is $100/month. See the Pricing page for plan limits and upgrade paths.

What counts toward usage?

Usage usually depends on agents, monthly query volume, knowledge limits, model costs, and enterprise requirements. Exact rules can vary by plan.

Can we upgrade later?

Yes. Teams can start small, prove a use case, and move to Pro or Enterprise when usage, governance, or infrastructure needs grow.

Who handles billing questions?

Email [email protected] for procurement and plan questions, or [email protected] for account-level billing issues.

Security, privacy, and access

Where should I report a vulnerability?

Email [email protected] with clear reproduction steps, affected surfaces, severity, and contact details. Avoid public disclosure until the issue is triaged.

Can Enterprise customers request private deployment?

Yes. Enterprise discussions can include private LLM deployment, dedicated infrastructure, SSO/SAML, SLAs, audit exports, and custom governance.

How do I ask about privacy rights?

Email [email protected] with the request type and the account or organization context needed to locate the relevant data.

What should support tickets include?

Include workspace name, agent name, widget URL if relevant, screenshot or prompt, expected behavior, actual behavior, browser, and urgency.

Escalation

When the issue is urgent, send sharper context.

For outages, security reports, blocked launches, or customer-facing errors, include impact, affected users, timestamps, URLs, agent names, and reproduction steps.