← All changes
scheduled taskschannelsdata tablesmemoryintelligenceagents

Images in scheduled messages, rolling due dates, and rebuildable memory

Scheduled and audience messages can carry an image and roll a due date forward, and owners can rebuild memory and business intelligence from past conversations with cost quoted up front.

New

  • Attach an image to a scheduled message. Every scheduled task — a one-off reminder, a recurring check-in, or an audience message to everyone matching your filters — can now carry one image. It arrives as a single message with your text as the caption, not a photo followed by a separate bubble, which is what a birthday greeting or a promotional card needs to look right. Pick it from your Assets library; everyone in an audience gets the same image. See attaching an image.

  • WhatsApp image templates now work. Templates that Meta approved with an Image header were previously rejected. Selecting one now reveals the Image field, and the template body becomes the photo's caption. A template's layout is fixed when Meta approves it, so an image still cannot be added to a text-only template — create one with header type Image in WhatsApp Manager. See templates and quality.

  • Move a date forward after sending. The audience message setting formerly called Mark as contacted is now After sending, update, and on a date column it can do more than stamp the send time: tick Move it forward by N months and the column is set to its own value plus that many months instead. A reminder filtered on due_date is {{today+7d}} now rolls each row to its next cycle as it sends, so the following cycle is picked up with no further setup — the shape subscription renewals, appointments and insurance premiums all need. Author one task per interval, each filtered to its own frequency. Month-ends clamp rather than overflow, so a 31 January due date moves to 28 February and returns to the 31st as soon as the target month is long enough. See updating the row after sending.

  • Rebuild a contact's memory. Open a contact's Second Brain and choose Rebuild memory. KlicForge re-reads that contact's past conversations and regenerates what the agent knows about them. Useful when memory was switched on after the conversations had already happened, or when older memories were captured before recent accuracy improvements.

  • Rebuild your workspace's business intelligence. Rebuild on the Intelligence page re-reads every ended conversation in the workspace. You can rebuild memory, business intelligence, or both — rebuilding both together costs the same as either one alone, because they share a single pass over each conversation.

  • See the cost before you commit. Both rebuild buttons show how many conversations will be re-read, what that costs in interactions, and how much of your monthly allowance is left, before anything happens. A rebuild costs 1 interaction per conversation. If it would exceed your remaining allowance, it is blocked rather than run.

  • The Conversations tab is back on Agent Detail. A read-only table of every conversation with that agent — widget, Telegram, WhatsApp, and Admin Chat sessions — now lives under a Conversations tab. Rows don't open inline; a View Chat action hands off to the full transcript in Inbox or Chats.

Changed

  • The "mark as contacted" setting has a clearer name. It is now After sending, update. Existing tasks are unaffected — with no interval set it stamps the send time exactly as before.

Notes

  • Only images shared with all conversations can be attached to a scheduled message. Open the file in Assets, choose Share with all conversations, and give the agent permission to send it. Files belonging to one customer are deliberately not offered — a scheduled message has no single customer behind it to check them against.
  • A message with an image counts as two interactions instead of one. A 500-person campaign with a photo uses 1,000. See interaction counting.
  • On Telegram, keep the text under 1,024 characters — past that the remainder arrives as a second message.
  • Rebuilding memory or intelligence happens in the background over the following minutes. Memories and insights repopulate as it progresses.
  • Old memories are archived, not deleted. People and companies your agents have identified are kept as they are, so existing connections between them survive.
  • Events you have rejected or corrected on the Intelligence Audit page are preserved. A rebuild may surface similar events again, so it is worth re-checking the Audit queue afterwards.
  • Rebuilding is available to owners and admins. Memory needs the Startup plan or above; business intelligence has no plan requirement.
  • Clicking Rebuild twice does nothing the second time and costs nothing — conversations already queued for a rebuild are not counted again.