Below is a high-level architecture

[alexalamin]

For example, the incoming call can get an automatic response or could be redirected to another number. Using these building blocks, setting up a phone number masking application is straightforward. Two parties can have a phone call or engage in an SMS conversation through a proxy number without revealing their real numbers. We can simply forward the messages from one number to the other when receiving a webhook. And it all works seamlessly as if you’re communicating directly with the other person.

Below is a high-level architecture of how Yelp integrated with a lebanon mobile phone numbers database telephony API provider to offer the utility of phone masking, while keeping all phone events in sync with the Yelp conversation. For calls, we proxy the call immediately to the second number and reflect the call on the user’s inbox. For SMS, the flow looks very similar, except instead of a call we persist and forward a text message. Masking Session Data Model The only thing left is an appropriate data model to integrate phone masking with the Yelp conversation.



Our key requirement is that only the Yelp business can call the proxy number to reach the customer, and vice versa. Therefore, we need a data model which encapsulates the customer and business numbers and links them via a proxy number, so that we can route messages and calls to the proxy number to the intended recipient. We call this model a “masking session” because it provides a temporary connection between the two real numbers while not exposing them directly to each other.