Set up personal service providers for Email & SMS notifications

An overview of how to configure 3rd party service providers (Email & SMS) in Quixy

After this article, you will know:

• What is the use of Email and SMS configuration in preferences

• How to configure an Email server 

• How to configure SMS server

Email & SMS option in Preferences is used to setup custom email & SMS sender for your organization, i.e., you can customize sender email address and sender SMS name for all notifications in the application sent through Quixy.

For example, the emails which are sent from Quixy will have email address as notifications@quixy.com, you can change that to be notifications@slcs.com. The SMS notification which is sent from Quixy will have name like VVTQXY, you can change it to whatever name you want, maybe, SLCSUK.

How to configure Email?

To configure a new sender email address, you need to enable the Custom Email Sending Configuration option and provide all the required details. Refer to the image below to know about the required details.

1. Give an Email Address by which the emails will be sent from Quixy. 

2. SMTP Client: An SMTP Client allows sending of e-mail notifications using a SMTP server. Simple Mail Transfer Protocol (SMTP) is a widely used protocol for the delivery of e-mails between TCP/IP systems and users. Nowadays, SMTP servers usually require a client authentication using credentials.

   Example

   An SMTP client for Gmail, An SMTP (Simple Mail Transfer Protocol) server is an application that's primary purpose is to send, receive, and/or relay outgoing mail between email senders and receivers. ... When you send an email, the SMTP server processes your email, decides which server to send the message to, and relays the message to that server.

3. Give the User ID and Password of your company.

4. Give the SMTP port, modern email servers use port 587 for the secure submission of email for delivery. For example, if you use an email client software like Outlook or Apple Mail, it is most likely is configured to use this port to send your messages.

How to configure SMS?

To configure a new SMS sender, you need enable the Custom Email Sending Configuration button to fill the required details, refer to the image below to know about the required details.

1. Give the SMS Gateway URL, your SMS address is the email address associated with your cell phone and is determined using your mobile phone number and mobile service provider. For example, if your mobile phone number is 555-123-4567 and your mobile service provider is AT&T, your SMS address would be 5551234567@txt.att.net.

2. Enter user id provided by your SMS service provider.

3. Enter secret key provided by your SMS service provider.

4. Enter sender id with which you want to send SMS messages.

Configuring SMS Gateway with GET and POST Methods

When setting up a custom SMS sender in Quixy, you can choose between GET and POST methods to integrate with your SMS service provider. This flexibility lets you tailor how messages are sent, ensuring compatibility with your provider’s API and meeting your business needs.

• GET – Works like typing a website URL. Everything (mobile number, message, API key) is visible in the link.

• POST – Works like filling out a form. Details are hidden inside the request body for better security and flexibility.

Why Does This Matter?

Imagine you work at Swiftly Deliveries, a logistics company that keeps customers updated with real-time SMS notifications. You want to:

• Instantly notify customers when a package is dispatched.

• Securely share tracking links and estimated delivery times when a package is out for delivery.

With Quixy’s GET and POST options, you can:

• Use GET for simple, fast alerts like dispatch notifications.

• Use POST for secure, data-rich messages like tracking updates.

Let’s break down how both methods work and when to use them.

How GET Works:

Think of GET like sending a postcard. Anyone who sees the URL can read the message. It’s best for quick alerts where security isn’t a concern.

Step-by-Step Flow for GET SMS

• Quixy sends an SMS request to the provider’s API.

• The request is in URL format, containing the message, number, and API key.

• The provider delivers the SMS.

When to Use a GET Request?

A GET request sends data through a URL, making it a quick way to trigger SMS notifications. However, since everything is visible in the URL, it’s best for simple, non-sensitive messages.

When Should You Use GET?

• Instant alerts – Example: Your order has been confirmed!

• Shipping updates – Example: Your package is on the way!

• Basic reminders – Example: Your appointment is tomorrow at 10 AM.

When Should You Avoid GET?

• If the message contains personal or sensitive information.

• If you need to send long messages, as URLs have length limits.

• If security is a concern, since data is visible in the URL.

How POST Works:

Think of POST like sealing a letter inside an envelope. The details stay hidden, making it ideal for secure messages or when sending bulk SMS.

Step-by-Step Flow for POST SMS

• Quixy sends an SMS request to the provider’s API.

• The details (message, mobile number, API key) are sent inside the request body (not in the URL).

• The provider processes and delivers the SMS.

For secure or detailed messages, POST is the better option.

When Should You Use a POST Request?

A POST request is best for secure, structured, or complex SMS messages. Unlike GET, it keeps sensitive data hidden and allows longer messages.

When Should You Use POST?

• Secure notifications – Example: "Your OTP is 456789."

• Tracking updates with links – Example: "Track your package here: [link]."

• Bulk messaging – Sending many SMS messages at once.

When Should You Avoid POST?

• If you need a simple, quick setup, as GET is easier.

• If debugging is a concern, since POST data isn’t visible like GET.

For secure, detailed, or large-scale messaging, POST is the best option.

Multiple From Emails in a Single SMTP

Admins can configure multiple "From Email" addresses with the same or different SMTP setups, allowing greater flexibility in managing email communications. Along with the one "From Email" configuration, address could be used, but now multiple addresses can be added to suit various functions.

Admins can set one address as the default, ensuring that it’s used for the majority of outgoing emails, such as app notifications. However, when specific communications require a different address, admins can easily override the default and choose a more appropriate "From Email" address based on the situation. This setup helps in organizing email communications by function or department, ensuring that recipients can easily identify the sender.

For instance, a company can assign different "From Email" addresses to various teams:

• Support Team: support@company.com

• Billing Department: billing@company.com

• Marketing Team: marketing@company.com

While the support email address may be set as the default for most notifications, the billing department can use their own email address for sending invoices, and marketing can use theirs for promotional communications. This improves the clarity and organization of emails, ensuring that the right team is represented in each message.