Let change requests arrive as ordinary email, with no ticket system and nothing new for your customer to learn. The mail becomes a documented work order, which is carried out and shown on its own preview with test data before anything goes live. A building services firm already works this way and has said so in writing.
The Agentic Part
An agent reads incoming emails from the customer mailbox and treats them as a problem description that still needs to become a documented work item. Before writing anything, it reviews the affected code itself. An agent then carries out the work item and shows the result on its own preview with test data, before anyone approves it.
Main Features
- Fixed order: cause first, then build, test, preview
- Email counts as a problem description that the team still needs to translate into work steps
- Fixed rules for mailbox and data protection
- Fixed reply format for the customer
- Direct read access to the customer mailbox
- Code review before the work item is written
- Dedicated preview environment as the last step before approval
Use Cases
- A customer without their own ticket system sends a short email: the login button on the homepage has stopped responding. That becomes a documented work item that first runs on its own preview with test data, before anything goes live.
- An email only describes what the customer noticed, for example that a page looks wrong. The code is reviewed first, so the work item lands on the right cause.
- A building-services company already works this way and wants replies to customers to always come in the same format. Every email gets a fixed reply format, whoever answers it.
- A smaller change should be allowed to go live without a second review. It is agreed in advance which kind of change qualifies for that.
What we build for you
- Mailbox connection setup
- Preview environment with its own test data
- Agreement on what may skip a second review
- Emails describe the problem, not a finished solution
