Playbooks you describe, updates that land

Every business runs on procedures that live in one place: your head. This release stops asking you to type them out — describe how something is handled and a teammate writes the playbook for you. The other half of the release is quieter and just as overdue: come back to Loquent after switching away and every screen has already caught up, instead of showing you the moment you left.

Playbooks you can just describe

A skill is a playbook — how your business handles one situation, written once so any teammate can follow it. Writing one used to mean facing an empty editor.

• Say it, and it gets written down — open Skills, choose “Tell your team”, and describe the procedure in your own words. A teammate called the Librarian listens for the three things that make a playbook usable — when to reach for it, what happens in order, and the exceptions — and asks only when something important is missing.
• Nothing goes live until you say so — every drafted playbook arrives switched off and attached to nobody. You read it back in plain language, then decide.
• Written in your words, not generic business English — your team already talks like you, and a playbook that doesn’t is harder to follow, not easier.
• It builds on what you have — the Librarian reads your existing playbooks first, so a close match gets extended instead of quietly duplicated.
• Granting is a separate step — switching a playbook on makes it available; you still choose which teammates get it, and you can take it back from one without touching the playbook.
• Or write one yourself — the editor is still there, one tap away, with the same limits either way.

An app that catches up on its own

Switch to another app, come back, and Loquent used to show you exactly what you left — live indicator lit, numbers frozen, a refresh the only cure.

• Coming back is enough — returning to Loquent now refreshes what’s on screen, whether you switched apps, switched tabs, or your connection dropped and came back.
• Every screen, not just the obvious ones — the whole product was audited surface by surface, so counts, summaries and lists all catch up rather than just the ones with live conversations on them.
• Your place in long lists is kept — a refresh no longer discards the pages you scrolled through, or your position in them.
• Sync that finished while you were away still finishes — a phone or social sync that completed during a connection drop now shows its result instead of spinning forever.
• “Draft ready” appears where you’re looking — when a teammate drafts replies, the badge lands on the conversation you already have open.

Web chat

• Messages reach your inbox the moment they land — a message sent through the chat on your website was always saved, but it didn’t raise a live notification, so a conversation already open on your screen wouldn’t show it until you reloaded. Web chat now behaves like every other channel.

Conversations

• A tidier message list — consecutive messages from the same person group together instead of repeating the name and time on every line, and sender names moved into the avatar. On a phone, a short reply no longer carries a label wider than the message.
• Delivery receipts you can act on — Sending, Sent, Delivered and Read, each with its own mark, so you can tell at a glance whether a message landed. Failed is impossible to mistake for anything else.

Reliability

• A calmer return — coming back to the app asks the server for far less than it used to, and clients no longer all reconnect at the same instant after a deployment.
• Longer playbooks supported — the ceiling on a skill’s length was raised to fit the procedures real businesses actually write.