Telecommunications tenders, on-call and SLAs
iERP for telecommunications brings together the three fronts of an operator or installer: the connectivity tenders that fit your company, on-call technicians with their shifts and clock-ins, and client incidents with their SLA. You run it from your Claude or ChatGPT, without jumping from one tool to another.
-
01 · Public sector
Tender spotted
InConnectivity tender
OutDocuments read, fit checked
-
02 · Public sector
Requirements reviewed
InDocuments read, fit checked
OutCredentials and technical means
-
03 · Public sector
Awarded
InCredentials and technical means
OutContract with a 4 h SLA
-
04 · People
On-call technicians
InContract with a 4 h SLA
OutOn-call calendar
-
05 · People
Shifts published
InOn-call calendar
OutTeam with shifts and alerts
-
06 · Support
Incident opened
InTeam with shifts and alerts
OutTicket with priority and SLA
-
07 · Support
Technician assigned
InTicket with priority and SLA
OutWhoever is on call in that area
-
08 · Support
Solved within SLA
InWhoever is on call in that area
OutClient told it's closed
-
09 · People
Hours clocked
InClient told it's closed
OutOn-call time in the time records
One record from start to finish: nothing is typed twice · Sample data
On call, in one conversation
The operations manager asks and the assistant crosses shifts, clock-ins and incidents: who is on call, which SLA is at risk and which new tenders fit your network.
Your assistant · connected to iERP
Who is on call tonight in the north area, and is any incident's SLA at risk?
- → people · shifts and on-call
- → support · open incidents
- → support · assignment
Pol Ferrer is on call. There is a fibre incident in Getafe with 1 h 20 min of SLA left. Shall I assign it and let him know?
Yes, go ahead Review
Assigned to Pol · alert sent
Sample data
3 modules. Why each one.
The awarded contract sets the SLA, the shifts cover it and every incident is measured against it: one record.
-
Connectivity and roll-out tenders that fit your company. Radar · tender documents · applications
Public sector
-
Incidents with priority and SLA, in the client's language. Tickets · deadlines · languages
Support
-
Technicians' shifts and on-call, with clock-ins and time records. Shifts · clock-ins · holidays
People
Sample data
On-call, covered
The shift generator spreads the month's on-call slots respecting rest periods and holidays; you compare it with other options and publish it. Every on-call hour is clocked.
Bid, cover and resolve. One price.
- Public sector €59 / month
- CRM Required by Support €15 / month
- People €15 / month
- Support €15 / month
- Volume discount · −10% −€10
- Users · 10 €50 / month
- Connector to your AI (MCP) Included
This industry's modules, 10 users and the connector to your AI, per month.
€144/ month
Paying annually: €117 per month.
Every user costs the same, whatever they use. Prices exclude VAT.
Frequently asked
Do I have to subscribe to all three modules?
No. You can start with People for on-call or with Public sector for tenders. Support relies on CRM, which sign-up adds automatically.
Does the shift generator take rest periods into account?
Yes. It proposes scenarios that respect rest periods, holidays and absences; you pick the one that best covers on-call and publish it.
Can I measure each incident against the contract SLA?
Yes. Each client has its SLA and each ticket shows the time left, so you know which incidents are at risk before they breach.
Can technicians clock in and check their shift from their phone?
Yes. They clock in from their phone and, if they connect their Claude or ChatGPT, they can ask for their next shift or request a swap without opening any screen.