Digest Scheduling and Language

A connected chat has three settings, all changeable from the chat itself and all belonging to that chat rather than to your account.

How often

/frequency offers four:

Daily	One digest a day, at your chosen hour. The default.
Every 4 hours	Six a day, evenly spaced from when you set it
Weekly	One a week, on your chosen hour
Off	Nothing scheduled

Off does not disable the bot. /briefing and /radar still work on demand, and chat still works. This is the setting for people who want Feedpik in a chat window without being messaged — and it is a perfectly ordinary way to use it, not a degraded one.

Every 4 hours counts from when you set it, not from midnight. It is spacing, not a clock, so the daily and weekly options are the ones that honour a time of day.

What time

/time sets the hour for daily and weekly digests, in your delivery timezone. Whole hours only.

The hour matters more than it looks. A digest is a summary of what happened since the last one, so setting it for 8am means "the overnight news, waiting when you start"; setting it for 6pm means "the working day, as a wrap". Same feature, two different products, and the difference is one setting.

Every 4 hours ignores this — there is no single hour to honour when there are six.

Which language

/language picks from eight: English, Chinese, Japanese, Korean, Spanish, French, German, Portuguese.

This is a shorter list than the AI output languages elsewhere in Feedpik, and the reason is worth stating: the bot's own interface text — prompts, confirmations, error messages, the help listing — is hand-written per language rather than machine-generated. A model will write a summary in almost any language, but a bot that summarises in Dutch and then says "Got it — daily." in English is worse than one that stays in English throughout.

So the list is the languages the interface has actually been written for.

It changes the writing, not the reading. The bot will summarise English sources in Japanese. Which sources you get is decided by your content languages, which is a separate setting in the reader.

Per chat, not per account

All three belong to the binding, so two connected chats can differ completely — a Telegram chat on English every four hours and a Discord one on Japanese weekly, from one account.

That is deliberate. A chat is a context: the phone you check at breakfast and the team channel you keep an eye on during work want different cadences, and forcing them to share one makes at least one of them wrong.

What a digest actually contains

Your top stories from your own ranking, summarised in plain language rather than listed as headlines. Radar topics appear when several of your sources converged.

Each delivery costs 1 credit. Daily is about 30 a month; every four hours is about 180. Pro includes 1,800, so even the fastest schedule is a small fraction of the allowance — see plans.

Reactions on any story go straight into your ranking, so a digest is an input as well as an output.

If something looks wrong

Nothing arrives — check /frequency is not off, and that the hour has come round since you set it. A daily digest set at 8am after 8am starts tomorrow.

It arrives at the wrong hour — the hour is in your delivery timezone. If that is wrong, everything shifts by the offset rather than being random.

Two chats behave differently — expected. Settings belong to the binding; run the command in whichever chat is wrong.

The digest is empty or short — it covers what arrived since the last one. On a fast schedule with a small feed there is genuinely not much between deliveries; a slower schedule produces fuller digests.

My language is not offered — the eight are the ones the bot's own interface has been written for. Use the reader's AI output language for a wider set, or ask and we will consider adding a pack.