Technical project case study
A private Slack application was built to structure requests, track supplier orders, monitor services and schedule compliance prompts without turning chat messages into an uncontrolled system of record.
01The operational problem
Operational conversations in chat are quick but difficult to standardise. Requests can omit SKUs, dates or ownership; supplier-order updates become buried in channels; service failures are noticed inconsistently; and recurring compliance checks rely on somebody remembering the calendar.
The answer was not to automate every message. The requirement was to give a small number of repeatable processes a structured form, durable state and a reliable link back to the authoritative warehouse or order system.
02What was built
ECom Clarity built a private Slack app with forms and commands for spares requests, warehouse orders, decisions, refund-response drafting and incidents. Scheduled prompts cover defined compliance activities and operational reminders, while health monitors post only when a service changes state.
For Wicked Costumes orders, the app reads confirmation email, creates or refreshes a warehouse order card and polls Peoplevox every five minutes. The displayed status is derived from Peoplevox rather than a manual progress button.
03Technical design
- Slack Socket Mode application with structured modals, shortcuts, slash commands and thread updates.
- SQLite persistence for workflow state, schedules and observed transitions.
- Gmail polling with mailbox UID checkpoints so messages missed during a restart are recovered.
- Peoplevox purchase-order matching using the customer order reference.
- Europe/London scheduling for working-day reminders, lunch holds and periodic compliance tasks.
- Systemd deployment on an always-on service with environment-managed credentials.
04Controls, failure handling and operational safety
- The app does not archive channels, delete messages, read direct messages or change credentials.
- The first service health check establishes a baseline without posting noise.
- An unmatched Peoplevox reference triggers a private status-check warning rather than a warehouse reminder.
- Duplicate supplier confirmations refresh an existing order card.
- Refund guidance is drafted for review and copying; it is not sent to a customer.
- Compliance and warehouse messages use explicit UK schedules and retained request details.
05Why the design matters
The app makes routine coordination more legible without asking teams to leave the collaboration tool they already use. Structured inputs improve message quality, while source-system polling prevents the chat interface from inventing operational status.
It also demonstrates a practical distinction between notification and authority. Slack tells the right person what needs attention; Peoplevox, the mailbox or the monitored service supplies the fact.
06What this project demonstrates
- Slack workflow engineering connected to live warehouse operations.
- Careful notification timing and escalation design.
- Durable processing across restarts and duplicate inbound events.
- Automation boundaries that preserve review for customer-facing or destructive actions.
07Practical lessons for similar integrations
Chat automation succeeds when it reduces ambiguity, not when it maximises message volume. A state change or exception is usually a better trigger than a fixed stream of reminders.
If Slack displays operational status, the application should be able to explain which source supplied it and when it was last checked.