It reads what reaches the project, keeps where it stands current and shows where every line comes from. Nothing leaves until someone on your team sends it.
A project folder and a mail thread are enough to start. Once you connect Outlook, Teams and SharePoint, the project stays current from them, and each project reads only the sources you give it.
Everyone on the project sees the same state. Every statement carries a numbered source with the file, the version and the lines AUVY read, and every version is kept, so you can see what was true when.
AUVY prepares the reply and the next steps, and your client approves by link without an account. You accept, edit or reject every step, and when a step needs a decision the run stops and asks a named person.
Mention a colleague and they join the same AI thread, and you edit documents together live. An outside partner joins one project without seeing the rest of your workspace, and personal notes stay yours.
Describe the tool you need and AUVY builds a working mini-app with its own table, right on the project home. There is nothing to deploy, and every change to the tool and its data has a history.
Make a change log for this project with date, requested by, and status.
| Date | Change | Requested by | Status |
|---|---|---|---|
| 12 Mar | Munich as third site | Client · Ops | Agreed |
| 18 Mar | Go-live to 14 Nov | Client · Ops | Agreed |
| 2 Apr | Extra template | Client · Mkt | Open |
The agent does the follow-up after a change, and bots work beside the team. Both show every step they take and stop for a person before anything leaves.
Give it the follow-up and watch each step until it waits for the right person to decide.
Worked for 1m 9s
Waiting for Anna to accept
A bot is an agent of its own, with its own memory, accounts and processes. You message it or mention it in chat, and it works in each project with that project's permissions.
A process handles the same situation the same way every time. It starts on a mail, a meeting, a date or a change in the data, and anything no process covers still reaches your inbox.
Client moves a date
Example project, synthetic data.
These are the systems AUVY runs on today, on our own servers in Helsinki.
The mail, meetings and files your project runs on. Each project reads only the sources you give it.
Watches the sources you connect and flags what moved: a date, a change in scope, a new requirement.
Your documents, versioned, with search by meaning, so every answer points at the exact version it read.
Reads, cites and prepares the next step, and pauses to ask a named person whenever a step needs their decision.
Picks a model for each job, from a quick one to the most capable, and uses the most capable only when the task needs it. Every call records what it cost.
Someone on the team reads the draft, edits it if needed and sends it.
Your client answers or approves from a link, without an account. The answer is recorded in the project.
Underneath, on our servers in HelsinkiLive collaboration · Sign-in and secrets · Background workers · Databases
AUVY sends nothing on its own and reports only the changes it can see in your sources. It does not decide for you, and it does not replace your ERP or PLM.
On a project with many people, something changes every day: a date in a mail, a decision on a call, a new version of a file. Whoever misses it keeps working from the old plan. However many people work on a project and however fast it changes, AUVY keeps everyone in sync, so each of them builds on the same solid ground.
How it works →AUVY. It syncs the project's Outlook mail and calendars, Teams and SharePoint files into one current state of what is true now, what changed, what it affects and what comes next, each with its source. Nobody types the update in, and the whole team, its agents and bots work from the same state.
How it works →AUVY reads the project's mail as it arrives, so the new scope or the moved date is in the project's state with a link to the mail, and everyone on the project works from it. AUVY drafts the change request and the reply for a person to check and send.
Change requests →