I'm trying to make sure a phone number attached to a Messaging Service auto create a conversation in a specific conversation service not the default one. From the Conversations > Default screen on the console I can read this:
What steps do I have to follow here to "specify another Messaging Service" in my request when the conversations are being auto created by twilio?
Requirements are:
I need a specific phone number creating a conversation in a specific Conversation Service as these are scoped to individual customers.
Twilio developer evangelist here.
Currently it is not possible to choose the conversation service for a messaging service to autocreate conversations in. The default conversation service is the only one that will be used to autocreate conversations.
An alternative approach here would be to create a new subaccount for each of your individual customers. You can then host your numbers, messaging service and conversation service for that customer within the subaccount and handle this use-case.
Related
I have bought two Twilio phone numbers which are validate and configured by Twilio and WhatsApp.
I created two Conversation Services ("Main Conversation Service" (SID:IS1234) and "Dev Conversation Service" (SID:IS4321)
Both are configured as "Engage in a discussion" Use case configuration.
Both are configured as "Autocreate a Conversation" in the Integration configuration.
Each service has a different phone number configured in the Sender Pool
Each WhatsApp Sender number Endpoint Configuration is configured a "Use Messaging Service (recomended)" with its respective Conversation Service
I have 2 Studio Flows ("WA_MAIN" and "WA_DEV"). In Flex > Manage > Messaging I have 2 WhatsApp addresses pointing each phone number to its respective Studio Flow.
This is the complete configuration, if something important is missing please ask me in the comments.
When I send a whatsapp message to each number the conversation is routed to the correct Studio Flow, but it is managed by the Main Conversation Service (IS1234), which is the older one. I have zero conversations in Dev Conversation Service (IS4321). All previous conversations with my phone number are in "closed" state.
Why is this happening? How can I build to independent environments to work with Conversations API without risking the SLA of Production environment?
This happens because of a Conversation Configuration where you configure the default messaging service that will handle the inbound conversations, you can see it on Conversations > Manager > Defaults.
The Twilio Team advises creating a new account to Homolog or Staging, so it's can be a solution to not affect your production environment.
I hope that it can help you.
We have 560 different Messaging Services for our customers in Twilio. We are trying to register one of these for an A2P 10DLC Campaign Use Case so that we can do some discovery and perhaps build a PoC.
We have:
Created our business profile in TrustHub
Registered our US A2P brand
Attempted to "Setup Messaging Service" by checking "Use an existing Messaging Service"
Only the first 20 Messaging Services are shown. There is no way to paginate, filter, or sort. I can't find anything about Campaigns in the API documentation or I would do this with the SDK or Postman.
I am still waiting on a response to my support ticket and emails to our account representative. Two million SMS messages a month seems like we would be eligible for a response in under a week, but we're currently blocked.
Is there anyone who has encountered this problem and can offer some suggestions while we wait to hear back? Thank you for any assistance.
Campaign Registration Console Screen
We have the need to open an SMS conversion between clients and service providers. The thought is to send an initial request to the provider with a message from the client and then have the provider reply (and converse) directly with the client.
I've looked in the quick starts and the API docs but I don't see any clear pathway.
Am I missing some thing?
You can use a product like Twilio Conversations for that purpose. You add both as participants into a conversation. They communicate to each other via their assigned Twilio Proxy numbers.
Introducing Twilio Conversations: Now, every message becomes an invitation for a conversation
Using Twilio Conversations (Using Conversation You Tube Video - Signal 2019)
Hi I have been working on one of my apps for integrating chat using Twilio SDK. I would want to know if it is possible to get the system message inside a channel for eg: 'Member A joined the channel', 'Member B left the channel', 'Member C accepted the invitation to join' and so on. It seems like Twilio SDK does not have API to get the system messages or to set them. How can we achieve this?
I also noticed that it can be achieved by setting the custom key-value pair in attributes inside the message and sending it to the channel. But for the newly invited members, they cannot send a message when they are declining the invitation request such as 'Member A declined the invitation to join channel', as they have not joined the channel yet.
Twilio developer evangelist here.
If you want to send persistent system level messages like this, you can do so with a combination of webhooks and the REST API.
The idea is that you can send messages to a channel using the REST API whenever you need one of these system messages. The default user for the REST API is the system and you can then treat messages from system as special for display in your UI.
I mention the webhooks because you can register to receive them for a number of useful events, like members joining and leaving channels. The webhooks may not cover all the things you want, like declining an invite, but for that I would just trigger my own HTTP request from the application to your server.
Let me know if that helps at all.
Can Twilio be hosted separately (specific to a customer) on the Twilio cloud?
This is for a customer requirement where they want their call details to be segregated and stored separately. Is this possible in Twilio?
Twilio developer evangelist here.
You won;t be able to host Twilio yourself as it's a cloud platform. What you can do however is have a subaccount for each one of your customers.
This way, their data will be segregated and not displayed with other accounts. This will also allow you or your customers to run reports that are only for that particular account.
All that data is stored in the cloud though, so technically they all live together in the same database.
You can read more about subaccounts here.