Custom Channel: to integrate your own channel
complete
I
Iaroslav Kudritskiy
This would allow connecting your own chat applications as a channel to Rocketbots.
Examples of custom channels are SMS providers or in-app chats.
NOTE: due to the complexity and cost of this feature, it will only be available to our Enterprise, Reseller and CUSTOM customers.
Jerry (CEO)
⚠️ We are looking for customers who would like to gain early access to this feature and participate in its development.
Please me know if you are interested!
Z
Zy
complete
Integration with any — yes, any — third-party messaging channel is now possible 🎉 Our brand-new Custom Channel feature allows you to integrate any messaging channel with respond.io, so you truly can handle all conversations on a single platform.
Learn more about Custom Channel here: https://docs.respond.io/messaging-channels/custom-channel
Hasan Basri
Hello Jerry (CEO) ! We are interested, we would like to integrate with custom whatsapp api
Jerry (CEO)
Hey Hasan Basri: what WhatsApp BSP are you looking to integrate to?
In theory Custom Channel will allow you to integrate to any channel (including custom WhatsApp implementations), but do note that WhatsApp is a rather complex channel that requires keeping track of the approved Template Messages, the 24 session, etc.
So even though it possible to integrate to a custom WhatsApp using the Custom Channel feature, you might end up losing some of the WhatsApp features.
Hasan Basri
Jerry (CEO): i made api service from lib https://github.com/adiwajshing/Baileys
Not official api whatsapp
Jerry (CEO)
Hasan Basri: haha then that shouldn't be any problem, however you will need to build a layer in between our Custom Channel and the WhatsApp service to modify the structure of the body.
Would you be interested to upgrade to an Enterprise plan to gain access to this feature?
Hasan Basri
Jerry (CEO): I think it is available in free hheh
Jerry (CEO)
Hasan Basri: haha sorry mate, I am afraid it's a very costly feature to maintain for us :(
Maybe in the future!
A
Alberto Ruiz
Hello Jerry (CEO) ! We are interested, we would like to integrate with local TELCO for SMS
Jerry (CEO)
Alberto Ruiz: that's great, integrating to local SMS providers is one of the main use-case for this feature. Tell me, do you have developers on your team?
A
Alberto Ruiz
Jerry (CEO): Yes
Jerry (CEO)
Alberto Ruiz: excellent, we will get back to you in the coming days via a private message.
A
Alberto Ruiz
Jerry (CEO): great Gerardo, looking forward
Masum .S
we are interested in-app chats chat features which we would like to integrate with our UC mobile and desktop app for cloud base UCaaS solution
Jerry (CEO)
Masum .S: are you looking to build these integrations via webhooks or via SDK?
The custom channel will be Webhook (http post) based. Let me know if that is what you are looking for!
Jerry (CEO)
⚠️ We are looking for customers who would like to gain early access to this feature and participate in its development.
Please me know if you are interested!
J
JABER BEVATEL
Jerry (CEO): we interest on that customization on channels
Jerry (CEO)
JABER BEVATEL: excellent, we will get back to you in the coming days via a private message.
A
Anthony Ho
Jerry (CEO): we are interested as well. Please contact us. ;D
H
Hasan Niyaz
Jerry (CEO): Would like to add our local SMS provider. This will reduce SMS costs to a quarter of what Twilio charges now.
Jerry (CEO)
in progress
Jerry (CEO)
under review
Jerry (CEO)
Store IVR thanks for your feedback, your request if part of our "Custom Channel" project which we will be implementing in Q4 this year. Curious, would you be interested in participating in our alpha program when we kick start? Looking forward to hearing from you soon!
S
Store IVR
Jerry (CEO): Definitely would love to be a part!
Jerry (CEO)
Store IVR: glad to hear that 🎉
Someone from our product team will reach out to you when we get started :)
Jerry (CEO)
Merged in a post:
Open Channel (Webhook) API
S
Store IVR
You can create an API endpoint for respond.io itself, where it allows open communication.
---
Example:
Create an Open Channel/ Client. Which allows us to send and receive basic things like:
(a) Body.
(b) unique conversation id (either respond.io generated or pass as payload).
(c) status (sent, delivered, read).
Next version could also have maybe Header, Footer, Quick Reply, etc.
===
Use case:
1) The number of service are then not limited.
In India sending SMS is tedious, but if sending via directly through Telecom Operator, we can make use of APIs even for services other than Twilio, Vonage, MessageBird and more.
2) There are more than the listed WABA (WhatsApp Business API) BSP (Business Service Providers), it will help integrate any and all of them, atleast to achieve basic conversations.
3) As respond.io becomes a great Omni Channel communication tool, we could also use this API to log Voice Call details, even for services other than Twilio, Vonage, MessageBird and more.
4) Add any other CRM chat.
- regards
Vachan (KDC)
Michael Stiller
A very important feature!
Load More
→