Akumina Developer Documentation

Akumina Developer Documentation

  • API
  • Docs
  • Blog

›AI

Akumina

  • Quickstart

Yo Akumina

  • Yo Akumina
  • Start with Yeoman
  • React
  • Simple template

Widget Builder

  • Widget Builder Structure
  • Akumina Widget Builder
  • Skipping instances
  • Token replacement for widget properties

Widget Development Quickstart

  • Setting up the Project
  • Configuring .env file
  • Configuring - akumina.sitedployer.config.json file
  • Configuring - akumina.config.json file
  • Extras

Widget Info

  • Akumina Widgets Overview
  • Building a New Widget Instance
  • Widget Views
  • Widget Properties
  • Global vs Local widgets (Widget Scoping)
  • Akumina React Widgets
  • Callbacks
  • RenderChildWidgets
  • Vendor Package List

Virtual Page Builder

  • Akumina Virtual Page Builder
  • Using Virtual Page Layouts
  • Creating a Custom Layout

Stream Card Builder

  • Installation
  • Stream Card Builder
  • Custom Cards
  • Activity Comments Config
  • Akumina Activity Stream PUSH Subscription using PowerAutomate to connect to ServiceNow
  • Akumina Activity Stream PUSH Subscription using PowerAutomate to connect to Dynamic 365

Site Deployer

  • Overview
  • Version 6.0
  • List Attribute Deployments
  • NPM Commands
  • SPA Updates and Deploying to multiple sites

Authoring

  • Content Action Event
  • Publish Validation Integration
  • Field Event Integration
  • CK Editor external plugins
  • Custom Components for Fields

AI

  • Akumina AI
  • Knowledge Buckets
  • Managed Prompts
  • Response Cards
  • FAQ

Headless

  • Quickstart
  • Headless Teams support
  • Headless Troubleshooting

Modern

  • Overview
  • FAQ
  • Single Page Application
  • Modern Web Part Library
  • Google Analytics for Modern Pages

Site Creator

  • Overview
  • Adding A Custom Site Definition
  • Core Step Classes
  • Custom Site Definition Components
  • Custom Site Definition XML
  • Custom Subsite Definitions
  • Sample Step Code
  • Supported Tokens

Azure DevOps

  • CI/CD using Azure DevOps
  • Setting up a build to deploy a site package
  • Setting up a build to deploy file to App Manager hosted in an app service

Configuration

  • Configuration Context Overview
  • Edit the Redis cache timeout
  • Using a key vault for the client id and client secret

Debugging

  • Debugging in Akumina

Advanced

  • Central Site Collection Support
  • Eventing OOB Digital Workplace Events
  • Working with custom JSX Views
  • Page Indexing

Service Hub

  • Quickstart

Patch Notes

  • Patch Notes

Managed Prompts

Managed Prompts

Managed Prompts allow organizations to create and manage predefined prompts that help employees get more consistent and useful responses from AI.

They can be presented to employees as suggested questions, or used behind the scenes to automatically translate common employee terminology into a more complete prompt.

Why Managed Prompts Matter

Employees do not always interact with AI using complete, descriptive questions. Many employees are accustomed to traditional search and may enter short phrases such as:

  • PTO
  • leave
  • VPN
  • expense report

While AI experiences work best when users provide more context, organizations should not have to rely entirely on changing employee behavior.

Managed Prompts provide a bridge between what the employee enters and what you want AI to understand.


Creating Managed Prompts

Managed Prompts should represent common questions or tasks that employees are likely to have.

For example:

Managed PromptExample Use Case
What is our PTO policy?Employee benefits
How do I submit an expense report?Travel and expenses
How do I connect to the VPN?IT support
Tell me about our parental leave policy.HR policies
Summarize the latest company news.Internal communications

Focus on employee intent, rather than simply creating prompts around system or content names.

For example, instead of:

IT Documentation

Consider prompts such as:

How do I reset my password?
How do I connect to the VPN?
How do I request a new laptop?

These better represent the questions employees are actually trying to answer.


Suggested Prompts

Managed Prompts can be exposed directly to employees as suggested questions.

This helps employees understand what they can ask while eliminating the need to construct the prompt themselves.

For example:

How can I help?

