Skip to main content

The #wallu-knowledge Channel

If you do one thing to keep Wallu accurate, make it this: keep a staff channel where you post your definitive answers, and let Wallu import it. From then on, every new message there becomes part of Wallu's knowledge - no commands, no dashboard, no context switching.

Why it works​

  • Stays in Discord - your team writes and edits answers where they already work.
  • Zero friction - post a message; Wallu picks it up on its next refresh (about every 24h).
  • Always current - as your product changes, you just edit the message.
  • Instant updates - run /sync to refresh in under five minutes.

Set it up​

  1. Create the channel. If Wallu has the "Manage Channels" permission it can create a private #wallu-knowledge channel for you and import it automatically. Otherwise, create a staff-only channel yourself.
  2. Post your answers there (see the format below).
  3. Import it (if not done automatically): Documents → "Add new document" → "Add Discord channel" → pick #wallu-knowledge. This is a regular Discord document.
  4. Confirm the document shows as Processed, and choose which channels can use it.
tip

You can do all of this by asking the Setup Agent in #wallu-setup, e.g. "create a wallu-knowledge channel and import it".

How to write good knowledge posts​

Aim for one topic per message, written as a short paragraph. A loose Q&A style works best:

  • Full sentences: 3-8 clear sentences beat terse bullet points or one-liners.
  • Define terms: "MyApp runs on M4" → "MyApp runs on M4 (Apple Silicon Macs)".
  • Link, don't list: for long or changing lists (supported countries, prices), link to the page that stays updated.
  • One topic per message: keeps each answer easy to find and edit.

Good: "Refunds are available within 14 days for purchases from our site. Open a ticket in #billing with your order ID. Bought via a reseller? Contact them directly. Full policy: https://example.com/refunds."

Needs work: "Refunds? 14d. ID needed. See policy."

Keeping it tidy​

  • Edit, don't append - update the original message so only the latest guidance remains (or delete the old one).
  • Pin key answers so staff can find and update the canonical version.
  • Run /sync when you want a change live immediately.

This small habit compounds: your team writes once in Discord, and Wallu keeps support accurate and fresh automatically.