Glitch

Guide

Shared AI context template for a small business

Published November 2026. About a 2 minute read.

A shared AI context document tells an assistant which facts, terms, sources, and working rules a team has approved. Use this template to give teammates a common starting point while keeping assumptions, outdated facts, and private information clearly separated.

Glitch is live in the chat on our home page. Say what your business needs and it starts working, no signup.

Talk to Glitch

Copy the template

Free to use with your own tools. No email required. Replace the brackets with information you're allowed to share.

Business context version: [date and owner]
What we do: [approved description and source]
Who we serve: [approved audience]
Terms we use: [term = definition]
Authoritative sources: [document, owner, last reviewed, permitted audience]
Working rules: [drafting, approvals, actions that require permission]
Known unknowns: [questions that need an answer]
When sources conflict, name the conflict and ask the source owner.
Use only material this audience is permitted to see. Don't treat old examples as current policy.

Try this template with Glitch

Start with an example in the homepage chat. This won't connect your private tools.

Worksheet to copy and adapt

Context areaRecordMaintenance rule
Business factsApproved description and sourceName an owner
TerminologyPreferred term and definitionReview ambiguous terms
Working rulesAllowed work and approval boundaryState exceptions
Source mapDocument, access, freshnessCheck permissions
UnknownsQuestion and resolverDo not fill with guesses

Write facts and instructions in separate sections

“We serve independent shops” is a business fact. “Ask for approval before sending a customer email” is a working rule. Keeping these separate helps reviewers notice when an instruction changes rather than burying it in background prose.

Start with the smallest set of facts needed for one workflow. A full company archive is harder to maintain and may contain material that not every teammate is allowed to see. Add context when a real task reveals a gap.

Worked example: a stale offer

Illustrative situation: an old sales deck lists a service that is no longer offered. The current service document excludes it. A source map should name the current document as authoritative and mark the deck as historical.

A good answer says the sources conflict and uses the approved current policy. It should not combine the two into an invented package. Preserve a review date so the team can tell whether “current” has become stale.

Test shared context with two teammates

Have one teammate ask a question, correct the underlying document, and have a second teammate repeat the task in a fresh conversation. Compare the answer and its source reference. This tests retrieval behavior rather than merely whether the first chat remembers the correction.

Do not assume every product shares memory between users. Verify which workspace, document permissions, and chat settings apply. A correction in one conversation may stay in that conversation unless you update an approved shared source.

Try it on your business

Paste your website address. Glitch reads it and shows you where it'd start, in about a minute, before you sign up for anything.

No signup, no card. Nothing gets connected until you say so.

Give each source a maintenance owner

Assign someone to review changes to pricing, services, terminology, and operating rules. Use a short change note explaining what changed and why. Archive superseded versions so people can investigate an old answer without treating it as current.

For Glitch, start by exploring the shared-AI guide below and testing one approved workflow. The template is portable; you can also keep it in your existing documentation system and use it during a product trial.

Common questions

Does a shared context document train the model?

Not by itself. It supplies context for a workflow. How a vendor stores or uses that content depends on the product and its settings.

Should all company information go in it?

No. Include only what the workflow needs and what the intended readers can access. Keep restricted sources separate.

Keep reading

See it working, not described

Try it with your own website

Paste your website address. Glitch reads it and shows you where it'd start, in about a minute, before you sign up for anything.

No signup, no card. Nothing gets connected until you say so.

Or start free with email, no card