Solopreneurs and small businesses

Goal: Build a reply guide that tells a helper which business facts are approved, what remains unconfirmed, and where to check before making a promise.

When this helps

You sell handmade notebooks. A customer asks for 50 copies by next Friday, a weekend helper quotes an old delivery rule, and your latest supplier note is buried in a folder. The task is to give everyone the same reference before they answer. Start with one product and one recurring question; a complete catalogue is unnecessary.

Use Business practice as your exercise theme. Later, replace the examples with approved brand wording, product specifications, FAQs, and operating instructions. Customer identities, payment details, and individual order records belong in their usual business systems.

Before you start: Complete your first workspace and select a workspace where you are an Editor or Owner. You can complete this exercise without an AI connection. Markdown is ordinary text with headings, lists, and tables; you do not need to write software code.

Fictional practice material

The examples are invented. When using your own files, check ownership, permissions, and the intended readers before uploading or sharing them.

Give each kind of information a home

Material	Where to keep it	Why it belongs there
Supplier specification, permitted product photo, dated price sheet	Library	Retain the source you can compare with a summary later.
Product facts	Context	Explain approved specifications and unanswered questions in everyday language.
Delivery policy	Context	State the operating rule, exceptions, approver, and effective date.
Reply guide	Context hub	Link the facts and policy and collect reviewed answers to recurring questions.
Brand voice and opening/closing checklist	Additional Context pages	Help a substitute use the same tone and operating standards. Add them when needed.

In words: original material supports Product facts; that page and Delivery policy support Reply guide. A person checks the guide and sends the answer through the normal business channel. The arrows show reference relationships, not automated order processing.

Build the three-page guide

1. Open Context → New Context page. Put the first page title below in the title field and its Markdown in the body.
2. Choose Save draft and check that saving completes. Read the page, then choose Publish. This makes a workspace version available to readers; it does not enable anonymous web access.
3. Create and publish the second supporting page the same way.
4. Create the hub page last. Type [[ or choose Wikilink to select each existing target. The copied [[Page title]] text is a starting point; select the correct page if a title is ambiguous.
5. Publish the hub and open every link in the reader. Check the workspace and actual target if a link does not resolve.

For toolbar, citation, and editing details, see Context pages and images and links.

Copy the page content

Create the pages in this order. Put each heading’s page title in the title field and paste the block below it into the body.

Product facts

# Product facts

## Fictional product
A handmade notebook.

## Confirmed details
- Size: A5
- Pages: 80
- Cover: blue

## Unknown
Bulk-order lead time has not been confirmed.

Delivery policy

# Delivery policy

## Practice policy
Dispatch within three business days after payment confirmation.

## Exceptions
Confirm stock before accepting a bulk order.

## Missing information
Destination-specific delivery time is not specified.

## Approval
Exercise only; replace with a policy you have approved.

Reply guide

# Reply guide

## Before answering
Check [[Product facts]] and [[Delivery policy]].

## Practice question
Can I order 50 notebooks for an event next week?

## Draft reply
Thank you for your interest. I will confirm stock and the dispatch schedule before promising a date.

## Need to confirm
- Quantity available
- Destination
- Required arrival date

## Status
Draft wording for human review; not sent to a customer.

Use it for an incoming question

1. Open Search, enter Reply guide, choose Scope → Context, and open the published result. You should reach the hub rather than hunt through individual messages.
2. Open Product facts and Delivery policy from the hub. Compare the requested quantity and date with the approved facts. In this exercise, A5 size and dispatch within three business days are recorded, but bulk stock and destination-specific transit time are not.
3. Prepare an answer using the guide's draft wording. Ask the customer for the destination and required arrival date in your usual channel. Confirm stock separately; the wiki does not check live inventory.
4. If a new question keeps returning, choose Edit on Reply guide and add an FAQ entry with a confirmed answer, its source, and any exception. Save, check, and publish it when approved.
5. Reopen the reader-facing page and check Readers see v…. A helper with Viewer access should now receive the approved FAQ, while an unsubmitted edit remains the author's saved work.

Add a brief brand rule such as “Use plain language and give a concrete next step; avoid promising stock before checking.” Keep proposed campaign wording under Proposed wording until you accept it. A published page may still contain a clearly labeled proposal; publication alone does not mean every sentence is an approved policy.

Change a price or policy without losing the reason

Suppose a fictional price changes from 12 to 14 credits on 1 November, and large orders now need five business days before dispatch. Keep the old and new facts distinguishable.

1. In Library, open the existing price-sheet item and use Upload new version if that source changed. Inspect Versions and the extracted content; a successful upload alone does not prove all amounts were read correctly.
2. Choose Edit on Product facts or Delivery policy. Record the new value, effective date, who approved it, and the reason, such as a supplier-cost change. State whether an already accepted quotation keeps its former terms; do not invent that exception.
3. Add the relevant source with Citation and select the actual source suggestion. A citation makes the reference reachable; you must still compare the amount yourself.
4. Save the draft and arrange a human check of price, tax wording, effective date, and exceptions. In the browser, Save draft does not itself submit a Review item. An Editor or Owner may publish directly after checking; if an integration has submitted a proposal, use Review queue → Pending, inspect View changes, and approve or request corrections.
5. Publish the approved update, then update every affected FAQ in Reply guide. Open History to compare the changed values and reopen the published pages. Linked text is not automatically rewritten when a policy changes.

A useful recurring check is five minutes at opening: search the hub, check today's effective rule, and list unresolved questions. Once a week, compare frequently used answers with their sources and clear obsolete wording after preserving the decision in History.

Share the guide appropriately

For a helper, use Share → Copy workspace link after confirming their membership and role. A workspace link does not grant access by itself. Review workspace membership rather than assuming a link exposes only one page.

For customers, prepare a separate public FAQ containing only approved customer-facing terms. Exclude supplier costs, private negotiations, and customer examples. Preview the published version before Publish to web and check the public URL signed out. An Owner's acknowledgement is required for anonymous exposure from a non-public workspace; an unlisted URL can be forwarded. After later edits, check both the public snapshot and sharing state again. See sharing.

Check the result

• A helper finds the guide through Search and opens both supporting pages.
• Each price or policy states its effective date and owner; uncertain lead times are visibly unresolved.
• The current published FAQ agrees with the current published policy and original source.
• History explains the most recent change, and no customer names or order records are needed.
• A public FAQ, if you created one, contains only the reviewed customer-facing version.

Optional: draft an answer or audit a change with AI

Complete MCP connections first and grant only the required workspace and reading permission. These prompts request no writes. The credential grants and workspace permissions control access; wording in a prompt does not enforce them. An external AI service can receive material its tools read, so use only material you may send to that service.

Read Product facts, Delivery policy, and Reply guide. A customer asks for 50 notebooks for an event next Friday. List the confirmed facts, missing details, and a polite proposed answer. Cite the relevant pages. Do not promise an arrival date, send a message, accept an order, or edit pages. Reply here only.

For a policy update:

Read the current Product facts, Delivery policy, and Reply guide. Identify FAQ wording that may conflict with the recorded effective dates or dispatch rule. Quote brief supporting passages and return a correction checklist. Mark uncertain cases. Do not change pages or invent a business decision.

Check each suggestion against the actual product specification and approved terms, including which dated rule applies. You decide, publish corrections, and send any reply. dtxWiki provides reusable business knowledge; it does not run a POS, message customers, collect payments, or manage fulfilment.

Chats records dtxWiki tool activity; it is not the complete conversation or a record of every external action. None of these examples depends on an AI service.