Everything worth knowing, nothing that isn't.
What 'sustained' means
Most aggregators publish a default per-bind TPS; BroadNet sets no fixed per-account limit and agrees capacity per bind with each account, up to 30,000 SMS/s per node. The SLA promise: that rate is sustainable indefinitely, not just for a 10-second burst. Sustained throughput depends on the aggregator's downstream operator routes and any rate-limits the operator imposes. A 1,000 TPS aggregator-side bind throttled by a 200 TPS operator route gives you 200 TPS effective for that destination.
Burst vs sustained
Burst TPS is what you can submit for short windows before queues back up. Sustained is what you get for the long run. Most production integrations care about sustained; OTP services care about burst (a marketing-trigger event can produce a 10x OTP-request spike for 30 seconds). BroadNet sets no fixed per-account limit: quote your peak-to-mean ratio when you size, and capacity per bind is agreed with your account team, up to 30,000 SMS/s per node.
How to raise it
Higher TPS is provisioned per bind, per destination. The constraints: operator-side route capacity (some operators cap inbound A2P trunk capacity), your aggregator's connection pool to that operator, and your own infrastructure's ability to produce submissions at that rate. BroadNet provisions higher TPS through a sales conversation; lead time depends on route headroom and on whether additional operator agreements are needed.
What the SLA should specify
Five things. Sustained TPS per bind. Burst TPS and burst duration. Latency p95 and p99 at the SLA throughput. DLR delivery latency. Credit/penalty structure if the SLA is missed. Without all five the SLA is a marketing claim, not a contract.