This endpoint or api is responsible for seeding the client to a particular personnel within sub_dealer. In the same call message could be sent to the client spoofing the dealer
There is an option to use sub_dealer’s braango_number or use partner_dealer’s generic blast nunber. Please work with ‘support@braango.com’ to establish generic blast number for your account. If no braango_number is specified, partner’s blast number is used. As a fallback, braango_system has generic numbers to that can be used.
At moment for every partner dealer, blast number is seeded by support team, in V2.1 there will be API support or it will be hidden process
By default, the connection to the personnel is not enabled and it is expected that partner will parse the response to leading question is sent to client and based on that decide to enable or disable the bridge
*(Note personnel and sub_dealer_master account both need to be enabled and active)
The same API can be used to send onlt messge to the seeded client, there is no need for seperate API. This use case would be for any changes detected in partner system that needs to be sent to client, such as offers, or personnel entering message in UI
This API along with Dealer Connect(S) api forms a powerful solution for early binding. Lead Generators and Portals will find this flow most interesting
This endpoint or api is responsible for seeding the client to a particular personnel within sub_dealer. In the same call message could be sent to the client spoofing the dealer
There is an option to use sub_dealer’s braango_number or use partner_dealer’s generic blast nunber. Please work with ‘support@braango.com’ to establish generic blast number for your account. If no braango_number is specified, partner’s blast number is used. As a fallback, braango_system has generic numbers to that can be used.
At moment for every partner dealer, blast number is seeded by support team, in V2.1 there will be API support or it will be hidden process
By default, the connection to the personnel is not enabled and it is expected that partner will parse the response to leading question is sent to client and based on that decide to enable or disable the bridge
*(Note personnel and sub_dealer_master account both need to be enabled and active)
The same API can be used to send onlt messge to the seeded client, there is no need for seperate API. This use case would be for any changes detected in partner system that needs to be sent to client, such as offers, or personnel entering message in UI
This API along with Dealer Connect(S) api forms a powerful solution for early binding. Lead Generators and Portals will find this flow most interesting
This API enables connecting un-seeded client to the particular personnel within sub_dealer Calling this API seeds the client to particular personnel within the sub_dealer. In case if you want to see all personnel within sub_dealer using the more generic version of the API please refer here
The API spoofs the client and sends message to the dealer. Partner or master account is expected to notify the dealer that client in question is seeded and is ready to communicate
API is poweful to use sub_dealer’s braango number to connect client with dealer. This would result in engagement between client and dealer using dealer’s braango number. It would be avisable to notify client in that case of change of ownership either using add_client api call prior to maing this call (add_client allows to spoof dealer to client) or using message_blast api and notifying change of ownership in the message. This would engagement experience more smoother. By default client is still engaged with blast number that was used in original message_blast api call
In case if sub_dealer’s braango number is not used to connect client with dealer, client will be able to communicate using the blast number on which it first received the message. The blast number then acts as bridge between the client and the dealer
It should be noted that , client can be connected to multiple sub_dealers by calling this API call repeatedly with diffent sub_dealers . In case connection has to be made to all the personnel within the sub_dealer, then there is variant of this API described below that can be used.
(Note for connecting clients to dealer with blast number, we allow only 3 connections. In case client needs to be connected to more than 3, we suggest to use sub_dealer’s braango_number instead)
Combination of message_blast and this API is very powerful for lead_reselling , lead_harvesting business model. Lead providers typically use this model in say “Buy Here Pay Here BHPH” or other scenarios where they have quality harvested
This API enables connecting un-seeded client to the particular all personnel within sub_dealer Calling this API seeds the client to all personnel within the sub_dealer. In case if you want to see one personnel within sub_dealer using the more specialized version of the API describe please refer
The API spoofs the client and sends message to the dealer. Partner or master account is expected to notify the dealer that client in question is seeded and is ready to communicate
API is poweful to use sub_dealer’s braango number to connect client with dealer. This would result in engagement between client and dealer using dealer’s braango number. It would be avisable to notify client in that case of change of ownership either using add_client api call prior to maing this call (add_client allows to spoof dealer to client) or using message_blast api and notifying change of ownership in the message. This would engagement experience more smoother. By default client is still engaged with blast number that was used in original message_blast api call
In case if sub_dealer’s braango number is not used to connect client with dealer, client will be able to communicate using the blast number on which it first received the message. The blast number then acts as bridge between the client and the dealer
It should be noted that , client can be connected to multiple sub_dealers by calling this API call repeatedly with diffent sub_dealers . In case connection has to be made to all the personnel within the sub_dealer, then there is variant of this API described below that can be used.
(Note for connecting clients to dealer with blast number, we allow only 3 connections. In case client needs to be connected to more than 3, we suggest to use sub_dealer’s braango_number instead)
Combination of message_blast and this API is very powerful for lead_reselling , lead_harvesting business model. Lead providers typically use this model in say “Buy Here Pay Here BHPH” or other scenarios where they have quality harvested leads
This endpoint or api is responsible for seeding the client to a particular personnel within sub_dealer. In the same call message could be sent to the client spoofing the dealer
There is an option to use sub_dealer’s braango_number or use partner_dealer’s generic blast nunber. Please work with ‘support@braango.com’ to establish generic blast number for your account. If no braango_number is specified, partner’s blast number is used. As a fallback, braango_system has generic numbers to that can be used.
At moment for every partner dealer, blast number is seeded by support team, in V2.1 there will be API support or it will be hidden process
By default, the connection to the personnel is not enabled and it is expected that partner will parse the response to leading question is sent to client and based on that decide to enable or disable the bridge
*(Note personnel and sub_dealer_master account both need to be enabled and active)
The same API can be used to send onlt messge to the seeded client, there is no need for seperate API. This use case would be for any changes detected in partner system that needs to be sent to client, such as offers, or personnel entering message in UI
This API along with Dealer Connect(S) api forms a powerful solution for early binding. Lead Generators and Portals will find this flow most interesting
This endpoint or api is responsible for seeding the client to a particular personnel within sub_dealer. In the same call message could be sent to the client spoofing the dealer
There is an option to use sub_dealer’s braango_number or use partner_dealer’s generic blast nunber. Please work with ‘support@braango.com’ to establish generic blast number for your account. If no braango_number is specified, partner’s blast number is used. As a fallback, braango_system has generic numbers to that can be used.
At moment for every partner dealer, blast number is seeded by support team, in V2.1 there will be API support or it will be hidden process
By default, the connection to the personnel is not enabled and it is expected that partner will parse the response to leading question is sent to client and based on that decide to enable or disable the bridge
*(Note personnel and sub_dealer_master account both need to be enabled and active)
The same API can be used to send onlt messge to the seeded client, there is no need for seperate API. This use case would be for any changes detected in partner system that needs to be sent to client, such as offers, or personnel entering message in UI
This API along with Dealer Connect(S) api forms a powerful solution for early binding. Lead Generators and Portals will find this flow most interesting
This API enables connecting un-seeded client to the particular personnel within sub_dealer Calling this API seeds the client to particular personnel within the sub_dealer. In case if you want to see all personnel within sub_dealer using the more generic version of the API please refer here
The API spoofs the client and sends message to the dealer. Partner or master account is expected to notify the dealer that client in question is seeded and is ready to communicate
API is poweful to use sub_dealer’s braango number to connect client with dealer. This would result in engagement between client and dealer using dealer’s braango number. It would be avisable to notify client in that case of change of ownership either using add_client api call prior to maing this call (add_client allows to spoof dealer to client) or using message_blast api and notifying change of ownership in the message. This would engagement experience more smoother. By default client is still engaged with blast number that was used in original message_blast api call
In case if sub_dealer’s braango number is not used to connect client with dealer, client will be able to communicate using the blast number on which it first received the message. The blast number then acts as bridge between the client and the dealer
It should be noted that , client can be connected to multiple sub_dealers by calling this API call repeatedly with diffent sub_dealers . In case connection has to be made to all the personnel within the sub_dealer, then there is variant of this API described below that can be used.
(Note for connecting clients to dealer with blast number, we allow only 3 connections. In case client needs to be connected to more than 3, we suggest to use sub_dealer’s braango_number instead)
Combination of message_blast and this API is very powerful for lead_reselling , lead_harvesting business model. Lead providers typically use this model in say “Buy Here Pay Here BHPH” or other scenarios where they have quality harvested
This API enables connecting un-seeded client to the particular all personnel within sub_dealer Calling this API seeds the client to all personnel within the sub_dealer. In case if you want to see one personnel within sub_dealer using the more specialized version of the API describe please refer
The API spoofs the client and sends message to the dealer. Partner or master account is expected to notify the dealer that client in question is seeded and is ready to communicate
API is poweful to use sub_dealer’s braango number to connect client with dealer. This would result in engagement between client and dealer using dealer’s braango number. It would be avisable to notify client in that case of change of ownership either using add_client api call prior to maing this call (add_client allows to spoof dealer to client) or using message_blast api and notifying change of ownership in the message. This would engagement experience more smoother. By default client is still engaged with blast number that was used in original message_blast api call
In case if sub_dealer’s braango number is not used to connect client with dealer, client will be able to communicate using the blast number on which it first received the message. The blast number then acts as bridge between the client and the dealer
It should be noted that , client can be connected to multiple sub_dealers by calling this API call repeatedly with diffent sub_dealers . In case connection has to be made to all the personnel within the sub_dealer, then there is variant of this API described below that can be used.
(Note for connecting clients to dealer with blast number, we allow only 3 connections. In case client needs to be connected to more than 3, we suggest to use sub_dealer’s braango_number instead)
Combination of message_blast and this API is very powerful for lead_reselling , lead_harvesting business model. Lead providers typically use this model in say “Buy Here Pay Here BHPH” or other scenarios where they have quality harvested leads