Outlook add-ins — where the email stops being the end of the line.
A panel inside Outlook that turns the open email into what it should have produced: a ticket, a task, a record in the ERP. No copy and paste, without leaving where the work happens.
Email is where work arrives and, very often, where it stays. Someone reads a request, opens another tab, looks up the customer, copies the subject, pastes the body, picks a category and creates the ticket — two minutes per email, dozens of times a day, and one in five never gets logged at all. An add-in fixes this where the problem happens: inside Outlook.
What we build
From the email to the system, in one click
The panel reads the open email — sender, subject, body, attachments — and fills in what it can. The person confirms category and priority, clicks once, and the ticket exists. What took two minutes becomes a gesture.
Built for the system you already have
Freshservice, Freshdesk, Jira, in-house ERPs, internal databases. We connect through the API where there is one and build the bridge where there isn't. We have shipped an add-in that opens Freshservice tickets and another that creates tasks in an internal management app.
Works everywhere Outlook works
Windows, Mac, browser and phone. A modern add-in is HTML and JavaScript served over the web, with a manifest Outlook reads — not an installer IT has to push to a hundred machines.
Two things you learn the second time round
The API key cannot live in the browser
An add-in runs on the user's machine. Putting the ticketing system's API key there hands it to anyone who opens the developer tools. We always build a middleware in between: the add-in talks to it, it talks to the system, and the key never leaves the server.
Outlook Web lives on another domain
The panel runs on outlook.office.com, and most APIs refuse requests coming from there. Without a service of your own in the middle, the add-in hits CORS and no setting will fix it — the missing piece has to be built.
How it goes
- A short conversation about what arrives by email and what should happen next.
- A working add-in, wired to your real system — not a mock-up.
- Deployed across the organisation by your Microsoft 365 admin, to everyone or to one group.
- Handed over with the code and whatever it takes to keep it running without us.
How long
From one week, fully working, in production and with documented tests. The real timeline depends on the system at the other end — a documented API and a legacy ERP with no interface at all are not the same job, and we say which one it is before starting.