Skip to content
2026.8.19

Messages can start with @ again

A quick follow-up to the private side channel: a message that begins with an Instagram handle sends normally, and production errors now raise an alert.

  • messaging
  • hotfix
  • reliability

A small follow-up to yesterday’s release. The new @ shortcut for addressing your teammate was catching messages that merely started with an @ — an Instagram handle, for instance — and locking the send button. The picker now follows the match, not the symbol.

Composer

  • @handle sends — a leading @ that matches no teammate, like @alluringplasticsurgery, no longer disables Send or swallows Enter. It goes to the contact as ordinary text.
  • Escape keeps your draft — dismissing the teammate picker preserves every character, the @ included.
  • No teammate yet? Choose one — typing @ on a contact nobody is handling offers a Choose a teammate action right there instead of a dead end, and Send stays live.
  • One rule everywhere — the compact send button, the modal, the preview card and ⌘/Ctrl+Enter all follow the same rule, and a failed teammate lookup shows a visible Try again.

Reliability

  • Production errors raise an alert — server errors are now grouped and alerted on, and logs can be searched by organization, call and contact, with credentials scrubbed before anything leaves the server.
  • Meta deliveries kept for diagnosis — every verified delivery from Meta is kept byte-for-byte for 30 days, so a message shape we haven’t seen before — like the ad DMs that arrived without their referral — can be inspected instead of guessed at.

← 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.