PRODUCT DIRECTION · 8 OCTOBER 2026

Towards a shared inbox for customer conversations

We want your team to receive and handle enquiries in one place. Each conversation should have an owner, with context still available when it changes hands.

The aim is to bring together email and, later, channels such as WhatsApp and Instagram, alongside follow-up for opportunities and existing customers. We are checking how to do this reliably with little extra work for the team.

What you can try today

The public demo lets you assign a fictional enquiry, change its status and schedule a next action. No account or card is needed. It does not connect inboxes or send messages, and changes reset when you reload.

Try the current demo

Next steps

  1. Understand each team's work

    Research · September to early October

    We review how enquiries arrive, how teams share them and what information is copied between tools.

  2. Review changes with context in view

    Public prototype · fictional data

    Try a review that brings together the original response, a proposed change and a brief reason. You choose whether to confirm or keep the previous context. The example and proposal are predefined: there is no automatic detection or LinkedIn connection. It sends no messages and changes disappear when you reload.

    Try the context review · English interface; fictional conversation text remains in Spanish.

  3. Check real connections

    Internal email, Instagram and WhatsApp pilots · no customer access

    Using our own Instagram test account, we received a real message and sent a reviewed reply from Lead Relay. We also repeated the incoming event under controlled conditions without creating another message in the history. We renewed access and stopped receipt in Lead Relay while keeping recorded messages. Stopping receipt in Lead Relay does not itself revoke Instagram permissions.

    In Gmail, we received a new email during an automatic synchronisation test and sent a reviewed reply from the private inbox. We checked the sent copy and receipt in another account we own. We also checked automatic access renewal after expiry in a bounded production test, without reconnecting the account. We switched off the trial controls afterward. In a further bounded test, synchronisation continued after one real service restart without duplicate messages. Sustained operation remains to be checked; these features are not yet available to connect customer accounts.

    In WhatsApp, we received test messages and sent a reviewed reply from the private inbox. The provider confirmed delivery of that reply. The panel distinguishes an accepted reply from confirmed delivery and does not automatically resend an uncertain result.

    These checks used our own accounts. The public demo still uses fictional data and does not allow account connections.

  4. Offer the interface in more languages

    ES/EN interface published · 9 October 2026

    The website, application interface and help are available in Spanish and English. You can change the interface language. This does not open connections or customer accounts with real data. This change covers the interface and system messages; it does not translate conversations or customer content.

  5. Add channels and customer context

    Future direction · no committed date

    We want to bring email, Instagram, WhatsApp and LinkedIn into a workspace where teams can share conversations and handle both sales enquiries and existing customers. The internal email, Instagram and WhatsApp tests are a first step. They are not yet available for connecting customer accounts. Expansion depends on each provider's official access and the tests we can perform. Personal LinkedIn requires a separate assessment; it is not connected.

What we are learning

One concern raised in conversations is having to copy messages and update another panel. We want to check the extra work each proposal creates before adding features.

We are also testing whether seeing the original response alongside a reason for a change makes decisions clearer. These are research indications, not results from sustained use by teams.

What this roadmap means

We will update the status as we complete connection tests and hear from potential users. Integrations depend on provider conditions and the tests performed. Not every feature of their applications will necessarily be available through Lead Relay.

Purchasing and customer accounts with real data are not open now. Internal tests use an account we own for the pilot. Today's demo is free; that does not set the price or terms of a future service.

Does an enquiry get stuck between team members?

We are looking for examples from service businesses where two people share enquiries or quotes. We can review a general case for free and return a brief proposal using your existing tools, with one follow-up clarification. You do not need to change software.

We do not need account access or customer messages. Tell us what happened last time and how you noticed, without personal data. This review does not include connecting inboxes or ongoing support.

Request a free review

Updates and changes in direction

9 October 2026 · Conversations and opportunities counted separately

The inbox overview separates open and resolved conversations from sales opportunities. Totals respect each member's access and do not depend on loaded pages. An unavailable total is shown as pending, never as an empty inbox. This is a snapshot when the panel loads; it does not confirm active channel synchronisation.

8 October 2026 · Email and WhatsApp tested in the private inbox

We checked reading and recovering a test email, and receiving messages and delivering a reviewed WhatsApp reply. We continue checking access continuity and provider restrictions before offering connections to other businesses. The public demo keeps its fictional data and does not connect accounts.

6 October 2026 · Reply pilot scope

The internal panel distinguishes the Instagram reply flow from features still unverified. Each reply requires review and confirmation, as well as checking the connection, permissions and allowed time window. Instagram accepting a reply does not confirm delivery. We are still preparing this version; it does not open customer access or connections in the public demo.

5 October 2026 · Internal Instagram cycle checked

The internal test account let us check receipt, a reviewed reply and no duplicates when repeating the test event under controlled conditions. Access renewal and stopping receipt in Lead Relay were also checked, keeping the history. The provider subscription is independent of this local stop. This progress does not open customer accounts or change the public demo.

26 September 2026 · Priority: check the work we avoid

The roadmap puts reviewing a concrete case and testing the existing prototype first. We added the intention to offer the interface in more languages. Connections remain under assessment, without a committed date.

16 September 2026 · Context review prototype

The interactive example lets you see the response, proposal and reason together, and confirm or keep the previous context. It uses fictional data only and connects no channels.

We will publish relevant changes here so you can distinguish what you can try from what we are still studying. When a feature changes, we will also update its instructions and the pages presenting it.