Answer Slack Team Questions

WorkSpace is a chat window on steroids. It's a place where you can add new concepts and facts to your knowledge graph using conversational English and simple forms. It's also a place where you and your team can collaborate by recording suggestions and comments against these concepts.

WorkSpace has visual tools that let you see the shape of your emerging knowledge graph and it maintains a conversational audit trail of who changed what.

Your customers hang out in Messenger, WhatsApp^*, Telegram and Discord. KayBot gives you a presence in each of these consumer messaging channels.

You can also embed a simple chat widget script to put KayBot into your own corporate, customer support and forum sites and onto your pages at partner sites.

* Coming soon

A query is any question or comment from a user in any connected chat device or in any Consumer or Enterprise channel. A request made using Graph Workspace or the REST API is also a query. Query counts are collected from all graphs that have been run during the month and then totalled.

Running your knowledge graphs "on-demand" is how we keep your costs down. It's a strategy that some call "serverless" computing. When a query arrives at your on demand graph, the graph is started to service that query. The graph then stays running while it's getting queries, and for a few more minutes after the last query is received.

Each graph runs on its own isolated graph database, so it can take a few seconds to start. However, it's usually less than the time it would take a human to type a response.

For Business and Enterprise plans, time-critical and high-use graphs can be set to "always on" in the KayBot Control Panel.

Yes you can. The Graphs Control Panel gives you comprehensive control over your account, its subscription plan and your graphs. Your plan may place some resource constraints on your graphs, but within those constraints you can control their resource footprint, their integrations and many other properties. For more detail see the FactNexus EKG Graphs Control Panel Reference.

Very. Your knowledge and data are encrypted at rest, and in transit. Enterprise users even get to control the key used for that encryption.

There are no multi-tenancy risks to your in-memory and working knowledge either. Each of your graphs runs on its own isolated graph database.

To register for an Essentials, Specialist, Workplace, Team, Business or Enterprise plan, first register for a Free Trial.

When you're ready, you can choose your plan by clicking Change Plan in the Account Details tab of your Graphs Control Panel.

Enterprise plan CPU-minutes, Workspace users and queries are paid for using KayBot Credits. An Enterprise plan includes 500 credits per month. This is enough to cover the KayBot resource needs of most enterprises. Credits that aren't used are accumulated for the next billing period and, if needed, more can be bought either manually or automatically.

It's a subscription strategy that gives you predictable costs and no risk of "bill shock".

Yes. You can build, modify and get answers from your graphs - and integrate them with other applications - using the  EKG REST API.

What's more, the API hides the structural complexity inherent in any knowledge graph by providing simple abstractions - Concepts, Facts and Cards.

KayBot can "bulk load" existing data into your knowledge graph. The product list from your WooCommerce, Squarespace, Shopify or other e-commerce store for example. Or the tags, titles and URLs of the articles or snippets from your Wordpress, Wix, Zendesk, Confluence or other Knowledge Base.

Prepare the table as a CSV (Comma Separated Value) file, then ingest it from your Graph Control Panel. Alternatively you can POST it using the REST API. For more detail see the FactNexus EKG Table-to-Graph API Reference.

Yes. KayBot understands the semantics of a user's "I want to talk to a human" request and will take them to the relevant "handover" concept. It's then one click to connect with the live chat framework of your choice.

KayBot is a powerful Knowledge Agent, but she's not designed for building procedural chatbot pathways. She does, however, have the semantic prowess to understand a user's intent.

To connect with your existing agent, you create a knowledge graph concept for each intent your procedural agent handles. Using a strategy we call "Intent Handover", KayBot infers your user's intent then directs them to your bot via that concept.

See it working - ask KayBot something like "Why is my messenger integration not working?"

Alternatively, you can use the REST API to collect responses from KayBot and pipe them through your existing bot framework.

First up, ask KayBot. If KayBot can't locate a concept that answers your question, she'll point you to the community forum or connect you with a live agent.