What is our PTO policy?
How do I submit an expense report?
How do I reset my password?
What company holidays are coming up?

Suggested prompts are particularly useful for introducing employees to an AI experience and encouraging adoption.


Auto-Resolving Managed Prompts

Managed Prompts can also be configured to automatically resolve based on keywords.

This is especially useful when employees continue to interact with AI as though they are using traditional search.

For example:

Employee enters:

leave

Managed Prompt:

Tell me about the company's leave policies.

The employee does not need to rewrite their question. The platform recognizes the configured keyword and executes the Managed Prompt instead.

Another Example

Employee InputAuto-Resolved Managed Prompt
PTOWhat is our PTO policy?
carryoverCan unused PTO be carried over to next year?
VPNHow do I connect to the corporate VPN?
expensesHow do I submit an expense report?

This allows organizations to support existing employee search behavior while gradually moving employees toward more conversational AI interactions.


Managed Prompts + Knowledge Buckets

Managed Prompts and Knowledge Buckets solve different parts of the AI experience and can be particularly powerful when used together.

Managed Prompts help determine what should be asked.

Knowledge Buckets help determine how and from where the question should be answered.

For example:

Employee enters:
carryover

↓

Managed Prompt resolves:
Can unused PTO be carried over to the next calendar year?

↓

Knowledge Bucket resolves:
Time Off & Leave

↓

AI responds using the appropriate curated documents, instructions, tools, and configuration.

This creates additional control without requiring the employee to understand how the AI experience is configured.


Keywords

Keywords can be associated with Managed Prompts to help recognize common employee terminology.

Good keywords represent terms employees are likely to actually enter.

For a Managed Prompt such as:

How do I connect to the corporate VPN?

Useful keywords might include:

  • VPN
  • remote access
  • connect from home

Avoid adding large numbers of unrelated or overly broad keywords. A keyword should provide a strong indication that the Managed Prompt represents the employee's intended question.


Best Practices

Start With Real Employee Questions

Create Managed Prompts around questions employees actually ask rather than around the structure of your intranet.

Avoid:
Human Resources

Better:
How do I update my benefits?

Keep Prompts Specific

A prompt should communicate enough context for AI to understand the intended task.

Avoid:
Time off

Better:
How much PTO can I carry over to next year?

Use Keywords Strategically

Keywords are most valuable for common shorthand, terminology, acronyms, and search behavior where the employee's intent is reasonably predictable.

Don't Try to Create a Prompt for Everything

Managed Prompts are most valuable for common, important, or predictable employee needs.

AI should still be able to handle open-ended questions that do not match a Managed Prompt.

Test the Employee Experience

Test both the full Managed Prompt and the short employee inputs that are expected to resolve to it.

The goal is not simply to verify that the Managed Prompt works—it is to verify that employees are being routed to it when expected.


Measuring Managed Prompt Adoption

Managed Prompts can also help organizations understand how employees are using AI.

The AI Adoption experience includes visibility into the most-used Managed Prompts, allowing administrators to see which curated experiences employees are selecting and using.

This information can help identify:

  • Which Managed Prompts provide the most value.
  • Which employee topics are generating the most interest.
  • Opportunities to create additional Managed Prompts.
  • Prompts or keywords that may need to be refined.

Managed Prompts should therefore be treated as something that can evolve with employee behavior rather than as a one-time configuration.


The Goal

Managed Prompts are not intended to replace natural conversations with AI.

They provide organizations with a way to guide the experience where guidance is valuable.

Employees can continue asking AI anything, while Managed Prompts provide a more controlled path for common and important use cases:

Employee language → Better prompt → Right AI experience → Better answer.

← Knowledge BucketsResponse Cards →
  • Why Managed Prompts Matter
  • Creating Managed Prompts
  • Suggested Prompts
  • Auto-Resolving Managed Prompts
    • Another Example
  • Keywords
    • Start With Real Employee Questions
    • Keep Prompts Specific
    • Use Keywords Strategically
    • Don't Try to Create a Prompt for Everything
    • Test the Employee Experience
  • The Goal
Akumina Developer Documentation
Docs
Akumina Framework 5.0Akumina Widget BuilderAkumina Yeoman GeneratorSite Deployer
Community
Akumina Community Site
More
GitHubStar
Copyright © 2026 Akumina