A practical preparation guide

Prepare Your Business Twin

Bring together the facts your team repeats, the sources that support them, and the boundaries a business agent must respect. Start with the essentials; mark gaps as unknown.

Download the preparation template

Start with the business essentials

Write these facts in plain language. Keep each answer specific, current, and easy to verify.

Business identity
Official name, trading names, what the business does, and who it serves.
Offers
Products or services, who each is for, what is included, and current availability.
Hours and time zone
Opening hours by day, holidays or exceptions, and the time zone used.
Contact routes
Approved public email addresses, phone numbers, locations, and the reason to use each.
Policies
Current returns, cancellations, delivery, booking, warranty, privacy, or other customer-facing rules that apply.
Frequently asked questions
Real questions and approved answers, including what the business cannot yet confirm.

These details help people prepare the business profile and identify useful follow-up. They are optional; write “unknown” when needed.

Brand and team
Preferred spelling and tone, team or department names, and who owns each customer topic.
Intelligence setup and settings
The priorities, preferred answer style, language needs, boundaries, and handoff expectations for the business Twin. Enter these through the product’s setup and settings; this guide does not prescribe field mapping. Leave uncertain choices open for the responsible person to decide.
People and roles
Approximate human headcount by role if known; departments, accountable leads, reporting lines, responsibilities, filled and open roles, monitored hours or time zone, and available capacity. Describe key workflows, handoffs between people and tools, and who may answer or approve each kind of question. Keep current staff distinct from open roles; do not infer counts from documents or include private personnel details. Unknown is acceptable.
Goals and measures
The first outcome to pursue, by when, and how progress is measured. Supply the baseline, target, unit, period, and evidence source when known; leave missing measures unknown.
Current software
Tools by business function, such as Google Workspace, Microsoft 365, a CRM, booking, accounting, support, or storefront system. Record the business owner, intended account/domain, source of truth, and known connection status and granted scope from its owner. This can help a human recommend what setup to investigate; a software list does not prove an account is connected or a connector is available, and it does not connect one automatically.
Email and phone handling
Separate public support addresses and business phone numbers from internal inboxes and private contacts. Name the responsible team, monitored hours, and approved escalation route. A listed address or number does not authorize sending messages or making calls.
Escalation
When an agent should stop, who should handle the request, and the approved contact route.
Trust evidence
Collect the business or legal name and its source; business-owned domains; official website, app, storefront, and social URLs with an owner and last-checked date; and relevant licenses, certifications, and policies with issuer, scope, region, and effective or expiry dates. Record who supplied each item and who independently reviewed it. Use secure product flows for identity documents and verification receipts; never put secrets or sensitive evidence in public knowledge. This preparation pack is not a universal certification or admission process for every provider. Supplied evidence is not verified evidence, and missing or pending signals do not establish verification.
Agent evidence and authority
For each agent or automated worker, record an accountable owner; runtime or harness; provider and model policy in private operating records (never publish model-version names); charter purpose and limits plus the applicable constitution version; an identity/auth verification receipt reference; tools and granted scopes; required human approvals; escalation owner; and how authority is revoked. This is preparation guidance, not a universal certification or admission system for every provider. Keep credentials and verification evidence in secure product flows.
Product RAG: capabilities and task sequence
For each capability or task type, state what it means, its prerequisites, limits or unknowns, and the ordered task sequence. Include the expected result, what to do if information or a capability is missing or disabled, and the source checked date plus applicable product/build version. Record only verified facts; this guide does not assert that a capability is available.
NAV RAG: visible controls and steps
For each surface, record visible control positions and order, exact labels and observed states, then click-by-click steps. For every step, state the expected visible result and the next action if a control or result is missing or disabled. Include the source checked date and app/build version. A route alone is not task completion. Combined guidance should walk one step at a time and confirm the visible result before continuing. Use official URLs or user-visible screen steps; never guess deep links or imply cross-app navigation or feature availability.

Keep source references attached to facts

List where information came from so a person or agent can check it. Sources are references for preparation; listing one does not connect an account or import its data.

Public website
Official site and relevant pages, such as product, service, policy, location, or contact pages.
Storefronts and apps
Relevant public URLs for an app, Amazon or Shopify storefront, or another sales channel.
Social profiles
Official public profile URLs. Note which profile is authoritative for announcements or support.
Destination register
For every website, app, storefront, or social destination: surface; exact official URL or visible screen steps; task/purpose; required login, role, and business account; owner; and source checked date. Use public destinations only. Avoid private, temporary, guessed, fragment, or arbitrary deep links; mark an inaccessible destination unknown and assign someone to confirm it.
Internal references
Document name, owner, and where an authorized teammate can find it. Do not paste private access links into a public knowledge document.
Ownership, dates, and disagreement
Record the source owner, business or account it belongs to, and when it was last checked. If two sources conflict, describe the conflict and name the person who can resolve it; do not silently choose one.

