Number Pooling & Concurrency

Number masking does not need one virtual number per relationship. The platform allocates from a pool of numbers you have enrolled and safely reuses a single number across many active sessions at the same time — as long as no party is already live on that number. When you create a session, an available number is picked automatically; when the session ends or expires, the number is returned to the pool for the next one. This collision-safe reuse keeps your number costs low: you only enroll more numbers when genuine concurrency demands it, and the API tells you clearly when it is time to add capacity.