Skip to main content

Deway Admin - App Info for AI Assistant

This document provides context for the AI assistant to help users navigate the Deway Admin dashboard. It contains information that cannot be inferred from the UI alone.


Product Overview

Deway Admin is where you configure and monitor your autonomous adoption layer. The admin allows you to:

  • Train your AI agent with your product knowledge
  • Customize the chat widget appearance and behavior
  • Monitor chats between users and the AI
  • Define user goals (Jobs) to improve AI guidance
  • Manage your team and their access levels
  • Connect integrations with analytics and support tools

The sidebar contains these sections (top to bottom):

  1. Project Selector (top) — Switch between projects if you have multiple
  2. Dashboard — Analytics and metrics overview (Deway team only)
  3. Accounts — Account management (Deway team only)
  4. User Activity — Engagement metrics and trend charts
  5. User Sessions — Individual session replay with AI-generated summaries
  6. Chats — View chat history between users and AI
  7. Jobs — Define user goals the AI should help with
  8. Agent Look & Feel — Customize widget appearance
  9. Agent Training — Configure sensitive topic handling
  10. Knowledge Base — Manage documentation sources for AI
  11. Settings (bottom) — SDK setup, team, integrations, security

Feature Details

Dashboard

What it shows:

  • Total questions asked by users
  • Active users count and percentage
  • Average chats per engaged user
  • Trend charts for user engagement over time

Time range options:

  • Last 7 Days (default)
  • Last 30 Days
  • Custom date range

Empty state: If you see "No data yet", the SDK hasn't been integrated or no users have interacted yet. Check Settings > SDK Setup for integration instructions.

Tip: Hourly data is shown for shorter ranges; daily aggregates for longer ranges.


Jobs

Purpose: Jobs tell the AI what users are trying to accomplish. This helps the AI provide more relevant guidance instead of just answering questions.

Job fields:

FieldRequiredDescription
NameYesShort identifier (e.g., "Create First Project")
Job to be DoneYesNarrative description of the goal (e.g., "Help the user create their first project by guiding them through the project wizard")
AudienceYesWho this applies to (e.g., "New users in their first 7 days")

Best practices:

  • Start with 3-5 critical Jobs
  • Focus on onboarding, activation, and common support requests
  • Be specific about outcomes, not actions

Example Jobs:

  • "Complete Profile Setup" → For new users who haven't filled their profile
  • "Connect First Integration" → For users who haven't connected any tools
  • "Export First Report" → For users who haven't used the export feature

User Activity

What you'll see:

  • Total questions asked by users
  • Active users count and engagement percentage
  • Average chats per engaged user
  • Trend charts for "Users with Questions" and "Active Users" over time
  • Time range selector (last 24h, 7 days, 30 days, custom)

User Sessions

What you'll see:

  • Table of individual user sessions with AI-generated titles
  • Session duration, event count, and flow outcome badges
  • Filters for user ID, time range, duration, event count, and bot/dev traffic

Session details (click to expand):

  • AI-generated TL;DR and summary
  • Chronological business events with parameters
  • Flow outcomes: Completed, Mistakes, Dropped-Off

Chats

What you'll see:

  • List of all chat sessions between users and your AI
  • User info (ID, name, email if identified)
  • Message count, topic, page paths, and timestamps
  • Full message history when you click a chat

Message details:

  • Actor: Either "user" or "assistant"
  • Citations: For assistant messages, shows which Knowledge Base sources were used
  • Intent: What the AI detected the user was trying to do
  • Topic: Current conversation topic
  • Page: Which page the user was on

Using chats to improve:

  1. Look for unanswered questions → Add to Knowledge Base
  2. Look for repeated goals → Create new Jobs
  3. Look for frustration → Add Sensitive Topics

Agent Look & Feel

Widget appearance modes:

  • Bubble - Floating circular button (typically bottom-right)
  • Bookmark - Fixed tab on the side of the screen

Theme configuration:

The theme has light and dark mode variants. Each mode configures:

CategoryProperties
Accentbase, hover, active, muted, subtle
Surfacebase, elevated, secondary, tertiary, inset
Textprimary, secondary, tertiary, disabled
Bordersubtle, light, medium, strong

Color formats: #RGB, #RRGGBB, or #RRGGBBAA (with alpha)

Typography:

  • Base font: For body text (e.g., "Inter, system-ui, sans-serif")
  • Mono font: For code blocks (e.g., "JetBrains Mono, monospace")

Copywriting options:

FieldPurpose
Assistant NameDisplay name shown to users
AI DisclaimerMessage shown before chat starts
Thinking MessagesShown while AI is processing (rotates if multiple)
Welcome TitleGreeting headline when chat opens
Welcome SubtitleSecondary greeting text
Prompt SuggestionsUp to 4 starter questions shown to users