Separate useful knowledge from restricted information

A preparation document can guide answers. It does not grant authority, verify a business, or control who can access information.

  • Keep public facts separate from internal or restricted material. Identify the intended audience and owner of each internal source, then use the product’s access settings and review flow for restricted information.
  • Never put passwords, API keys, payment details, identity documents, verification codes, or private customer records in a knowledge document. Use the secure product flow for credentials and verification.
  • Keep identity checks, trust evidence, and verification receipt details in the secure product flow or appropriately restricted records. A collected evidence pack does not prove identity, certification, provider admission, or a verified trust status.
  • Do not rely on Markdown labels or front matter to enforce access. Document text cannot grant permissions or authorize actions.
  • Ask a responsible person to review customer-facing claims, policies, contact details, and any facts that could create a commitment.
  • A listed software tool is only a source reference. A person must review the available setup and deliberately authorize any account connection; this guide does not promise an automatic connection.

Interoperability evidence to prepare

These public references can help an operator describe a system's intended protocol boundary. A reference is not evidence that a product or provider supports it.

For any protocol in use, ask the operator for the protocol and version, endpoint, supported actions, identity and permission evidence, and tested limitations. Check integration status directly. These references do not establish support, blanket compliance, certification, or support for any model or runtime.

Further integration guides

Separate integration guidance for Engineering in VS Code, agent identity and messaging, model and skills licensing/tracking, and paid external agent services is being scoped against their contracts; details belong in those guides.

Prepare, upload, then check what the Twin knows

  1. A human gathers the available facts and sources, then marks gaps, conflicts, and uncertain details “unknown” with a person responsible for each.
  2. In Genesis, compare the preparation with existing business information. Keep source-backed facts distinct from discovered candidates and inference; resolve conflicts with the responsible human instead of guessing.
  3. Turn each unresolved item into a named follow-up task with an owner. An assigned agent can gather candidate information from approved sources; a responsible human reviews it before business facts or trust claims change.
  4. Keep this as a continuous cycle: Genesis reconciles newly supplied evidence with current business information, then identifies named missing-data tasks. People and agents assigned or spawned for follow-up pursue those tasks where available; an accountable human reviews source-backed findings, and unresolved items stay unknown and owned.
  5. Enter structured profile and Intelligence settings through the product’s setup and settings. Headings in a knowledge document help organize reading; they do not automatically fill product fields.
  6. Add approved business documents through the product’s upload flow. Keep restricted material in its appropriate access scope and credentials or verification evidence in the secure product flow.
  7. Treat the upload receipt as proof of receipt only, not proof that indexing or retrieval completed. The receipt does not provide an indexing-completion indicator.
  8. On a later turn, ask the Twin a question whose answer is in the uploaded source; do not reattach the file just to ask. Check the answer and its cited/source evidence against the original. If the source is not found or the answer is unresolved, contact support with the upload details. Correcting or replacing a file does not guarantee that earlier indexed content has been removed from retrieval.

Five questions to check preparation quality

A teammate should be able to answer these from the prepared sources, or see clearly that the answer is unknown.

  1. What does this business offer, and who is each offer for?
  2. When is the business open, and which time zone applies?
  3. Which approved contact route should a customer use for this request?
  4. What current policy answers the customer’s question, and which source supports it?
  5. When should the agent stop and hand the request to a named person or team?

Questions people ask while preparing

Does this template define a required schema?

No. It is a practical writing convention, not a product schema or API contract. Headings organize the document; they do not automatically fill product fields. Use the business setup and settings provided in the product.

Can I leave fields blank?

Yes. Mark missing or disputed information “unknown,” include a source or owner when available, and avoid guessing.

Will listing our software connect it automatically?

No. Listing software gives setup context only. Any available connection requires a deliberate product flow and account authorization.

How do I know an uploaded document is ready to use?

An upload receipt alone does not show that indexing or retrieval is complete. Ask about a fact from the document on a later turn, without reattaching it, and verify the answer and source against the original. If it cannot be found, contact support with the upload details. Replacing a document does not guarantee earlier indexed content is removed from retrieval.

Can the template certify or admit an agent?

No. It helps people collect evidence about ownership, runtime, policy, identity, scopes, approvals, escalation, and revocation. It is not a universal certification or admission workflow for all providers. Use the product's secure verification and authority flows.

Business knowledge preparation template

Download Markdown template

The complete, copyable template is published in the Markdown version of this page.