All Collections
Integrations
1:1 SMS Communication
1:1 SMS Communication

1:1 SMS Communication with smrtPhone, Twilio, and Plivo

Kylie avatar
Written by Kylie
Updated over a week ago

Our 1:1 SMS feature can be used with our smrtPhone, Twilio, and Plivo integration to send messages directly from within your REISift account.

Installing the Integration

smrtPhone

To install the smrtPhone integration, please follow the steps listed in this article: Setting up smrtPhone Integration

Once the smrtPhone integration is installed, copy the API key listed under the Admin -> API Tokens section of your smrtPhone account.

Then paste the key into the Settings -> Integrations -> smrtPhone -> Data Out section of your REISift account then click Validate Key.


If there is already a key in the Data Out section please click the eye icon and confirm it matches the API Token in your smrtPhone account. If it does not match, please copy the key from smrtPhone, paste into REISift and click validate key.

Plivo

To install the Plivo integration, copy the authentication token and authentication ID from your Plivo account. Next navigate to the Settings -> Integrations -> Plivo section of your REISift account and paste the authentication token and ID from Plivo.

Twilio

To install the Twilo integration, copy the authentication token and authentication ID from your Twilio account. Next navigate to the Settings -> Integrations -> Twilio section of your REISift account and paste the authentication token and ID from Twilio.

Sending SMS

Once the integration is installed and you have purchased numbers in smrtPhone, you can send sms directly within the Property Records, the Owner Records, or your Contacts in Phonebook.

Next, open the record you want to send SMS to.

Select the phone number you want to send the message from (this will be your smrtPhone, Twilio or Plivo numbers).


Then select the phone number you want to send the message to.

Enter in your message (up to 160 characters), then hit send! All SMS are logged to the owner activity log.

Note: smrtPhone Phone numbers are ordered by

  1. any number that was already used to send a message to the owner

  2. the last number the current user used to sms someone

  3. other numbers available in the account ordered by creation date

At this time you're unable to set a default number for a specific user as smrtPhone uses callflows to manage numbers and phone numbers are not assigned to a person.

Refreshing Numbers

When purchasing new phone numbers, select the Refresh icon located to the right of the Send to number to refresh your phone number list and bring in any new phone numbers.

Filtering SMS messages

To filter which messages are displayed, click the funnel icon then select the phone number.

Troubleshooting

Setting up 1:1 SMS integration empowers users with efficient communication capabilities. However, common API key issues can lead to unsuccessful message transmissions and hinder seamless communication. In this article, we will guide users through the process of identifying and resolving API key errors, ensuring accurate integration set-up

Understanding API Key Issues: API key misconfiguration is a frequent challenge during the integration process. Users may encounter issues that disrupt the smooth flow of messages, affecting the overall communication experience.

Accessing and Validating the API Token: The first step in resolving API key errors is to access and validate the API token in the SmrtPhone account. Proper validation is crucial to ensure the accuracy of the integration setup.

Comparing API Keys: Data Out vs. SmrtPhone: Next, users must compare the API key listed in the Data Out section with the API key in the SmrtPhone account. This comparison will help identify discrepancies and potential sources of errors.

Replacing an Incorrect API Key: Having identified the incorrect API key, users should promptly replace it with the validated one. This corrective action is essential to establish a seamless 1:1 SMS integration.



Related Trainings
Setting up smrtPhone Integration



Did this answer your question?