Mobile app
The web is the workshop, where you build and configure. The phone is the bridge of the ship: approve, intervene, and check how the business is doing from wherever you are. Nothing on the phone duplicates a web screen; when a task needs the workshop, the phone hands you to the exact tab.
Get it#
- Android: Autoflowly on Google Play
- iOS: in preparation. Until then the web app works well in Safari, and approvals arrive by email too.
Sign in with the same account as the web.
The four tabs#
| Tab | What you do |
|---|---|
| Apps | One card per business: live or draft, a 7-day activity sparkline, money this week, the launch checklist. The card's menu has share, QR code, pause AI team, publish, and open on web |
| Team | Agents on each app and the AI Receptionist's channels; add, remove, pause |
| Inbox | Proposals to decide, customer threads, incidents. Swipe to decide, tap to read and edit |
| Brain | Facts and standing rules, with the ones you just added at the top |
The Create button starts something new: a business system, an app from an idea, a goal loop, or an agent.
Pushes you will get#
| Push | When | Tap to |
|---|---|---|
| Approval needed | An agent proposed something at your "ask" level | Approve or reject from the lock screen (low and medium risk), or open it |
| Money received | A card or mobile-money payment was confirmed | See the job. Test payments in sample mode are marked and never counted |
| Morning briefing | 08:00 your time, only on days with something to say | The summary: messages, bookings, money, what is waiting |
| Weekly report | Monday 09:00 | The week's numbers, and offers to automate kinds of action you keep approving |
| Incident | A new warning or critical problem with an app | The incident, with Fix on web |
| Done automatically | An action ran under a permission you set to auto | The audit entry, quieter than an approval |
| Growth | A budget to approve, a daily change proposed, the goal reached or missed | The Grow screen |
Quiet hours in Settings silence everything except critical incidents.
Deciding safely#
Approving a high or critical proposal (anything with money) asks for Face ID or your passcode before the decision is sent. Rejecting never does. Devices without biometrics fall back to the passcode and are never locked out.
Voice#
Tap the microphone and ask in plain words: "How is my business doing this week?", "What is waiting for me?", "Pause the team on the Leeds shop". You get a spoken answer from your real data, and anything that changes something becomes a proposal.
Hand-off to the web#
When a task needs the workshop, the phone opens the web dashboard at the exact tab: connect payments, edit the database, fix an incident, connect a domain, rewrite a goal. The reverse hand-off is a QR code on the web dashboard that opens the same app on your phone.
Updates#
Most improvements arrive without a store update, the next time you open the app. Features that need new device permissions (biometrics, notification categories) ship through the store.