What happens after the alert?
The network goes down. SmartTile detects it, opens the ticket in the customer’s ITSM system, gets the carrier ticket opened — by API where the carrier has one, by Joey, our AI voice agent, where it does not — and writes every note until the monitor proves the circuit is back.
Is operational complexity consuming your team’s time?
Detection isn’t the problem. The manual work after the alert is, and that’s where network operations automation pays off.
More sites, same team
Locations, acquisitions and vendors keep growing. Headcount doesn’t.
Too many disconnected tools
Network, cloud, carrier and ITSM platforms don’t talk, and stale documentation leaves engineers hunting for context.
Carriers eat the day
Opening cases, waiting on hold and chasing updates pulls skilled engineers away from real work.
Faster resolution, no extra capacity
Leadership wants quicker fixes and better reporting without adding workload.
How SmartTile eliminates your operational complexity
SmartTile sits above the tools you already run and automates the work that follows every alert, from the device to the carrier to your ticketing platform.
DeviceAutomate
Every device, one current view
Syncs your network and security devices into a single live inventory, tracks every state change and runs scheduled fleet firmware updates, so new sites don’t mean new manual work.
See integrationsCarrierAutomate
No more time on hold
Opens and works carrier tickets through API or AI voice agent, then tracks every update to restoration. If a ticket can’t be established, our 24/7/365 U.S. NOC takes over.
See integrationsServiceAutomate
Tickets that arrive ready to work
Creates and enriches tickets in the ITSM platform you already use, adding site, circuit, device and contact context automatically so engineers skip the hunt and start the fix.
See integrationsBuild your stack.
See what SmartTile automates.
Drag the tools your IT team runs today into your stack, or click to add them. SmartTile shows which automations switch on for your environment.
Integrations
Your IT Stack
Drop your integrations here
Start with your firewalls, carriers and ticketing platform. You can also click any tool to add it.
Automations switched on 0 of 6 automations active
Like what you built? Send us your stack and we’ll map a SmartTile rollout for one high-friction workflow in your environment.
Get my stack reviewAutomations that handle the work after the alert
Pick any automation to see the problem it solves, exactly what SmartTile does step by step, and what it has delivered in production.
Devices & Infrastructure
FirmwareAutomate
The problem
Every vendor ships firmware on its own schedule, and nobody can watch six release feeds and patch on time.
How it works
- Every 10 minutes, compares each device’s firmware with what the vendor offers.
- A newer build raises an advisory with a 14-day SLA.
- Opens a ticket in your connected ITSM system and emails site contacts.
- Your team picks the maintenance window, and the ticket is updated when it’s set.
- Verifies the running version after the upgrade. A match closes the ticket; a mismatch is flagged within 4 hours.
In production: 122 firmware advisories raised, with 58 tickets opened for them.
AccessAutomate
The problem
Who signed in to the firewall at 3 a.m.? Usually nobody knows until the audit.
How it works
- Every 5 minutes, reads admin activity from Cisco FMC, the Meraki dashboard and UniFi controllers.
- Checks each login against your list of authorized admins.
- An unknown admin or 3 or more failed logins opens a ticket and emails your chosen contacts.
- Every event and verdict exports to CSV as SOC 2 evidence.
In production: 102 admin access events recorded from 7 management planes, each with its verdict.
Config Backups
The problem
The configuration you need after a bad change is the one nobody saved.
How it works
- Every 20 minutes, reads the configuration of each device with backups enabled.
- Compares it with the last saved copy. No change means nothing new is stored.
- A change saves a new version with a line-by-line diff.
- Real changes can open a ticket automatically when auto-ticketing is on.
- Three failed backup runs send an alert email, with one more on recovery.
In production: 5,638 configuration versions saved, each change with its diff.
Network Diagrams
The problem
A site diagram drawn by hand is out of date the day after the next install.
How it works
- Drawn from each location’s device records (carrier, gateway, firewall, switches and access points) and colored by live status.
- Every device is labeled with vendor, model, circuit ID, IP, latency and loss.
- Dual-WAN gear appears as one box listing every WAN IP with its carrier.
- Each time a diagram opens or refreshes, the file is saved to the location’s Documents.
- With IT Glue connected, the diagram is pushed to the mapped organization.
In production: 68 location diagrams kept current, with no one redrawing them.
VPNAutomate
The problem
A site-to-site tunnel can drop while both firewalls stay green.
How it works
- Lists every tunnel: Meraki AutoVPN, Meraki third-party IPsec peers and SmartTile-provisioned tunnels.
- Polls every 60 seconds. You choose which tunnels to watch and how long counts as down (3 minutes by default).
- Past that window, opens one ticket with both sites, the peer and the drop time, and emails your chosen contacts.
- When the tunnel recovers, a note is added and the ticket closes after 10 minutes of stability.
In production: 14 tunnels watched, with 4 tunnel-down alerts raised and ticketed automatically.
CloudAutomate
The problem
Cloud servers sit outside the NOC’s view. A stopped server gets noticed by the customer, not by monitoring.
How it works
- Connects read-only with a least-privilege policy. Every region is scanned unless you specify otherwise.
- AWS EC2, RDS and WorkSpaces, Azure virtual machines (beta) and DigitalOcean droplets become monitored devices.
- Status every 60 seconds. Stopped or missing for two polls counts as down, with the same alert and ticket.
- Metrics every 5 minutes feed health thresholds, and spend and security findings refresh hourly.
In production: 196 cloud resources monitored as devices, out of 300 discovered.
EndpointAutomate
The problem
“The phones are down” starts an argument about whose problem it is, because handsets aren’t on the board.
How it works
- Connect Grandstream GDMS with an API client ID and secret. A built-in test confirms access and counts handsets.
- Polled every 60 seconds. Each online handset becomes a VoIP phone device at the right location.
- Down is confirmed over 3 polls and restored over 2, with 7-day uptime history per handset.
- Many handsets dropping together at one site is one site event, not dozens of alerts.
- Handsets can be rebooted from SmartTile, once a day at most and never during a call.
In production: 184 handsets monitored as devices, out of 326 tracked.
DeviceAutomate
The problem
Hand-built device lists are wrong within a month, and gear behind NAT can’t be pinged.
How it works
- One credential per vendor cloud or controller, and you choose what to import.
- Model, serial, firmware and MAC fill in automatically, without overwriting anything your team typed.
- Status comes from the vendor on every poll. Offline or missing counts as down.
- A confirmed outage alerts and opens a ticket, the same as a pinged device.
- If the vendor connection drops, devices turn grey (unknown), never a false green.
In production: 8 vendor clouds and controllers supported out of the box.
ServiceAutomate
The problem
Alerts in one inbox and tickets in another, and the second inbox is the one nobody watches.
How it works
- A device down past your “open a ticket after” window creates a ticket in your ITSM system.
- One outage, one ticket per location. Additional down devices become notes, not duplicate tickets.
- Notes sync both ways every 5 minutes between your ITSM system and the SmartChoice NOC.
- Recovery adds a note, and the ticket closes per your Ticket Policy.
- Every ticket and note is logged in the Automation Audit Ledger.
In production: 953 device outage tickets opened and tracked automatically.
CarrierAutomate
The problem
A circuit drops at 2 a.m. Someone has to find the account, call the carrier, sit in the phone tree and write down the ticket number.
How it works
- Confirms the outage first, then checks for the circuit ID, any open carrier ticket and a genuine site contact.
- Uses the carrier’s API where available. Otherwise Joey, our AI voice agent, calls the carrier.
- Joey works the phone tree, reads out the circuit ID, holds up to 45 minutes and returns the ticket number.
- Status calls follow a cadence (15 minutes, 1 hour, 4 hours, up to 3 days), each summarized in the ticket.
- After ten attempts without a result, a live SmartChoice engineer takes over.
In production: 1,179 carrier calls placed by Joey across 40 carriers: 88 new tickets opened and 984 existing tickets updated.
Production figures measured on SmartTile’s main server. Point-in-time measurements, not a service-level commitment.
Don’t see your platform?
Let us know and we’ll build it for you.
Network operations automation FAQ
Network operations automation uses software to handle the repetitive work that follows a network event: opening and enriching tickets, contacting carriers, tracking repairs, updating firmware and keeping documentation current. Instead of an engineer manually working each alert, the platform carries the issue from detection through resolution and keeps your team informed along the way.
Most monitoring tools stop at the alert. SmartTile handles what comes next. It opens a ticket in your ITSM platform with site, circuit, device and contact details already attached, opens and chases the carrier repair ticket, and tracks the issue to restoration. Your team gets a resolved incident instead of another alert to work.
When a circuit goes down, CarrierAutomate opens a repair ticket with the carrier through API or an AI voice agent, then tracks every update until service is restored. It works with AT&T, Verizon, Lumen, Spectrum, Comcast, Zayo, Granite and 60+ other carriers. If a ticket can’t be established, SmartChoice’s 24/7/365 U.S.-based NOC takes over.
SmartTile waits for a sustained 15-minute outage before opening a ticket. That window filters out brief blips and false alerts so carriers and your engineers only work real incidents. Site contacts are notified once the outage is confirmed.
Yes. FirmwareAutomate checks every device against the vendor’s latest release every 10 minutes. When a newer build is available, it raises an advisory with a 14-day SLA, opens a ticket and emails site contacts. Your team picks the maintenance window, and upgrades are only pushed when you switch that on. SmartTile then verifies the running version and closes the ticket.