To associate a number (or push registration) with a user you create a "binding"
More info here: https://www.twilio.com/notify/api
With new offerings like Copilot and presumably this, they get a chance at a fresher start BUT unless you want to handle interacting with Twilio's endpoints directly you're going to have to wait for your client libraries to catch up, which might not be a problem with NodeJS, but for instance my company uses a third-party Golang library that's two years old and has only received minor tweaks in the past 6 months. It will probably not be updated with new features soon or ever, and should I want to utilize these new features I would have to extend or re-write the library myself.
Finally Twilio provides no ways of including metadata in an SMS submission (which is a huge freaking oversight) and makes it very difficult to associate a number with an account. The most accepted answer for that problem currently is to use the Twilio number as a foreign key for an account, which a) does not work with Copilot as you have no control over which number will send the message and b) requires each account to have its own ($1) number, which does not scale.
Do developers integrate Twilio SDK into their apps (similar to Fabric, etc.)? If so, sounds like a way different model than what they used to do (Basically you could integrate just by calling their REST endpoint since it was SMS based and required no installation of any app, but with APNS the only way I can see this work is if you tightly integrate with Twilio API by using their SDK)
How do they figure out a number is associated with an account? Does this assume that users will enter their phone numbers when signing up to a service?