Skip to main content

July 2026

The month agents2.me was born. All of July's work was foundation: the architecture, the authentication, the message data model and the first screens of service and CRM.

31/07/2026 — CRM contacts are born separate from the channel​

New: the distinction that gives the mini-CRM meaning — the channel contact (who wrote) and the CRM contact (the person's record).

  • A CRM contact can gather conversations from several channels; a conversation can exist without a CRM record.
  • Custom fields for contacts, with type, validation and search, from day one.
  • Conversion of a conversation into a contact, preserving the history.

30/07/2026 — Login restrictions by IP​

New: the network barrier at login, per company and per profile.

  • Rules in IP ranges (CIDR) with precedence between the company rule and the profile rule.
  • Temporary block after repeated login attempts from an unauthorized origin.
  • Periodic check of allowed domains, for offices that change their outbound address.

30/07/2026 — Message core and the first queue​

New: the data model that sustains all service and the first queue screen.

  • Separation between channel, channel contact, conversation and message.
  • Conversation lifecycle: enters the queue, is taken, transferred and finished.
  • Queue with members, capacity per agent and the monitoring screen.

29/07/2026 — Users and permission profiles​

New: the product's access control, with section × action granularity.

  • Users screen with invite by e-mail and invite status.
  • Reusable profiles that cut out what each person sees and does — including what a connected AI assistant can answer later.
  • Protected Administrator profile, which the platform uses for sensitive operations.

28/07/2026 — Presence, profile and the app shell​

New: the structure around service: the main navigation, the presence status and the user profile.

  • Presence with online, busy and away — and the direct effect on conversation distribution.
  • Profile with personal data, language and time zone.
  • Single session per device: the same browser does not open duplicate sessions.

27/07/2026 — agents2.me is born​

New: the architecture specification of the omnichannel platform with mini-CRM and the implementation plan that took it from zero to deploy.

  • Monorepo with backend, web applications and shared packages.
  • Backend with per-company isolation from the first table: every query runs with the company context, which guarantees that no workspace sees another's data.
  • Automated testing and continuous build routine set up together with the first code.

27/07/2026 — Login and visual identity​

New: the login screen with the product's split layout, cookie session and password recovery.

  • Planning of login, the post-login shell and the pattern of settings screens.
  • Passwords stored with a hash — no one, not even Soublox, can read them.