2705 Page Level Ai
Page-Level AI
Introduction
Page Assistants
What are Page Assistants?
Capabilities
- Answer Questions - About data displayed on the page
- Provide Guidance - Help users understand how to use features
- Explain Data - Clarify what information means
- Suggest Actions - Recommend next steps based on context
- Navigate Users - Guide to relevant sections
- Generate Content - Create content based on page data
Setting Up Page Assistants
Step 1: Enable Page Assistant
- Go to Page Settings
- Enable "AI Assistant"
- Choose assistant appearance (floating button, sidebar, embedded)
Step 2: Configure Context
- Define what data assistant can access
- Set page context and purpose
- Configure available actions
Step 3: Write System Prompt
Define assistant behavior and capabilities.
Example 1: Dashboard Assistant
System Prompt:
You are a helpful business intelligence assistant. You can see the following dashboard data:
- Total Revenue: ${Total Revenue}
- Revenue Growth: {Growth Percentage}%
- New Customers: {New Customer Count}
- Customer Churn: {Churn Percentage}%
- Top Products: {Top 5 Products}
- Regional Performance: {Region Data}
Answer questions about this data, provide insights, and explain trends. Keep responses concise and business-focused. If asked about data not on this dashboard, say you can only see current dashboard metrics.
Example Interactions:
- User: "Why did revenue grow this month?"
- AI: "Revenue grew 15% primarily due to increased sales in the Electronics category ($45K) and strong performance in the West region (+22%)."
- User: "Should I be concerned about the churn rate?"
- AI: "The 3.2% churn rate is slightly above your target of 3%. Consider focusing on customer retention in segments with highest churn, particularly accounts under $1000 monthly value."
Example 2: Form Helper Assistant
System Prompt:
You are a helpful form assistant. You're helping users complete a project proposal form.
The form includes:
- Project Title
- Description
- Budget Requirements
- Timeline
- Team Members
- Success Metrics
Help users by:
- Explaining what information is needed for each field
- Providing examples when asked
- Suggesting content when users are stuck
- Validating that required information is included
- Answering questions about submission requirements
Current form state:
{Current Field Values}
Be encouraging and helpful. Keep responses brief.
Example Interactions:
- User: "What should I put for success metrics?"
- AI: "Success metrics should be specific, measurable goals. For example: 'Reduce processing time by 30%' or 'Increase customer satisfaction score to 4.5/5'. What outcomes are you hoping to achieve?"
Example 3: Data Explorer Assistant
System Prompt:
You are a data assistant helping users explore customer data. You can see:
{Visible Records on Page}
Total Records: {Total Record Count}
Applied Filters: {Current Filters}
Help users by:
- Answering questions about visible data
- Suggesting useful filters or views
- Identifying patterns and trends
- Explaining outliers
- Recommending actions based on data
Be analytical but conversational.
Example Interactions:
- User: "Show me customers at risk of churning"
- AI: "I'll help you find at-risk customers. Try filtering for: No orders in 90+ days, Support tickets > 3, and Customer satisfaction
Smart Search
What is Smart Search?
Capabilities
- Natural Language Queries - "customers who haven't ordered recently"
- Semantic Understanding - Understands meaning, not just keywords
- Synonym Handling - "purchase" finds "order", "buy", "transaction"
- Context Awareness - Understands field relationships
- Intent Detection - Figures out what user is looking for
- Smart Suggestions - Recommends related searches
Traditional vs Smart Search
Traditional Search:
- User types: "urgent orders"
- Searches for exact text "urgent orders"
- Might miss orders marked "high priority" or "rush"
Smart Search:
- User types: "urgent orders"
- AI understands: looking for time-sensitive orders
- Finds: Priority="High", Rush="Yes", Requested Date=Soon
- Returns: All urgent orders regardless of exact wording
Setting Up Smart Search
Step 1: Enable Smart Search
- Go to Page Settings
- Find Search Configuration
- Enable "AI-Powered Search"
Step 2: Configure Search Scope
- Select which fields AI can search
- Define search context
- Set result formatting
Step 3: Define Semantic Context
This search covers customer records with these fields:
- Company Name
- Industry
- Status (Active, Inactive, Pending)
- Revenue (annual)
- Last Order Date
- Priority (High, Medium, Low)
Understand queries like:
- "big customers" = Revenue > $100k
- "inactive" = No orders in 90+ days or Status = Inactive
- "tech companies" = Industry contains technology-related terms
- "VIP" or "important" = Priority = High or Revenue > $250k
Return relevant results even if exact terms don't match.
Example Queries
Query: "Show me customers we haven't contacted recently"
AI Interpretation: Looking for customers with no recent interactions
Filter Applied: Last Contact Date > 60 days ago
Results: Displays customers matching criteria with last contact date highlighted
Query: "Healthcare clients in the Northeast"
AI Interpretation: Looking for industry="Healthcare" AND region="Northeast"
Also Finds: Industry="Medical", "Hospital", "Healthcare Services", etc.
Region: NY, NJ, MA, CT, etc.
Query: "Problematic orders this week"
AI Interpretation: Issues with recent orders
Looks For: Status="Problem", "Delayed", "Error" OR Support Tickets > 0
Timeframe: This week
Contextual Help Systems
What is Contextual Help?
Types of Contextual Help
- Field-Level Help - Explains what specific fields mean
- Task Guidance - Step-by-step help for current task
- Troubleshooting - AI helps diagnose and fix issues
- Best Practices - Suggests optimal ways to complete tasks
- Learning Hints - Progressive education as users work
Example: Adaptive Onboarding
Implementation:
You are an onboarding assistant helping new users learn the system.
Current Page: {Page Name}
User Progress: {Completed Steps}
User Role: {User Role}
Provide:
- Brief explanation of current page purpose
- What user can do here
- Suggested first actions
- Tips relevant to their role
- Links to related pages
Adapt help to user's experience level. Be encouraging and concise.
Dynamic Help Content:
- First Visit: Detailed explanation and walkthrough
- Return Visits: Quick tips and shortcuts
- Advanced Use: Power user features and optimization
Page-Level AI Prompts
What are Page-Level AI Prompts?
Use Cases
- Data Analysis: "What patterns do you see in this data?"
- Summarization: "Summarize the key points from all these records"
- Comparison: "Compare the top 5 performers"
- Anomaly Detection: "Are there any unusual values?"
- Action Recommendation: "What should I focus on first?"
Example: Sales Pipeline Analysis
Page Context:
Visible Data: {List of Opportunities with Status, Value, Close Date, Owner}
Total Pipeline Value: ${Pipeline Total}
Number of Opportunities: {Count}
Average Deal Size: ${Average}
Current Filters: {Active Filters}
Sample Questions:
"Which deals are most likely to close this month?"
AI Analyzes: Close dates, stages, deal sizes, historical patterns
Response: Provides list with reasoning
"Why is the pipeline smaller than last month?"
AI Analyzes: Current vs historical data
Response: "Pipeline value is down 15% primarily because 3 large deals ($150K total) closed last month, and new deals added this month are smaller. You have 12 new opportunities but average $8K vs $15K last month."
Advanced Page AI Techniques
Multi-Page Context
Example:
- User asks about customer on list page
- Navigates to customer detail page
- AI maintains conversation context
- Can refer back to previous pages
Proactive Insights
Example:
- User opens dashboard
- AI notices significant change in metrics
- Proactively shows: "Revenue jumped 25% yesterday, primarily from Enterprise segment"
Guided Workflows
Example:
- User starts complex task
- AI explains each step
- Validates completion before proceeding
- Provides tips and warnings
- Celebrates completion
Adaptive UI
Example:
AI notices: "You frequently filter for high-priority items. Would you like me to add a quick filter button?"
Page AI Best Practices
User Experience
- Non-Intrusive: Don't interrupt user flow
- Easy to Dismiss: Users can ignore AI if not needed
- Clear Attribution: Show it's AI, not human support
- Persistent: Assistant available but not obtrusive
- Contextual: Only show relevant help
- Progressive: More help for beginners, less for experts
Privacy & Security
- Respect Permissions: AI only accesses data user can see
- No Data Leakage: Don't expose restricted information
- Audit Trail: Log AI interactions for compliance
- User Control: Let users disable AI features
- Transparency: Clear about what AI can and can't do
Performance
- Lazy Loading: Load AI only when needed
- Caching: Cache common responses
- Async Processing: Don't block page load
- Scope Limiting: Only provide necessary context
- Resource Management: Monitor AI usage impact
Implementation Checklist
Planning
- Identify pages that would benefit from AI
- Define what assistance users need
- Map out available context
- Plan assistant personality and tone
- Consider user roles and needs
Implementation
- Write clear system prompts
- Configure context correctly
- Set up appropriate triggers
- Design intuitive UI
- Test with real users
Optimization
- Monitor usage patterns
- Collect user feedback
- Refine prompts based on interactions
- Optimize performance
- Expand to more pages
Next Steps
Next: AI Prompt Engineering - Writing Effective Prompts
Hands-On Exercise (To Be Added)
Exercise placeholders will include practical activities such as:
- Setting up a page assistant for a dashboard
- Configuring smart search for natural language queries
- Creating contextual help for a complex form
- Testing different assistant personalities and tones
Knowledge Check (To Be Added)
Quiz questions will test understanding of:
- Differences between page assistants and component AI
- Best use cases for smart search
- Contextual help implementation strategies
- Privacy and security considerations
We'd love to hear your feedback.