Seventeen engineers alerted in fifteen seconds for SAMA Consulting
SAMA Consulting keeps Infor ERP systems running for aerospace, automotive and heavy-equipment manufacturers. When a production line stops, every minute costs its client millions, and the fix starts with the right engineer waking up. Joe now alerts all 17 of them on WhatsApp, by voice call and by email at once, in under 15 seconds, at any hour.
The business, in brief.
SAMA Consulting, based in San Jose, does one thing: Infor ERP for heavy industry. Implementations, integrations and managed support for aerospace, automotive, construction and heavy-equipment manufacturers, the systems that run their clients’ production lines.
Support like that has no closing time. SAMA keeps engineers awake across timezones so that someone is always on duty, because the systems they watch do not fail politely between 9 and 5.
What they were up against.
When an incident hits a monitored production line, the next two minutes decide everything. A line standing still costs the client millions, and the repair clock only starts when an engineer is actively on the problem. The alert chain was the weak link: a message to one person can land on a silenced phone, a group chat can sit unread, an email can wait until morning. Any single channel, and any single person, is a point of failure you find out about during the incident.
Minutes priced in millions
A stopped line burns money until someone competent is working on it. The delay between detection and an engineer engaging was the one part of the response SAMA did not fully control.
One channel is a single point of failure
A phone on silent, a WhatsApp outage, an email filter: any one of them could quietly absorb the alert. The failure mode was invisible until the exact moment it was catastrophic.
Human relays do not scale to 3am
Waking the team by hand means one person calling seventeen, one by one, across timezones. That person is now the bottleneck of a response measured in seconds.
The work, off their plate.
Joe usually answers the conversations customers start. SAMA hired him for the opposite job: to start one, everywhere at once. The moment an incident is detected, Joe fires WhatsApp messages, voice calls and emails to all 17 people on the escalation list simultaneously, mixing the channels so that no single outage, silenced phone or full inbox can mute the alarm. On a normal day the system says nothing at all.
Three channels per person, at once
Every engineer on the list gets a WhatsApp message, a voice call and an email in the same instant, 51 simultaneous contacts per incident. One channel down, two still ring.
Under fifteen seconds, around the clock
From incident detected to the first phones lighting up: less than 15 seconds, at 3pm or 3am. The team is spread across timezones, so someone awake is always among the seventeen.
Silent until it matters
The target is zero notifications. Joe sends nothing on a normal day, so when he does ring, nobody has learned to ignore him. An alert from Joe means a line is down, now.
Setup, not a project.
Wired the incident feed to Joe
The monitoring systems that watch the production lines now hand every detected incident straight to Joe over API, with the context an engineer needs to start working attached.
Wrote the escalation list once
Seventeen people, their numbers, their addresses, their timezones, in one place. One list drives all three channels, so keeping it current is one edit, not three.
Mixed the channels on purpose
WhatsApp, voice and email fire together, not in sequence. The design assumes any one channel can fail at the worst moment, and makes that failure cost nothing.
One escalation list, three channels, one rule: silence until a line stops.
Your version of this story starts this afternoon.
Hire Joe today. The first conversation gets answered tonight.
400 credits on us for 7 days to decide if he keeps the job.