Tips

Tips are short, high-signal answers that Ogma can use alongside your longer documentation.

Where tips come from

• Auto-learn — after a staff-resolved ticket closes, Ogma extracts a concise tip and adds it to the knowledge base. Remove unwanted tips in the learned-tips Discord channel or the dashboard.
• Manual — you can create tips directly in the dashboard when you notice a repeated question that does not belong in a long doc.
• Import — bulk-add tips from a JSON or JSONL file on the Tips page.

Only tips that remain in the knowledge base (not removed after auto-learn) are searched during tickets and Playground tests.

Tips vs Knowledge

	Tips	Knowledge
Length	1–3 sentences	Paragraphs to pages
Source	Resolved tickets or manual entry	Uploads, pastes, synced URLs
Update cadence	Frequent, small edits	Occasional, larger updates
Example	"Staging tokens expire every 6 hours"	Full guide on generating and rotating tokens

Use the right tool for the job. A 10-page integration guide belongs in Knowledge. The three-line gotcha your team repeats belongs in a tip.

Managing tips in the dashboard

On the Tips page you can:

• Browse all tips in the knowledge base
• Edit the title and body
• Merge near-duplicate tips
• Delete tips that are outdated or incorrect
• Import and export tips in bulk
• See which ticket a tip originally came from (when applicable)

Edits are live immediately.

Managing tips in Discord

When auto-learn adds a tip, it appears in your learned-tips channel with a Remove from knowledge base button:

• Remove — discards the tip from the searchable knowledge base (with a short confirmation step)

You can still edit or remove tips later from the dashboard.

Quality guidelines

Good tips are:

• Specific and verifiable
• Free of time-sensitive details that will rot quickly
• Written as the answer, not a prompt or instruction to the model

If a "tip" is growing long or has many conditional branches, consider moving it into a proper document in Knowledge and linking to it.

Import and export

Use Export tips to download all tips as a JSON bundle. Use Import tips to bulk-add tips from:

• A Ogma tips export file (schemaVersion: 1)
• A JSON array of { "content": "...", "question": "..." } objects
• A JSONL file with one tip per line (content or legacy tip field)

When importing into a guild that already has matching tips, choose Skip duplicates (default) or Stop import to fail the whole batch.

Turning auto-learn off

If you prefer a fully manual knowledge base, disable Auto-learn in Settings. Existing tips remain searchable until you remove them. You can continue to create tips manually.

Batch learning from transcripts

The Learn from transcript channel section on the Tips page scans a Discord channel for closed-ticket HTML transcript links and runs tip extraction over them in bulk using OpenAI Batch.

What it costs

Each HTML transcript page the AI successfully processes is billed at £0.01 per page on Plus and Enterprise. Important details:

• Separate from direct AI questions — batch learning does not use your included Playground or /ask quota.
• Per HTML page processed — you are charged when the AI runs on a transcript page, not when a tip is saved. Pages with no extractable tips still count if the AI ran successfully.
• Skipped pages are free — already-learned tickets, transcripts without a staff reply, and tickets that are too short are not sent to the AI and are not billed.
• Failed API calls are free — if OpenAI fails to process a page, you are not charged for it.
• Free plan — usage billing requires a Plus or Enterprise subscription.

After you scan a channel, the dashboard shows an estimated cost for the run (page count × unit price). Use Scan channel before Run batch learning to review the estimate.

Usage appears on your Stripe invoice under batch tip learning. See Billing for current rates and usage.