Two Products You Can Open And Test Right Now
EzyConn answers customer support questions. EnsureFix turns tickets into pull requests. We wrote both, we run both, and one of them is running on this page while you read it.
Most of what we build carries somebody else's name. Two things carry ours.
From this repository.Illustration.
EzyConn and EnsureFix are AI products we wrote, and we are the ones on the phone when a queue backs up at three in the morning. Operating your own software teaches you what handing it over never does: what an upgrade really costs on a working Tuesday, which alerts are worth waking somebody for, how a database decision made in the first month behaves in the eighteenth.
Both are live products with their own sites. Go and use them, then judge the rest of this site on what you find.
EzyConn
Customer support, answered from your own documents.
- Host
- ezyconn.com
- Pricing
- Free tier, unlimited teammates on every plan
- Channels
- Web chat, Teams, Slack, WhatsApp, Messenger, email, SMS
- Running
- On this page
Fig. 01Seven channels in one inbox, an answer citing the documents it came from, and a handover to a person.
This figure is a drawing of the product interface, not a photograph or a screen capture.
Entry
01
Open ezyconn.comThe product itself, in a new tab, so this page can be checked rather than believed.
How it works
Give it a website address, a Zendesk help centre, or upload PDF and Notion documents. It crawls what is there and builds its own index. Nobody has to sit down and type out an answer bank first.
Website chat is a single script tag in your page. Teams and Slack connect instead of embed, so your staff answer from the app they already have open all day.
It replies from the indexed content, in whichever channel the customer used. The answer comes from what you published, so a policy you changed last week is the policy the customer hears about.
The moment a conversation needs judgement it goes to a human, with the full transcript attached. Nobody has to ask the customer to explain it again from the start.
Routing is built in a visual workflow builder. You drag the path a conversation takes. There is no code to write and no ticket to raise with us when you want to change it.
What it connects to
- Website chat
- Microsoft Teams
- Slack
- Messenger
- SMS
- Zendesk help centre
- Notion
- PDF upload
What it does
- 01One shared help desk inbox for every channel, instead of a separate queue per platform
- 02A knowledge base that builds itself by crawling your site, your help centre and the documents you upload
- 03Handover to a person with the whole conversation attached
- 04A visual workflow builder for routing, with no code to write
- 05Analytics on resolution rates, team efficiency and customer sentiment over time
- 06Unlimited teammates on every plan, so the bill does not grow every time you hire
- 07A free tier, so you can try it before anyone signs anything
Control
What Happens To Your Data
Support conversations carry card numbers, home addresses and complaints, so this part matters more than the feature list does.
- AES 256 encryption at rest, TLS 1.3 in transit
- Row level tenant isolation, so one company's records cannot be reached from another company's session
- Card numbers and personal identifiers masked automatically
- Audit logging, so there is a record of who looked at what
- Retention you choose: 30, 90 or 365 days, or keep everything
- Your customer data is not used to retrain models
Verify
This Site Is Running It
The chat launcher in the corner of this page is EzyConn. It is loaded by this site's own layout from api.ezyconn.com, and it answers from the pages you are reading, which is the same thing it would do on yours.
Open it and ask it something about this company. Whatever it says back is the product, working on the material we gave it, with nobody standing behind it typing.
From this repository.
src/app/layout.tsx
<Script
src="https://api.ezyconn.com/api/v1/widget/script.js"
data-widget-token="your token"
data-theme="dark"
strategy="afterInteractive"
/>EnsureFix
Tickets in one end, reviewed pull requests out the other.
- Host
- ensurefix.com
- Input
- Jira, GitHub, Azure DevOps
- Output
- A reviewed pull request
- Stages
- Five, and you choose which stop for a person
Fig. 02A ticket entering five stages, the change it made, and the review waiting on you.
This figure is a drawing of the product interface, not a photograph or a screen capture.
Entry
02
Open ensurefix.comThe product itself, in a new tab, so this page can be checked rather than believed.
How it works
A webhook from Jira, GitHub or Azure DevOps hands over the ticket. Nothing is copied and pasted, and nobody has to remember to start it.
Multi file changes, in the shape your repository already uses. You can ask it questions about the repo while it works, and the answers come back with the files behind them.
When a test fails it goes back and repairs the change, and it recovers the same way from a failed CI run. Where the code it touched has no tests, it writes them.
Inline comments on the change itself: style violations, best practice notes, a severity score, and auto fix suggestions that arrive with the patch already attached.
Auto merge runs on confidence, and you set where the bar sits. Pick which of the five stages run on their own and which stop and wait for a person to look.
What it connects to
- Jira
- GitHub
- Azure DevOps
- Your CI pipeline
- Playwright
What it does
- 01Security scanning on every commit: SAST with CWE tracking, hardcoded secrets and API keys, SQL injection and cross site scripting
- 02Configuration scanning for insecure Dockerfile, Terraform and Kubernetes settings
- 03Vulnerable dependency checks and licence compliance
- 04UI bugs reproduced in Playwright, with screenshots, console output and network traffic captured
- 05Repository question answering that cites the files behind the answer
- 06Tests written for code that arrived without any
- 07DORA metrics: deployment frequency, lead time, change failure rate and mean time to recovery
Control
What You Keep Control Of
Software that writes software is only useful if you can say where it stops, so the pipeline runs in five stages and you choose which of them are automatic.
- Confidence based auto merge, with the bar for each stage set by you
- Every decision comes with the reasoning behind it, so reviewing is reading rather than guessing
- Reviews land inline on the diff, in the tool your team already opens
- It tracks which of its fixes you accept and which you reject, and adjusts to match
What Building These Taught Us
Four things that show up in client work, each one testable on your own project rather than a nice sentence about ourselves.
- 01
Support Is Where Software Gets Judged
Every gap in a product turns up in the support queue before it turns up anywhere else. Running EzyConn means we read those queues. It changes small things: error messages get written for the person who will paste them into a chat window at midnight, not for the developer who caused them.
- 02
Reviewing Diffs All Day Changes How You Write
EnsureFix reads pull requests for a living. Building the thing that finds the hardcoded key, the missing test and the injection risk made those the first three things we look for in our own work, well before a client ever has to raise them.
- 03
Shipping Weekly Keeps You Honest
Two products with real users on them means we release on a schedule and roll back when a release goes wrong. Your project gets that same pipeline. We are not working it out for the first time on your budget.
- 04
You Can Check This One Yourself
Most software companies ask you to trust a case study with the client's name taken out. These two have addresses. Open ezyconn.com or ensurefix.com and use them.
Tell Us What You Need Built Or Fixed
Write down what you are dealing with, in your own words. We will tell you whether it is work we do and what it would take.
What You Get
- Scope agreed before we start
- One team, not three suppliers
- You own the code and the accounts
- Plain answers about cost
- Support after it goes live
- Work you can hand to someone else
What Happens Next
- 1We call you at a time that suits you
- 2We ask what you have now and what is going wrong
- 3We send back a scope and a price
Tell Us About Your Project
Every enquiry gets a reply within one working day.