Dear all   A prospecitve customer (group company) is facing (conservatively guesstimated) 10-20 sms authenticated guests across 100 sites (sub-companies) per day, all year round. With european sms prices (Twilio calls a list price of USD 0.07 per msg), that will sum up to quite the amount of money per year for the parent/group company.  They're looking for a means to split/forward that bill "downstream" to the individual site or regional directors.  We (the MSP) absolutely want to avoid setting up 100 networks for 100 sites within that organization, and no one is looking forward to maintaining 100 Twilio sub-accounts with each their Account SIDs and Auth Tokens  Question: Can (selectable) meta information be passed along the with the API request to Twilio? For example, the AP's system name would nicely identify the site. But I'm also thinking of tags we could set per site or billing region for the AP. Once the information is with Twilio, the customer could sort out their split billing with Twilio directly.  The answers I got from Twilio's AI chatbot seem to suggest that their API might be able to ingest such information. Or: Do such things this happen already, and some AP related or other meta information is already going to Twilio by  default? Thanks for your thoughts and pointers. ... View more