# RelayDesk — workflow guide

BEMRIX portfolio concept / Working browser-local automation demo

## Try it
Open /demos/relaydesk/ on the BEMRIX site. The inbox starts with three fictional enquiries. Add your own fictional request, inspect the routing reasons, adjust the owner, edit and save the reply, then approve it locally. Filter the inbox by review status or export the complete workspace as JSON.

## Rules
- Development: website, app, ecommerce, software.
- Design: branding, logo, design, identity.
- Marketing: campaign, SEO, advertising, social media.
- Operations: automation, workflow, integration.
- Multiple matching service areas or no matches: General review.
- Priority: urgent, ASAP or today.

Matching is case-insensitive and uses whole words. It does not infer intent, synonyms, sentiment, dates or negation. A message saying “not urgent” still matches “urgent”. Priority is a review flag, not a delivery promise. The interface explains the original rule results; changing the owner is recorded separately.

## Approval
Drafts begin in Needs review. A person can edit the reply or override the owner. Saving an edited draft or changing the owner requires a fresh approval. Approving a draft marks it Approved locally. Nothing is sent. The local history retains the last 20 events per enquiry.

## Storage and export
Up to 40 enquiries are saved in this browser’s localStorage under bemrix-relaydesk-v1. Browser storage can be cleared or unavailable; in that case work may last only for the current visit. Reset replaces RelayDesk data with the three samples after an inline confirmation. Export creates a JSON download; it does not send anything to a server. Use fictional data. This is not a shared team database or a tamper-proof audit system.

## Implementation
Next.js, React and TypeScript. Deterministic classification and reply templates; no model call, AI service, email delivery or CRM integration. The UI supports desktop and mobile. All case-study screenshots are captured from this working interface.

## A production scope
Agree the enquiry taxonomy and ownership rules with the team. Add authenticated access and role permissions, persistent storage, delivery integrations, verified consent and retention policies, operational monitoring, retry/idempotency handling, and a durable audit log. Measure routing quality on representative enquiries. If AI interpretation is useful, evaluate it against a reviewed dataset, keep uncertain cases in human review and monitor the deployed results.

No client deployment, measured performance improvement or business result is claimed by this concept.