Skip to content
2026.7.12

Structured memory, per-contact control

Teammate memory becomes organized and deduplicated, and you can now change how a teammate handles one specific contact without touching the rest.

  • memory
  • learning
  • autonomy
  • console

Twenty-three changes shipped in this release. What a teammate remembers is now kept in organized blocks instead of one growing note, and autonomy stopped being all-or-nothing: you can set how a teammate treats a single contact.

Memory and learning

Memory now behaves like a well-kept notebook rather than an ever-growing text file.

  • Fold old notes into the new format — a one-tap reconcile on a teammate’s Memory & Learning tab converts old free-text notes into organized blocks and tells you how many facts were folded.
  • No more near-duplicates — when a teammate learns something it already knows in different words, it updates the existing note instead of stacking another one, so older important facts stop getting pushed out.
  • Repeated situations get learned — hitting the same kind of situation more than once now reliably becomes a lesson.
  • Paraphrased corrections count once — several corrections that mean the same thing are recognized as one lesson, so it takes effect sooner.
  • Proposals surface immediately — in approval mode, a proposed learning update notifies the owner and appears live instead of waiting to be discovered.
  • Consistent contact memory — a fact learned about a contact during a call or chat is reconciled against what is already known.
  • Old imported notes stay private — a contact’s legacy free-text notes are visible only to the owner through a teammate’s tools, and are cleaned before they appear anywhere.
  • Catch up always finishes — the catch-up action on a contact completes and re-enables even when there was nothing new to learn.

Per-contact control

Autonomy used to be a single setting for the whole team. Some customers need different handling.

  • Override one contact — from the contact or messaging screen, pause a teammate for that person, force draft-only, allow autonomous sending, or hand the contact to a different teammate entirely.

Console and messaging

  • One-tap confirmations — an action needing your approval shows a card with the recipient and the exact message, and Send fires it once even across a double-tap or two open tabs.
  • Tidier bulk actions — simultaneous bulk sends collapse into one-line summaries; anything that needs attention stays open.
  • Bulk sends stay with their operator — when several people have console access, each sees and controls only their own.
  • Image-only sends — sending an image without a caption works, by button and by keyboard.
  • Instagram routing — inbound DMs land in the right conversation, and your own sent replies stop being read as a new contact.

Under the hood

  • Lighter prompts — dropping the legacy memory blob from every turn removed roughly 17,000 tokens per turn on the busiest teammate.
  • One model setting for contact memory — all six contact-memory pipelines now run through a single tunable area instead of ad-hoc routing.
  • Documentation shipped with the release — an audit against the code found and corrected 29 gaps, and every documentation page now records when it was last verified.

← All releases

See these releases working on your own customers.

Loquent is in closed alpha and every business is set up personally. Request an invitation and we'll map your channels, teammates, and follow-up rhythm together.