Start with a small operational pack
For a quote responsibility, supply the approved packages, required scope questions, prices, exclusions and decision owner. For customer care, supply the current policy and the source of account-specific facts. For operations, supply the accepted-work handoff and dependencies.
A company website can provide a useful introduction, but it may not contain the internal rule that decides an exception. Treat public context and operational instructions separately. The workforce should know which information describes the business and which information controls what it may promise.
Make current versions easy to identify
A folder with three price lists does not tell a role which one to use. Name the owner, effective version and scope of each decision-bearing document. Archive the outdated instruction from the active pack rather than leaving it as an equally plausible source.
Changes need to reach the roles affected. If a package changes, sales must use the new offer and service must understand which earlier customers remain on accepted terms. A new company policy should not silently rewrite a historical customer agreement.
Include what the business does not do
Exclusions are useful knowledge. A contractor may not cover a particular service area. A professional-services firm may require approval before committing to a start date. A retailer may have an exception process for a disputed return.
Write the next step for those cases. “Ask the owner” is useful only if the owner receives the relevant facts. A good exception record identifies the request, the rule that prevents an automatic decision and the information needed to resolve it.
Test the pack with practical questions
Ask for a standard offer, an excluded request and a conflict between two apparent sources. The result should use the authoritative instruction or mark the conflict for review. An invented resolution is less useful than a clearly identified question.
Then change one fact and repeat the scenario. This helps check whether the current instruction reaches the workflow. Use fictional customer details in the public demo and keep sensitive business material out of an evaluation unless its use and handling are appropriate for your setup.
Keep knowledge and ownership connected
GPT Business’s workforce directed through the Manager uses company context around the work you direct. Its appeal is a place to explain how your business works and then inspect how that context shapes a useful output.
The knowledge pack is still your business’s instruction. Choose who maintains it, review meaningful changes, and confirm the connected actions during assisted activation. Good setup is an operating habit, not a one-time upload that can be forgotten.
Your working checklist
- Choose the first job.
- Collect only the facts it requires.
- Name the owner and active version.
- Include exclusions and approval boundaries.
- Test a conflict and a missing fact.
- Define how meaningful changes reach the workflow.
Try this in the demo
Use a fictional example and replace the business details with your own approved information. This prompt prepares a draft for review; it does not authorize live actions.
Help me organize a small knowledge pack for standard quote preparation. Use the offer, approved prices, exclusions and exception owner I provide. Identify conflicting or outdated instructions. List the facts that control decisions separately from general company background, and suggest a simple process for keeping the pack current.
Frequently asked questions
Should I upload every company file?
Not as a substitute for a clear first scope. Begin with relevant, current information whose authority your team understands.
Does company knowledge automatically authorize an action?
No. Knowing an approved price or policy is separate from permission to send, update, schedule or commit.
To define company context and authority, read approval rules for AI employees.
Related reading
Try it with a task from your business
Ask the Manager for a draft you can review. Decide what you want to keep doing yourself. Supported live actions and permissions are confirmed during setup.