FSENWe close the gap your answering machine can't
Never miss a service call again.
Your answering machine catches the call. That's where it stops. FSEN picks up where it leaves off — pages your crew, lets the first one to reply YES claim the job, and texts your customer back with a name in minutes. Automatic dispatch between the caller hanging up and a tech on the way. Set up in 10 minutes.
Every missed call is a job that went to a competitor
After-hours, every alternative ends the same way: a message you read later, not a tech on site. None of them route by trade, schedule, account SLA, or property context. They capture the call. They don't close it.
Staffed dispatchers
Expensive in-house team. Coverage gaps unless you staff 24/7. One person out and the pipeline stalls.
3rd party call centers
Premium per-minute rates, generic scripts, no trade or property context. Customers put on hold by strangers to your business.
AI receptionists
Pleasant voice, fluent conversation — but the endpoint is still a message in your inbox. No tech paged, no claim, no callback. Just a transcript.
Direct wakeup calls
One tech, no backup. If they don't answer, the call dies. No escalation, no logging, no accountability.
Capturing the call is the easy part.
An answering machine catches the call. An AI receptionist holds a nice conversation. Neither one sends a tech. FSEN closes the gap automatically — everything that has to happen between the caller hanging up and your crew showing up.
| After the caller hangs up… | Answering machine | AI receptionist | FSEN |
|---|---|---|---|
| Captures the call into a record | ◐ | ✓ | ✓ |
| Pages every on-shift tech for that trade — at once | ✕ | ✕ | ✓ |
| First tech to reply YES claims the job | ✕ | ✕ | ✓ |
| Texts the customer back with a name in minutes | ✕ | ✕ | ✓ |
| Stands the losing techs down so nobody double-shows | ✕ | ✕ | ✓ |
| Escalates to a backup contact if no one claims | ✕ | ◐ | ✓ |
| Tracks ARRIVED + DONE through to job completion | ✕ | ✕ | ✓ |
| Writes the resolution back to Jobber / ServiceTitan / Housecall | ✕ | ✕ | ✓ |
An answering machine's job ends at the beep. FSEN's job starts at the beep — which is why a missed call ends as a claimed incident instead of a voicemail you read tomorrow.
Built for trade shops with a real on-call rotation.
HVAC, plumbing, electrical, restoration. Anyone whose phone rings at 2 AM and needs a tech on site, fast.
Add your techs, set the schedule, pick the trade categories each one handles. FSEN cascades through the right people in priority order, falls back to your category manager when nobody answers, and writes every call to an audit log so your shop has a record instead of "I think Mike took it last Tuesday."
How the routing layer actually picks
Six rules run before the cascade rings anyone. Each rule trims the pool to the people who should actually take this call right now.
Trade and category match
Every worker carries the categories they actually handle. HVAC calls only ring HVAC people. Water leaks only ring plumbing. The cascade is built off the incident type, not a generic blast.
Priority cascade with timeouts
Tier 1 rings first. If no YES inside the response window, the next tier fires. Workers reply YES on SMS or press 1 on voice. Landline dispatch desks supported, no SMS required.
SLA tiers per account
Gold accounts get a tight response window with their own pool. Silver and Bronze get broader pools and longer windows. SLA scoping runs before the cascade picks anyone.
Per-category escalation
Cascade exhausts the list. HVAC bounces to your HVAC manager. Plumbing bounces to your plumbing manager. Each trade has its own fallback instead of one shared master phone.
From a missed call to a job your crew accepted
Five steps. No dispatcher in the middle. Your crew earns the job.
Call hits your line
A customer dials your FSEN number. The IVR picks up, identifies the caller against your account list, and pulls account and SLA context if there is a match.
Incident is logged
Address, trade, and description go into a new incident. The SLA timer starts. Every action from this point lands on the record with a timestamp.
Routing layer matches
FSEN filters your roster by trade, schedule, and account SLA. The cascade list is built before anyone gets rung.
Crew gets paged at once
Every tech tagged for that trade gets an SMS and a voice ring at the same time. First to reply YES claims the job — the rest get a "claimed by Mike" stand-down so nobody shows up twice. Want a strict tier order instead? Flip any priority list into ordered mode from the Schedule tab.
Fallback and writeback
No one claims it? The call rolls up to the owner phone — accept it yourself, or text ASSIGN MIKE to hand it off to a specific tech. Throughout the flow, lifecycle events fire to your FSM or webhook endpoint. Per-trade escalation routes are available in Settings when you want them.
From a missed call to a job your crew accepted
Five steps. No dispatcher in the middle. Your crew earns the job. Scroll to follow the call.
Call hits your line
A customer dials your FSEN number. The IVR picks up, identifies the caller against your account list, and pulls account and SLA context if there is a match.
Incident is logged
Address, trade, and description go into a new incident. The SLA timer starts. Every action from this point lands on the record with a timestamp.
Routing layer matches
FSEN filters your roster by trade, schedule, and account SLA. The cascade list is built before anyone gets rung.
Crew gets paged at once
Every tech tagged for that trade gets an SMS and a voice ring at the same time. First to reply YES claims the job — the rest get a "claimed by Mike" stand-down so nobody shows up twice. Want a strict tier order instead? Flip any priority list into ordered mode from the Schedule tab.
Fallback and writeback
No one claims it? The call rolls up to the owner phone — accept it yourself, or text ASSIGN MIKE to hand it off to a specific tech. Throughout the flow, lifecycle events fire to your FSM or webhook endpoint. Per-trade escalation routes are available in Settings when you want them.
Integration layer
Use it standalone. Or run it behind your existing stack.
The dispatch UI works on its own. The integration surface lets you wire FSEN into the FSM or workflow tools you already operate. You pick.
Two-way FSM sync
Incident lifecycle writes back to your field-service system as work orders, jobs, and visits. Acceptance, arrival, and completion all update on the customer record. No duplicate data entry, no manual handoff.
Outbound webhooks
Every incident lifecycle event POSTs to your endpoint with HMAC-SHA256 signing. created, dispatched, accepted, escalated, completed. Plug into Zapier, n8n, or your own service.
API keys for read/write
Bearer tokens for your existing systems to push incidents in or pull state out. Scoped to your company, revocable on the spot, no OAuth dance to integrate.
Standalone or wired in
Run FSEN on its own through the dispatch UI, or use it as the routing layer behind ServiceTitan, Housecall Pro, Jobber, ServiceChannel, or whatever stack you already operate.
Forward or fresh
Forward your existing main line, or publish a dedicated FSEN number.
Audit-grade timeline
Every call, SMS, accept, and decline timestamped on the incident.
Voice or SMS accept
Mobile workers reply YES on SMS. Landline dispatch desks press 1 on voice.
Now available · Trade shops
Get FSEN on your emergency line
FSEN replaces the 2 AM answering service with a routing layer that knows your trades, your techs, and your SLAs. Plans start at $99/mo. Forward your existing emergency line or publish a dedicated FSEN number. Book a 20-minute walk-through and we will have you taking calls the same week.
What you get
Full routing layer from day one
Trade match, SLA tiers, priority cascade, voice and SMS accept, category fallback. The complete dispatch stack, not a beta.
Runs alongside your current setup
Keep your existing answering service or dispatcher in parallel until you trust FSEN on real calls. No cold switch.
Two-way FSM integration
ServiceTitan, Housecall Pro, Jobber, ServiceChannel, Corrigo. Acceptance, arrival, and completion write back to the customer record automatically.
Audit-grade timeline on every call
Every accept, decline, escalation, and SMS timestamped on the incident. A real record instead of a garbled 7 AM email summary.
Founders on the phone
Direct line for setup, tuning, and the occasional 2 AM question. No support tickets, no hold music.
What we ask
A real on-call rotation
HVAC, plumbing, electrical, or restoration shop with 24/7 emergency coverage. Real calls, not test traffic.
Your trades and SLA logic
The rules your dispatcher already runs in their head. We encode them into the routing layer.
An emergency line to forward
Forward your existing main number, or publish a dedicated FSEN number on day one.
Tech roster and schedules
Who handles what, who is on call when, who escalates to whom. Loaded on the first call.
A plan that fits today
Starter at $99/mo for solo and small shops. Growth at $199/mo with Jobber. Operator at $399/mo for multi-trade volume.
Tell us about your operation. We reply within a day.