Support Handoff:

  • URL mode: Opens a link (e.g., your support page)
  • Selector mode: Clicks a DOM element (e.g., #intercom-launcher to open Intercom)

Developer settings:

  • Development Mode: Enables verbose console logging
  • Auto-show: Widget opens automatically on page load
  • User Allowlist: Restrict SDK to specific user IDs (empty = all users)

Custom icons:

  • Must be inline SVG markup
  • XSS protection is enforced
  • Widget icon size: 18-36 pixels

Agent Training

What you can configure: Sensitive Topics — categories of user messages that need special handling.

Built-in topics (always active, cannot be modified):

  1. Malicious Content — Blocks illegal, harmful, and prompt injection attempts. Reaction: Refuse to Answer.
  2. Human Handoff Request — Detects when users explicitly ask for a human. Reaction: Handoff to Support.

Custom topics you can add:

  • Pricing/Billing questions → handoff-to-support
  • Legal/compliance questions → refuse-to-answer
  • Competitor comparisons → refuse-to-answer

Each custom topic has:

  • Title — Short name
  • Description — What triggers this topic
  • ReactionRefuse to Answer or Handoff to Support
  • Custom Agent Response — Optional override for the default message
  • Examples — Up to 10 positive/negative training examples

Reactions:

  • Refuse to Answer: AI politely declines
  • Handoff to Support: AI offers to connect with human support

Training examples:

  • Positive case: Should trigger the topic (e.g., "Can I get a discount?")
  • Negative case: Should NOT trigger (e.g., "What's included in the Pro plan?")

Copy to another Project: Copies all training config to another project in your tenant.


Knowledge Base

Purpose: Add your documentation so the AI can answer product questions accurately.

Two types of data sources:

  • Web Scrape — Documentation websites crawled by the Deway team during onboarding
  • Manual — PDF files you upload directly (max 5 MB)

Data sources table shows:

  • Source (URL or filename)
  • Type (Web Scrape or Manual)
  • Status (Syncing, Completed, Failed)
  • Document count
  • Last updated

Uploading PDF files:

  1. Click Upload File
  2. Drag and drop a PDF or click to browse
  3. Processing starts immediately

Best practices:

  • Ensure your main documentation is indexed
  • Upload supplemental PDFs for internal docs not available on a public URL
  • Contact the Deway team to add or update web scrape sources

Settings

SDK Setup

Shows your App Key and integration instructions. The App Key is required for Deway.init().

Connection status:

  • Live: SDK connected and sending events
  • No Events: SDK installed but no recent activity
  • Error: Connection issue (check App Key, network)

Team Management

Roles:

RolePermissions
AdminFull access - manage team, billing, all settings
WriteCreate and modify content - Jobs, Training, Knowledge Base
ReadView-only access - see analytics and chats

Inviting members:

  1. Click "Invite Member"
  2. Enter email address
  3. Select role
  4. Click Invite

Notes:

  • Invited users authenticate via your organization's SSO
  • Email domain must match your organization
  • Recent invitations (< 1 hour) are marked

Integrations

Currently supported with configuration:

  • Mixpanel - Token + Region (US/EU)
  • Amplitude - API Key + Data Location (US/EU)
  • Segment - Write Key + Region (US/EU)

Display-only integrations (coming soon):

  • Google Analytics
  • HubSpot
  • Slack
  • Webhooks
  • Woopra

Data residency: Choose US or EU based on your compliance requirements.

Security

User Allowlist:

  • Empty list = all users can use the SDK
  • Add specific user IDs to restrict access
  • Useful for beta testing or staged rollouts
  • Comma-separated list of user IDs

Multi-App Support

If your organization has multiple products:

  • Use the app selector in the sidebar to switch
  • Each app has its own:
    • Jobs
    • Knowledge Base
    • Chats
    • Theme configuration
    • Integrations
  • Team members are shared across apps

Common Workflows

Setting up a new app

  1. Go to Agent Training → Set Core Identity
  2. Go to Agent Training → Add App Info with product details
  3. Go to Knowledge Base → Add your documentation URL
  4. Go to Agent Look & Feel → Customize theme to match brand
  5. Go to Settings > SDK Setup → Copy integration code
  6. Install SDK in your application
  7. Go to Dashboard → Verify events are flowing

Improving AI responses

  1. Go to Chats → Find poor responses
  2. Identify the gap:
    • Missing knowledge? → Add to Knowledge Base
    • Wrong tone? → Update Tone of Voice
    • Missing context? → Add to App Info
    • Sensitive topic? → Add to Sensitive Topics
  3. Test by asking similar questions

Onboarding team members

  1. Go to Settings > Team
  2. Click "Invite Member"
  3. Choose appropriate role:
    • Admins: For those who manage the product
    • Writers: For content managers
    • Readers: For stakeholders who just need visibility

Troubleshooting

"No data" on Dashboard

  • SDK not installed → Check Settings > SDK Setup
  • SDK not initialized → Verify Deway.init() is called
  • Users not identified → Ensure Deway.identify() is called

AI gives wrong answers

  • Check if relevant docs are in Knowledge Base
  • Verify sync completed successfully
  • Add more context to App Info
  • Check if include/exclude patterns are too restrictive

Theme changes not appearing

  • Save changes in Look & Feel
  • Hard refresh the page where SDK is installed
  • Check browser cache
  • Verify correct app is selected

Team member can't log in

  • Verify email domain matches organization
  • Check SSO configuration with IT
  • Resend invitation if expired
  • Ensure invitation was accepted

Key Terminology

TermDefinition
TenantYour organization/company
AppA product or application within your tenant
App KeyUnique identifier for SDK initialization
JobA user goal the AI should help accomplish
Data SourceA documentation URL indexed for AI knowledge
Prompt PartsConfiguration that shapes AI personality and knowledge
Sensitive TopicA subject requiring special handling (refuse or handoff)
SyncThe process of crawling and indexing documentation
CitationReference to Knowledge Base source used in an answer