Two front doors, and neither is a login page

Think about how much of your working day is spent travelling to where the information lives.

Not physically. Just in tabs. The orders are in one place. The conversations are in another. The report you need is three clicks deep in a dashboard you only open on Mondays. Each trip is short. Together they are most of the day.

We stopped noticing this because there was never an alternative. Software lived somewhere, and you went there. That was simply what using a computer meant.

But here is the interesting part. The two things that changed most about how people work in the last few years, the phone in your pocket and the AI assistant in your browser, both point in the opposite direction. They bring things to you. Nobody goes to their phone. Nobody goes to Claude. They are already open.

So the question for anyone building software is no longer just "what can it do?" It is "where does it show up?"

The FlowIQ app is now on the App Store and Google Play.

It is the whole product, not a cut-down version. Every channel in the one inbox: WhatsApp, Instagram, Messenger, email, and your Shopify or WooCommerce orders alongside the conversation they belong to. Your AI agent answering in the background. Your tickets, with the status and the summary, so you can pick one up from the car park without reading the entire thread.

The part I find myself using most is the quiet part. When the agent hits something it should not answer alone, a damaged parcel, an angry customer, a question about a refund, it opens a ticket, tells the customer a person is on the way, and steps back. That moment now arrives as a notification. You see it. You tap it. You are in the conversation.

Which is the point. Most of the moments that need a human do not happen at a desk. They happen at 7am, or in the queue at the post office, or on a Saturday. The app puts the inbox where those moments actually are.

The second door needs a little more explaining, so let me try it the way I would to a friend.

MCP stands for Model Context Protocol. It is a plain, open standard that lets an AI assistant use another piece of software on your behalf. Claude supports it. ChatGPT supports it. Most of the serious AI tools do now. Think of it as a set of hands the assistant can borrow.

FlowIQ now has an MCP server. Connect it to your account, and Claude or ChatGPT can see your contacts, your conversations, your campaigns, your tickets and your agent's own instructions, and do things with them. Not by pretending to click around a screen. Through a proper, named set of actions we built for exactly this.

So you type something ordinary, and it does the work.

When we switched this on for the first accounts, the requests were not clever. They were the questions people had always wanted answered and never had time to go and look up.

What did customers ask for last week that we do not stock? How did our AI agent perform last month? Did we get any Instagram messages from influencers yesterday? What is our average response time after an escalation? Which campaign brought in the most orders this month? How many abandoned carts did we recover today?

Then, once the reading feels normal, the doing starts.

Build a segment of everyone who has ordered twice, but not in the last 100 days. Send the Heritage Day campaign to them. Create a replenishment flow for three months after purchase. Send a discount code to everyone affected by the courier delays this week. Update the agent so it stops promising next-day delivery.

Every one of those is a real thing the connection can do today. And every one of them used to be a trip to the software.

This is the part I would want to know if I were reading this as a customer, so I will be plain about it.

Reading is instant. Ask for a report, a contact's history, a ticket, a broadcast's numbers, and you get them.

Changing things is two steps, on purpose. Anything that sends a message to a customer, or changes what your agent says on your live number, first shows you exactly what will happen. The audience and its size. The template. The diff of the instruction it wants to change. Then it stops and waits. Nothing goes out until you say yes to that exact thing.

A WhatsApp message cannot be recalled. An agent instruction is live the moment it changes. Those two facts shaped the whole design. An assistant that could send on its own would be faster, and nobody would trust it, and they would be right not to.

What surprised me is how natural the pause feels. You describe the change. You look at it. You say yes. It is closer to how you would brief a person than to how you use a dashboard.

Put the two side by side and the pattern is hard to miss.

The app takes FlowIQ to the place you already are when you are away from a desk. The MCP server takes FlowIQ to the place you already are when you are at one. Neither asks you to go anywhere. Both meet you where the work is happening.

For a long time, a product's front door was its login page. You arrived, you did your work inside, you left. I think that is quietly ending. The products that matter are becoming the ones that show up inside the phone, inside the assistant, inside the conversation you were already having.

Same FlowIQ behind both doors. Same inbox, same agent, same tickets. Just fewer trips to get there.

Maybe that is the whole shift. Not smarter software. Closer software.