Always Connect SolutionsTelecom workflow automation
Turn thousands of individual changes into one manageable job.
For Always Connect Solutions, LONGWApps built a bulk update workflow around an individual SIM update endpoint. The project design handles 10,000+ SIM updates per run through persisted jobs, controlled parallel dispatch, asynchronous status processing and live browser updates.
- SIM updates per run in the project design
- 10,000+
- Pending SIM updates selected per dispatch batch
- 100
- Progress returned through WebSockets
- Live status
Project details and figures come from LONGWApps’ architecture records and describe this engagement.
THE BUSINESS CHALLENGE
Make the operation easier to run.
The project architecture records that a bulk API was unavailable at the time, while the provider offered an individual SIM update endpoint. Sending a large list was therefore only part of the problem: the team also needed to see which updates were pending, in progress, completed or failed as asynchronous responses arrived.
WHAT LONGWAPPS BUILT
A connected path through the work.
We built a bulk job API that saves each job and its SIM records. A scheduler runs every minute, selecting 100 pending updates and sending the individual requests in parallel with cURL. An AWS Lambda webhook receives carrier callbacks, SQS holds the work, and a status processor updates the database and notifies the Node WebSocket service.
- Create a job
Upload or paste the SIM list and save the records as pending.
- Dispatch a batch
Select 100 records and send parallel individual API calls.
- Process callbacks
Receive asynchronous results through Lambda and SQS.
- Show progress
Update each SIM’s state and push changes to the browser.
ENGINEERING DECISIONS
Plan for the exceptions.
Persist the work before sending it
The bulk job API creates a job and inserts SIM records as Pending. The database provides the job record that the scheduler, callback processor and browser progress view can follow.
Use bounded batches around an individual API
Every minute, the scheduler selects 100 pending records, marks them In Progress and sends their individual updates in parallel with cURL. This batch size belongs to the ACS implementation and would be reviewed for another provider.
Separate acknowledgement from completion
The diagram shows an immediate 200 OK alongside asynchronous status callbacks. The workflow uses the returned status data to update SIM records rather than treating dispatch acknowledgement as completion.
Give failures and progress an operating path
The callback architecture includes a Lambda webhook, SQS, a status processing Lambda and a dead letter queue with up to three retries for failed messages. The Node WebSocket server sends the latest status changes to the browser.
VALUE FOR THE OPERATING TEAM
What changed for the team.
An operator uploads a CSV or pastes SIM numbers and follows each job through pending, in progress, completed and failed states. Carrier callbacks update the results as work finishes. Messages that cannot be processed after retries stay in a dead letter queue for investigation.
Explore the detailed system architecture

WHY THIS MATTERS FOR AGENTIC AI
Where AI could help next.
The same architecture gives an AI agent a clear way to request a job and check its progress. Permissions and execution rules remain in the application. This project delivered workflow automation. An operator assistant or AI interface would be a separate addition.
Possible next steps
- Help an operator prepare and validate a proposed bulk change before submission.
- Summarize the latest job progress and identify records needing attention.
- Explain failed updates from recorded responses while leaving retry authorization with the operating workflow.
Questions about this project.
How were bulk updates handled without a bulk endpoint?
The project architecture uses persisted jobs and a scheduler that selects 100 pending records each minute for parallel individual API requests. Carrier callbacks are processed separately through AWS Lambda and SQS, and the database records each SIM’s status.
How could operators see progress?
The browser displays Pending, In Progress, Completed and Failed states. A Node WebSocket server pushes status changes after callback processing updates the database.
Does 200 OK mean every SIM update is complete?
No. The diagram distinguishes the immediate acknowledgement from asynchronous status callbacks. The workflow updates SIM status from the callback response data.
