Skip to main content

One post tagged with "knowledge"

View All Tags

The Easiest Way To Keep Wallu Up To Date

· 2 min read
Topias
Topias
Wallu's Developer

If you only do one thing to improve Wallu’s answers, make it this: create a staff-only channel like #wallu-knowledge, post your definitive answers there, and import that channel into Wallu. From then on, any new message in that channel becomes part of Wallu’s knowledge within 24 hours - no commands, no docs tools, no context switching.

Why this workflow works​

  • Stays in Discord: Staff write, edit, and discuss answers where they already live.
  • Extremely Fast & Zero friction: No extra tools, no learning curve.
  • Zero commands: Post messages normally; Wallu picks them up on the next daily refresh.
  • Easy to review: Keep answers visible, editable, and searchable as regular Discord messages.
  • Organic updates: As your product changes, your team naturally updates the latest message/thread.
  • Use /sync if you want instant updates (updated in less than 5 minutes).

How to set it up​

  1. Create a private channel like #wallu-knowledge for your staff.
  2. Have your team start posting canonical answers there.
  3. In Wallu’s dashboard, add that channel as a knowledge source and run the initial import.
  4. That’s it. Wallu refreshes from the channel roughly every 24h.

Writing great knowledge posts​

  • Full sentences: Write in clear, complete sentences.
  • Few sentences per topic: 3–8 well-formed sentences instead of short bullet points, lists or short FAQs.
  • More context is better: Use a bit more words!
  • Define context of abbreviations/terms briefly: "MyProject works on M4" (bad) vs "MyProject works on M4 (Apple Silicon Macs)" (good)
  • Link instead of lists: For long, changing lists (e.g., supported countries), link to the page that's updated instead of listing them all in multiple places.
  • Avoid ultra-short FAQs: One-liners and terse lists reduce accuracy; expand to a small paragraph.

Practical examples​

  • Good: “Refunds are available within 14 days for purchases from our site. Open a ticket in #billing with your order ID. If you bought via a reseller, contact them directly. Full policy: https://example.com/refunds.”
  • Needs work: “Refunds? 14d. ID needed. See policy.”

Maintenance tips​

  • Edit, don’t append: Update the original message so only the latest guidance remains. (Or delete the old message)
  • One topic/FAQ per message
  • Pin key answers: Helps staff discover the canonical version to update.

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