Frequently asked Questions.

GladFox is an AI coworker deployed under your own brand, so your employees can ask it questions and get real work done without needing to know anything about AI. It's a chat interface, connected to your company's own documents, systems, and workflows — the goal is for it to feel like pinging a knowledgeable coworker, not like using a generic AI assistant that happens to be pointed at your files.

General AI access is already in most employees' hands — it's not the differentiator. What a generic AI assistant fundamentally can't securely access is your company's specific data: your internal jargon, onboarding process, policies, systems, and customer information. GladFox is the AI your team already sort of uses, except it actually knows how things work at your company.

It's built for the whole company, especially the employees who'd never otherwise reach for an AI tool at all — no prompting skill required, they just ask like they'd ask a coworker. It's also useful for employees who are already comfortable with AI tools, since GladFox answers company-specific questions faster and more reliably than driving a general tool themselves.

Both. The same chat widget can be pointed outward, deployed on your own customer-facing site with a knowledge base curated for customers instead of staff. It's the same underlying technology, just aimed at a different audience, whenever you're ready for that.

Anything that's grounded in what your company knows — policy questions ("what does our refund policy actually say?"), process questions ("how does our warranty handle this?"), and lookups against your own systems ("which accounts ordered X but never Y?"). Take a look at the live demo for a concrete, unscripted example.

Seconds, not the time it takes to dig through a wiki, a shared drive, or wait on a coworker to reply. Because GladFox reads from a curated, pre-loaded knowledge base instead of searching the open web, it isn't spending time hunting for the right source — it already has it, and answers directly from it.

No new app to learn. It's a familiar chat box available in web chat and inside Microsoft Teams, wherever your team already spends their day. It can also be embedded directly on your own intranet or portal page.

It's deployed under your own name, colors, and logo. Your employees see your company's assistant — GladFox is the engine underneath, not something they need to know about unless you want them to.

It runs on a curated knowledge base built specifically from your own documents, onboarding material, and internal processes — not generic knowledge repeated back at you. Someone at your company (or GladFox on your behalf) puts that knowledge base together, and it keeps getting updated as your policies, systems, and hires change, so it doesn't go stale.

Yes — it's built to connect to what you already run rather than forcing you onto a different stack, whether that's your own database technology, your ticketing system, or your internal APIs. Every new connection GladFox supports goes through the same careful integration process, so the assistant works with your actual tools instead of a generic substitute.

Yes. Beyond answering questions, GladFox can take action on your behalf — kicking off a workflow, drafting an email template, filling out a form, generating a report or document. Those actions connect to the same systems your knowledge base already draws from, so the work happens without an employee needing to track down the right tool or the right steps themselves.

That's something we configure together during setup. Low-risk, informational actions can run on their own; anything with a real external effect — sending something, submitting a form, kicking off a workflow — is scoped to what you're comfortable having GladFox do outright versus what should go through a person first.

It's built to only answer from what your company's knowledge base actually says (plus closely related general professional knowledge), rather than guessing. If something's out of scope, it says so briefly and points to what it can help with instead. A simple thumbs up/down on every answer feeds back into what your knowledge base needs to cover next.

Every employee only sees what they're already allowed to see — access follows your own existing permissions rather than opening everything up to everyone.

No. Messages are processed by the underlying AI provider strictly as a service to power your responses — not used to train their models. Your company's own private deployment is covered by a services agreement with its own data-handling terms, separate from the general privacy policy that covers this public website and its live demo — see that policy for how the public demo specifically handles information.

By default, only an anonymized signal is kept — a general topic category and a thumbs up/down — with no verbatim question or answer text stored, specifically so employees can ask "dumb" questions without worrying they're being tracked or judged. The only time full conversation text is ever saved is if an employee explicitly opts in through a clearly labeled "help this improve" action, so a reviewer can see what went wrong — never as a silent default.

No. GladFox manages the underlying AI provider account on your behalf as part of the platform — you don't need to set up, manage, or pay a separate AI vendor directly.

No. GladFox is powered by Claude by default, but the platform is built with a provider-abstraction layer so a different LLM can be swapped in per client where preference, cost, or procurement requires it.

A flat platform subscription, plus a transparent, at-cost pass-through of the AI usage your team actually generates. It's priced against what the realistic alternative would cost you — giving every employee their own individual AI access — not as a per-seat AI license.

Yes, generally by a wide margin. GladFox shares one cached knowledge base across every employee's questions instead of every employee burning their own separate budget on overlapping questions — a hundred employees asking similar things ends up costing a fraction of what a hundred separate AI budgets would.

No — the platform fee isn't a per-employee license, precisely because that's the pricing model GladFox is designed to be cheaper than. Talk to us for a quote shaped around your team's size and how you'd deploy it.

Yes — the live demo is a real, working instance of the product, not a scripted mockup, and there's no signup required. It walks through an unscripted scenario at a fictional demo company so you can see the actual back-and-forth for yourself.

Point us at your documents, onboarding material, and internal tools. We curate that into a knowledge base GladFox actually reads — no AI expertise needed on your side.

Three steps: we learn your company by curating a knowledge base from what you give us, we deploy it under your own brand across web chat and/or Microsoft Teams, and your team starts asking it questions like they would a coworker — no prompting skill required.

Email hello@gladfox.ai, or use the "Talk to us" button anywhere on this site — we'll get back to you.