We are building a solution where we have to send orders to our clients whenever a customer places one on our site. To simplify the process we are looking at some kind of low cost order confirmation device where the order can be printed at the clients ends and the client sends a confirmation back.
I have searched for such kind of devices but i only get patent results for such devices.
Could your website be changed to email the client when a customer places an order?
Related
We're building a live chat-like software and we're trying to connect it through Twilio to send SMS messages to our clients' staff members. We've built a backend base in our control panel that would allow staff members to reply to the users through our system (it would send them an SMS back through Twilio).
Our system is built so that a user can send text messages based on a specific interest, which would create a new lead (for that interest type) entry in our system (as well as notify the staff with SMS). We'd like to be able to show a threaded SMS conversation back and forth between the users and the staff members for each of those separate leads/threads.
It's not a simple one-to-one conversation between the user and a staff member because the same user phone number can have multiple threads for each lead type. Is there a way to somehow tag messages so we can detect which thread they belong to?
Twilio developer evangelist here.
The limitation here is the SMS platform. You can see, if you open up your own phone's SMS application, that SMS messages are delivered in chronological order only. You can only reply to the last message sent, not a different message in the history. There is no message threading in SMS.
You have two options:
You insist that your users include a specific ID within messages in a thread so that you can parse the message and extract the ID to tie the threads together. Or, as Digant Shah suggested, use an ID and then assume every message is for that ID until a new ID is used.
You conduct separate conversations between the same users using different Twilio numbers. This way you can tie the thread together using the number that was used.
I've had this conversation in this question before, and the follow up might help too.
Let me know if that helps at all.
With Rocket.chat and Twilio - the incoming chat 'user' is just a mobile number. This is not very user friendly if multiple conversations are ongoing. Responding to and tracking conversations by name and not phone number is much better if possible.
I have a database that could be used to match the incoming SMS phone numbers to a human name for most of my expected incoming SMS IM's. Trying to figure out the best way to do a lookup and add that to the Twilio # identity so that the 'chat' makes more sense to the in-house user who would be using it.
Appreciate any ideas anyone might have that would save me from re-inventing the wheel w/ Twilio and Rocket.Chat.
Related to RocketChat: How to send SMS Messages to Livechat channel from mobile
Twilio developer evangelist here.
I have not used RocketChat for this before, I just took a look through the code to see what I could find.
Turns out, RocketChat has a field for phone number on the user model and when an incoming message is received it looks up a user from their phone number. If the user is found, the message is sent from the user, otherwise a new user is created.
So, what you need to do is merge your database of usernames and phone numbers with the RocketChat User model.
Hope that helps!
I am currently using Twilio to send balance notifications for customers who have opted into SMS notifications, but have run into an issue in positively identifying accounts in the message logs. A number of customers have multiple accounts due to the nature of my industry, but naturally use the same phone number across all accounts. Is there any way to pass a parameter containing their internal account ID in the HTTP POST request without including it in the message body? I've searched extensively through Twilio's API docs and cannot find this addressed anywhere.
Twilio developer evangelist here.
As far as I know there is currently no way to store metadata, like your account ID, within an SMS sent via Twilio.
One idea could be that you purchase a number of Twilio numbers and tie together a user's phone number, a Twilio phone number and the specific account. That way, if you always send balance notifications for a specific account from a specific number then you can identify that message in the logs as belonging to that user phone number for that account.
Alternatively, I'd have thought it would be useful for users, if they have more than one account, to see to which account you are referring in a balance notification. Would it be possible to include the account id (or some other identifier that the user would recognise) and then parse that out of the message when reconciling messages and accounts?
Not exactly the question but if you are using twilio webhooks for status callbacks you can pass query string params through the status_callback parameter when making the call to send the SMS message and get it sent to your endpoint
Could anyone tell which countries would be able to send and receive SMS AND calls to Latvia?
I can't seem to find an answer, it appears that LV numbers can't send SMS, yet I see prices on the pricing page. I'm quite confused as of which country I should get a number in (and the price).
If I get a LV number, does it mean i can send, but not receive SMS? It would be fine for my app (already built, waiting to go live).
Basically, it is a browser app acting as a soft phone (single user), so no landline involved. Is there a way to solve the country problem?
Twilio evangelist here.
Looks like we currently only have Voice enabled Latvian numbers (numbers with a +371 prefix). Buying one costs you $1 US and use can use it to have Twilio make a voice phone call from it or receive phone calls to it.
For SMS, Twilio does support sending international SMS from US numbers, so you certainly could buy a US number and use it to send text messages to a Latvian number. The pricing for that is here (scroll down to see per-carrier pricing details).
Hope that helps clarify.
Now am heard about mailchimp for effective email marketting
So i downloaded it form here
But i have few questions
whta is the advantage of mailchimp ?
Better tutorial for mailchimp ?
Better tutorial for mailchimp ?
Anybody please help me
I want to integrate mailchimp in magento
any help is appreciated
The advantages...
Using the Magento newsletter function will probably get you banned from sending email from your web server. Most hosting plans put a limit on the amount of transactional emails that can be sent for the following reason. If they end up sending too much spam-like email, they will be put on block lists and then all their customers get penalized for a few bad players.
They would rather that you send promotional email which can bounce, or end up being marked as unsolicited commercial email through an email service provider that monitors and cleans up any activities that cause unnecessary junk mail to enter the system and also limits through TOS, where lists can come from (existing customers, people who've subscribed, people who wish to receive promotional email and have signed up through other means).
Mail Chimp is one such email service provider, there are several, a couple have created integration modules for Magento so you don't have to export your newsletter subscribers and import them into the email service.
Mail Chimp also is able to give you statistics and will tie into Google Analytics so you can start tracking how effective your promotional emails are, can try different approaches and see what really works and what customers were interested in on the promotional email through link referral from each item you've included. With Magento, you sling stuff at a wall and hope something sticks, with the statistics Mail Chimp can tell you what you flung at the wall, how hard you flung it, how sticky it was and whether people prefer popsicles and chocolate truffles over candy apples and lemon drops. From this you can go from "Meh, whatever..." responses to "Hmm, I think I want this".
Any email service provider you choose can offer this type of statistics and analysis... Magento Newsletter can't.
This is copy/pasted straight out of a proposal I recently submitted for a Magento site with integration with a 3rd party newsletter system (in this case I am using the Fontis Campaign Monitor module, which I like);
"
The default Magento email newsletter functionality is not as good as it could be. I would normally hook the email newsletter submission box up to a service like MailChimp or Campaign Monitor (I'd recommend the latter).
They allow you to manage your distribution lists and generate and customise email templates yourself which will actually arrive at the inboxes of your customers and not get spammed, bounced or look awful in their email client. These systems allow you to test your newsletter in a huge range of email clients and will advise you of any mistakes you've made (ie badly chosen spammable keywords).
They will allow you to send the comapigns to your distribution lists from thier server, and will also give statistics on your email campaigns – bounce rate, open rate, click through rate, numbers flagged as spam, users who unsubscribed, all the different geographies they went to etc.
And they are free until you get about 2000 recipients, after which you pay a small amount for a very good service.
"
You can find examples and demos in Third-Party API Wrappers for PHP repositories.