Case Study
Case Study: IoT Cold-Chain Monitoring & Support Automation
We built a connected set of automations for a company selling wireless temperature sensors to food distributors and cold-storage sites: cold-chain excursion detection and records, offline device and gateway monitoring, an AI support agent for troubleshooting and RMA intake, and a CRM that links pilots and active fleets to sales. Customers now hear about problems from the company first, and support works from complete cases.
- Business type
- Connected temperature sensor company serving food distribution and cold storage
- Team involved
- Founders, support lead, ops lead, quality adviser, sales
- Systems connected
- IoT platform, LoRaWAN network server, help desk, CRM, SMS, n8n
- Delivery
- Scrum, 1-week sprints, about 8 weeks to full launch
The challenge
Where the practice started
Customers checked temperatures on the vendor portal when they remembered, so excursions were often found after the fact and records were assembled by hand.
Gateways losing power or connectivity went unnoticed until a customer asked why their dashboard was blank.
Support answered the same pairing and connectivity questions daily, and RMA requests took several messages to get a serial number, photos and purchase date.
Sales tracked pilots in a spreadsheet and did not know which pilot sites had gone live or gone quiet.
Goals
What the project had to change
- Excursions are detected while there is still time to act, and every excursion has a consistent record.
- Offline gateways and devices are found by the company before customers notice.
- Routine support questions are answered from approved guides, and RMA cases arrive complete.
- Sales and support see each account with its pilot status and active devices.
What we built
What we built, as one connected system.
Cold-chain excursion records
We connected sensor readings to per-product limits set by the quality adviser, added alerts with escalation to each customer's chosen contacts and built an excursion record that fills in as people act.
Service detailsOffline monitoring
Each device and gateway was given its expected interval, heartbeat checks group silent devices by gateway and site, and support gets one ticket per incident with optional customer notices.
Service detailsSupport and RMA agent
A website and help desk agent answers from approved guides per model, checks device status read-only with the serial number and collects everything needed for an RMA, including the warranty date.
Service detailsFleet CRM
Trial requests and orders link to device activations, and sales is alerted when a pilot goes live, stalls or expands.
Service detailsArchitecture
How the company's workflows connect
- Input
- Logic and services
- AI step
- Data
- People
How it flows
- 1 Sensors report through the LoRaWAN network to the IoT platform; trials, orders and support requests arrive from the website.
- 2 n8n runs the excursion, offline and CRM workflows, and the support agent answers customers and builds RMA cases.
- 3 Tickets, excursion records and RMA cases land in the help desk; accounts and pilots live in the CRM.
- 4 Ops and support act and approve; the quality adviser sets limits and decides disposition.
How it behaves
How the system behaves day to day
What customers see
- Excursion alerts while there is time to act
- A heads-up when their gateway goes offline
- Fast answers to setup questions and one-conversation return requests
What the team sees
- Excursion records and offline incidents as tickets
- Complete RMA cases to approve
- Pilot status on every account
What the automation does
- Detects excursions and silence on schedule
- Answers from approved guides and collects RMA details
- Never decides product disposition, returns or refunds
Edge cases and fallbacks
- A logger has a data gap
- The excursion record marks missing data rather than in range.
- A whole site goes quiet
- Grouped as one gateway incident and the customer is told once.
- A customer reports smoke or heat from a device
- Immediate hand-off to a person with approved safety wording.
- A possible security vulnerability is reported
- Routed to the published security contact at once.
- n8n or the platform API is down
- Platform email alerts stay on as a fallback and the ops lead is told.
Integrations
What we connected
AWS IoT Core
IoT platformThreshold events, device status and readings for alerts, offline checks and dashboards.
AWS IoT rule actions such as HTTPS, Lambda, SNS and Timestream.
The Things Stack
LoRaWAN network serverUplinks and last-seen times for LoRaWAN sensors.
The Things Stack webhooks.
Zendesk
Help deskTickets, offline incidents and RMA cases.
Zendesk Ticketing API.
HubSpot
CRMAccounts, pilots, deals and device activation fields.
HubSpot CRM REST API.
Twilio
SMSOn-call texts, excursion alerts and acknowledgements.
Twilio Programmable Messaging API.
n8n
Automation platformRuns the workflows, self-hosted or on n8n Cloud.
Your own n8n instance; we hand over every workflow.
How we delivered it
Week by week, one workflow at a time.
Delivery timeline
Typical time to launch: about 8 weeks, then support
-
01
Discovery
Week 1
We mapped readings, gateways, support topics, the RMA process and sales stages, and the quality adviser set product limits.
-
02
Design and access
Week 2
Read-only platform access, device inventory with intervals, alert chains, guide library outline and CRM fields.
-
03
Sprint 1: offline monitoring
Week 3
Built heartbeat checks and gateway grouping, shadow-ran against known outages.
-
04
Sprint 2: cold-chain records
Week 4
Offline tickets went live. Built excursion detection, alerts and records with alerts to a test channel.
-
05
Sprint 3: support agent
Week 5
Excursion alerts went live for one customer. Built the agent, guide library and status lookup.
-
06
Sprint 4: RMA intake
Week 6
Tested the agent on real questions. Built RMA intake, warranty lookup and help desk cases.
-
07
Sprint 5: fleet CRM
Week 7
The agent soft-launched on one product. Built the CRM sync and pilot alerts.
-
08
UAT and handover
Week 8
The team ran acceptance tests on every workflow, then we switched everything on and handed over run books.
-
09
Support
Ongoing
Weekly check-ins during stabilisation, then monthly care.
Who does what
What the team does, and what automation does.
Automation does
- Detects excursions against product limits and alerts the right people
- Builds excursion records as people act
- Checks every device and gateway against its expected interval
- Answers setup and troubleshooting questions from approved guides
- Collects serial numbers, photos and warranty dates for RMAs
- Links device activations to CRM accounts and flags pilot changes
The team does
- Respond to excursion alerts and record actions
- Investigate offline incidents and contact sites
- Approve RMA cases and replacements
- Follow up pilots that go live, stall or expand
Engineer or ops lead decides
- Sets product temperature limits and allowed durations
- Decides product disposition after an excursion
- Approves out-of-warranty exceptions and refunds
- Handles safety concerns and security reports
Compliance handled
Privacy, consent and safety, built in.
Temperature control during transport
Excursion records support customers' obligations under the FDA sanitary transportation rule for adequate temperature controls.
Source: www.fda.govRecords on request
Records are stored by shipment and site so they can be produced quickly, in line with the 24-hour expectation in the FDA Food Traceability Rule.
Source: www.fda.govAI disclosure
The support agent tells customers it is automated, in line with Article 50 of the EU AI Act.
Source: artificialintelligenceact.euSecurity reports to people
Vulnerability reports go to the published security contact, reflecting UK PSTI and EU Cyber Resilience Act reporting expectations.
Source: digital-strategy.ec.europa.euProcessors under contract
The automation host and model provider are covered by GDPR Article 28 processor contracts.
Source: gdpr-info.euOutcomes
What changed for the practice
- Excursions now reach the right person while there is still time to act, and each one has a consistent record.
- Offline gateways are found by the company before customers notice, as one incident per site.
- Routine setup questions are answered from approved guides, and RMA cases arrive complete.
- Sales sees which pilots have gone live, stalled or expanded without asking support.
What we track
The measures the practice watches.
Excursion response
Time from excursion start to acknowledgement, and excursions resolved before product was affected.
Offline detection
Time from silence to ticket, and incidents reported by customers first.
Support deflection
Conversations resolved without a ticket.
RMA completeness
RMA cases created complete first time and time to decision.
Pilot conversion
Pilots live, stalled and expanded each month.
Cost estimate
What a project like this costs
-
Discovery and design
Process mapping, limits, data flows and the backlog for all four services.
$1,000 – $2,000
-
Offline monitoring module
Inventory, heartbeat checks, grouping and tickets.
$700 – $1,700
-
Cold-chain module
Detection, alerts, escalation and excursion records.
$800 – $2,000
-
Fleet CRM module
Order and activation sync and pilot alerts.
$700 – $1,600
-
Support and RMA agent
Agent service, guide library, status lookup and RMA intake.
$1,800 – $5,500
-
Integrations
IoT platform, network server, help desk, CRM and SMS.
$200 – $700
-
Testing, UAT and launch
QA, acceptance testing, launch and training.
$300 – $1,500
-
Total project estimate
$5,500 – $15,000
Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: three workflows at our fixed per-workflow range plus an AI support agent. Every company gets its own fixed quote after a free call.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
- IoT platform and network: Each vendor's own plan.
- SMS and model usage: Per-message SMS rates and pay-per-use model fees, usually modest at this scale.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
Tools we built
Free tools we built and use every day.
The Make It Flow platform
Website audits, monitoring and reports
- Website Monitoring Scheduled re-scans, score emails and 5-minute uptime alerts
- Website Security Scan FreeSSL, security headers, cookies and exposed file checks
- Email Deliverability Check FreeMX, SPF, DKIM, DMARC, MTA-STS and BIMI with ready DNS fixes
- DNS Health Check FreeNameservers, SOA, CAA, MX, TXT records and DNSSEC validation
- Website Audit API Queue scans and read results via REST API with signed webhooks
- White-Label Reports PDF reports with your logo, name and color, and shareable links
Free website tools for practices
Services in this case study
Cold-chain temperature excursion records
Detect temperature excursions from loggers and trailer sensors, alert the right people while there is still time to act, and assemble an excursion record with readings, actions and decisions for customers and auditors.
From $1,000 · About 4 to 5 weeks Details
Offline device & gateway monitoring
Compare every device and gateway with its expected reporting interval, catch silent devices before customers do, separate gateway outages from single devices and open a ticket or customer notice with history.
From $1,000 · About 4 weeks Details
AI support agent for troubleshooting & RMA intake
An AI support agent that walks customers through device setup and troubleshooting from your approved guides, checks device status, collects serial numbers and photos for RMAs and hands a complete case to your team.
From $2,500 · About 5 to 8 weeks Details
IoT CRM: trials, activations & fleet accounts
Link trial signups, device activations and fleet size to one CRM, flag accounts whose devices go live, automate follow-ups and keep every customer record tied to the devices they actually run.
From $1,000 · About 4 weeks Details
Engineer or ops lead decides
-
AI in Manufacturing: RFQs, Order Entry, Quality Docs and Maintenance LogsAutomation · 8 min read
-
Logistics Automation for UK Hauliers: Bookings, PODs and Compliance AdminAutomation · 8 min read
-
Automate Website Monitoring for Free: Uptime, Audits and AlertsAutomation · 10 min read
-
Website Monitoring Guide: What to Watch After Your Site LaunchesGuides · 8 min read
-
How to Format JSON and Fix Common JSON Validation ErrorsGuides · 6 min read
-
What Are AI Agents? A Plain-English Guide for Small BusinessesAutomation · 10 min read
-
Manufacturing SEO: How B2B Manufacturers Get Found by BuyersSEO · 10 min read
Free 20-minute call
Want this built for your iot & connected device?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
Sources we checked
Rules and product facts on this page come from these pages, checked in November 2026. This is general information, not legal advice; confirm the rules that apply to your practice with your own adviser.
- European Commission: Cyber Resilience Act summary
- European Commission: Data Act
- Matheson: Data Act access-by-design requirement
- GOV.UK: The UK PSTI product security regime
- FDA: FSMA sanitary transportation rule
- FDA: Food Traceability Rule
- EU AI Act, Article 50
- GDPR Article 28 (processors)
- FTC: CAN-SPAM Act compliance guide
- UK PECR regulation 22
- W3C WCAG 2.2
- AWS IoT rule actions
- Microsoft Learn: What is Azure IoT Hub?
- ThingsBoard REST API
- The Things Stack: webhooks
- Particle: webhooks
- n8n: MQTT Trigger node
- Zendesk Ticketing API
- n8n pricing
- Google autocomplete phrasing checked for keywords (iot device monitoring, iot dashboard development, predictive maintenance iot, cold chain monitoring, temperature excursion, rma process)