Building a Zendesk replacement with AI: 24 checks and 21 spec gaps

Description and use

<h2> The short answer </h2> <p>Yes, for a small team answering support email. We gave Claude, working in Type, our <a href="https://personalsoftwarefactory.com/blueprints/help-desk" rel="noopener noreferrer">Help Desk blueprint</a> and had it follow the four phase prompts in order. The final build passed <strong>24 of 24 acceptance checks</strong> in one browser run on a fresh database, with <strong>64 automated tests</strong>. It handles tickets from email and a web form, Zendesk's six statuses and lifecycle rules, public replies and internal notes, email threading, first-response targets, ca

Problem

<h2> The short answer </h2> <p>Yes, for a small team answering support email. We gave Claude, working in Type, our <a href="https://personalsoftwarefactory.com/blueprints/help-desk" rel="noopener noreferrer">Help Desk blueprint</a> and had it follow the four phase prompts in order. The final build passed <strong>24 of 24 acceptance checks</strong> in one browser run on a fresh database, with <strong>64 automated tests</strong>. It handles tickets from email and a web form, Zendesk's six statuses and lifecycle rules, public replies and internal notes, email threading, first-response targets, ca

Outcome

<h2> The short answer </h2> <p>Yes, for a small team answering support email. We gave Claude, working in Type, our <a href="https://personalsoftwarefactory.com/blueprints/help-desk" rel="noopener noreferrer">Help Desk blueprint</a> and had it follow the four phase prompts in order. The final build passed <strong>24 of 24 acceptance checks</strong> in one browser run on a fresh database, with <strong>64 automated tests</strong>. It handles tickets from email and a web form, Zendesk's six statuses and lifecycle rules, public replies and internal notes, email threading, first-response targets, ca

Evidence

Building a Zendesk replacement with AI: 24 checks and 21 spec gaps

Source