Zelpa

Support

Zelpa is run by one person, and support is personal: if something's wrong, you reach the person who built it.

How to get help

Email is the one support route: support@zelpa.fyi. Include your server's name and what you were doing when it went wrong — that speeds things up a lot.

Quick checks before you write

• Zelpa says it's under maintenance — an update is in progress. Summaries pause and resume on their own, usually within the hour.
• Zelpa won't summarize this channel — your server's admins may have blocked the channel, or Zelpa may not have permission to read it. An admin can check both.
• "Try again later" on a channel you just summarized — each channel allows one summary run per user per hour. The wait is real time; it counts down whether or not the bot is online.
• The server's daily pool is used up — every summary footer shows your server's running total out of 500,000 characters for the day. The pool refills at the start of the next day.
• Zelpa refused your file — spreadsheets, scanned PDFs and images, old .doc/.ppt files, archives, and audio/video are refused in plain words, by design. The FAQ lists what Zelpa does read.
• You want your messages left out — use Zelpa's opt-out command on that server; opt back in any time with the opt-in command.

One thing support can't do

Because Zelpa stores nothing, there are no saved summaries to recover, resend, or look up — if a summary scrolled away, run the catch-up again and Zelpa will rebuild it from the channel. That is the privacy design working as intended.