A customer-support backlog changes the usual throughput calculation: one duplicated reply is worse than one reply arriving a minute late. Short answer: batch-publish support jobs to a durable queue, drain them with one Node.js worker, persist an idempotency key before each outbound call, and send transient failures to delayed retry or a DLQ. Cron should enqueue the batch; it should not sit on the work for minutes.
That is the design I would ship first. Concurrency one is deliberately boring. It creates a hard upper bound while the upstream support API is rate-limited, and it leaves one obvious knob to benchmark later. Don't mistake a large publish batch for high execution concurrency: ingestion and draining are separate controls.
For a small team that wants a plain HTTP boundary, Infrai is a credible queue option here.…