Native apps and billing controls

Thirteen changes shipped in this release. Loquent became a real mobile app, plan and credit management moved into the product, and email joined the channels that can carry AI reply suggestions.

Mobile apps

• iOS and Android — the app now runs natively on both platforms with the full product inside it.
• Push notifications — inbound messages push to the device with badge counts that resync on open and clear when a conversation is read.
• Deep links — tapping a notification, or a Loquent link from another app, opens the right conversation.
• Native touches — haptic feedback on save, send, and confirm, comfortable tap targets, momentum scrolling, and keyboard-aware inputs.
• Stay signed in — the session survives app launches, so signing in is a one-time step.

Plans and credits

• Change plan in the app — owners can switch plans without leaving Loquent, with proration invoiced immediately on an upgrade and deferred on a downgrade.
• Clear feature gating — features that belong to a higher plan explain themselves with a contextual upgrade path, and someone without billing rights is told to ask their owner instead of hitting a dead end.
• Credit auto-recharge — when the balance falls below a threshold you set and an operation actually drew from general credits, a saved card tops it up. Repeated failures disable it automatically and explain how to recover.
• Seat capacity enforced — members plus pending invitations can no longer exceed the seats you pay for. The team page shows live capacity, and an at-capacity organization gets an upgrade path in place of the invite form.
• Per-feature spend — the current-cycle breakdown expands into per-feature AI spend with each feature’s share, instead of one opaque bucket.
• A stable allowance — the included-credit figure is snapshotted at the start of the cycle, so a mid-cycle change no longer rewrites what you were promised.

Messaging

• AI suggestions on email — email joins text as a channel that can have an agent assigned, and its suggestions are written as emails, with a greeting, paragraphs, and a sign-off, rather than one-line text messages.

Reliability

• Database connections repaired — the connection pool is created once per process and closed cleanly on shutdown, ending a steady stream of reset-connection errors in production.
• Leaner production builds — release profiles tuned for smaller, faster binaries, with build warning noise removed so real problems stand out.