Capture the original request
Incoming messages are stored with the source channel, raw payload, attachments, artifacts, and confidence data. The system keeps the original record before proposing summaries or actions.
Workflow
A controlled path from request to resolution.
Meef is designed around the daily rhythm of a dispatcher: capture the issue, decide what is safe, assign the right person, keep customers informed, and preserve the record.
Triage and propose the next move
Agent actions can summarize issues, draft responses, generate reports, and route risky changes to review. The dispatcher sees what the agent proposed and why.
Dispatch under human control
Admins and managers keep direct write authority for create, assign, cancel, escalate, and override operations. Technicians and agents move through controlled workflows.
Execute in the field
Mobile work orders give technicians the job, status controls, equipment context, photos, attendance, and notification flow they need without exposing management-only controls.
Close with proof
Portal activity, quote approvals, invoices, inventory usage, knowledge citations, and generated report snapshots preserve a clean service history for the customer and the dispatch team.
Risk model
Automation moves at the right speed for the decision.
Low risk
Summaries and information retrieval can complete quickly and still record provenance.
Medium risk
Drafts, suggestions, and operational proposals wait for a reviewer before taking effect.
High risk
Customer-facing or billing-impacting changes go through approval and material change history.