Messaging providers
Messaging providers are the email, SMS and Viber services that actually deliver your survey invitations — and any other messages — to your customers. They're what your messaging pipelines and the dispatch queue use to send. Configure the Email, SMS and Viber providers used to deliver surveys across all of your workspaces. Admin only
A provider you add is created across every workspace in your organization. You can test it any time, and when you edit it, your changes apply to every workspace that shares it.
No provider? You're covered
If you don't have your own messaging provider yet, you can use e-satisfaction's own email and SMS service. An Email Provider by e-satisfaction and an SMS Provider by e-satisfaction are available as part of your plan — see Subscription for what's included. They let you start sending surveys straight away, with nothing to set up.
When you're ready to send from your own infrastructure (for example, to use your own sender address or your own deliverability), you can add one of the providers below at any time.
How adding a provider works
For every provider, the pattern is the same: you create an account with the provider, generate API credentials (an API key, token or username and password) from their dashboard, then paste those credentials here. e-satisfaction uses them to hand your messages off to that service for delivery.
Common fields
When you add any provider, you'll fill in a few shared fields before the provider-specific credentials:
- Sender — the from-address (for email) or sender name (for SMS and Viber) your customers will see.
- Sender name — for email providers, the friendly name shown alongside the address.
- Title / description (optional) — a label to help you recognise this provider in your list.
After that, you'll enter the credentials specific to the provider you chose, listed below.
The provider list
Providers are grouped by the channel they deliver on. Use the table to see what you'll need to have ready before you start.
Email providers
| Provider | Channel | What you'll need |
|---|---|---|
| SMTP | Host, port, security (TLS/SSL), username, password | |
| Moosend | Username, password | |
| Contact Pigeon | API key, flow ID | |
| Mandrill (Mailchimp Transactional) | API key | |
| Mailgun | API key, working domain, region (US/EU) | |
| AMD Telecom | Application ID, application secret |
SMS providers
| Provider | Channel | What you'll need |
|---|---|---|
| EasySMS | SMS | API key |
| SMSMe | SMS | Username, password |
| Apifon | SMS | Token, API key |
| Yuboto | SMS | API key |
| M-Stat | SMS | User ID, auth key |
| Infobip | SMS | Base URL, API key |
| GT Digital | SMS | User ID, password |
| Contact Pigeon | SMS | API key, flow ID |
| sms4u | SMS | Username, API key |
Viber providers
Viber is delivered through the same account you use for the matching SMS service, so you'll connect it with the same provider credentials. Each Viber provider also offers an SMS fallback option, so a message is sent by SMS when Viber isn't available for a recipient.
| Provider | Channel | What you'll need |
|---|---|---|
| Apifon | Viber | Same account as Apifon SMS, plus optional SMS fallback |
| Yuboto | Viber | Same account as Yuboto SMS, plus optional SMS fallback |
| M-Stat | Viber | Same account as M-Stat SMS, plus optional SMS fallback |
| Infobip | Viber | Same account as Infobip SMS, plus optional SMS fallback |
| AMD Telecom | Viber | Same account as AMD Telecom, plus optional SMS fallback |
| Contact Pigeon | Viber | Same account as Contact Pigeon, plus optional SMS fallback |
Add and test a provider
Create an account with the provider
Sign up with the provider you want to use (for example, Mailgun for email or Apifon for SMS). Skip this if you're using e-satisfaction's own email or SMS service.
Generate your credentials
In the provider's own dashboard, generate the API key, token or username and password listed for that provider in the table above.
Add the provider here
Choose the channel and provider, fill in the Sender (and Sender name for email), then paste your credentials into the provider-specific fields.
Send a test
Use the test action to send a sample message to yourself. Confirm it arrives, looks right and shows the correct sender before you rely on it.
Save
Save the provider. It's now available across every workspace in your organization, ready for your pipelines and the dispatch queue to use.
Edits apply everywhere
Because a provider is shared across all of your workspaces, editing its sender or credentials changes it everywhere it's used. Send a test after any edit so you don't quietly break sending in another workspace.
Related
Configuration
Pipelines
Dispatch queue
Subscription